S3 Publish not working correctly

[lswith]

aptly version: 0.9.6

Steps to reproduce (all done through the api):

1. Create local repo + add .deb
2. Create snap1 from local repo
3. Publish snap1 to S3
4. Remove .deb from local repo
5. Create snap2 from local repo
6. Delete Publish from S3
7. Publish snap1 to S3

The .deb is included in the Package but the pool directory isn't created again.

[igurung]

Hrmm.. We are also getting same error as you describe @Lswith

[smira]

@Lswith are you using -no-lock or anything special in API mode?

[lswith]

No. Nothing special. It seems to work as expected with the Cli but not the Api. Also, if you correct it using the Cli, it works as expected until the same .deb's are taken out of the repo again.

It also works when using the local mode. On Mon, 15 Feb 2016 at 11:26 PM, Andrey Smirnov [email protected] wrote:

@Lswith https://github.com/Lswith are you using -no-lock or anything special in API mode?

— Reply to this email directly or view it on GitHub https://github.com/smira/aptly/issues/349#issuecomment-184186221.

[mnacharov]

Have the same problem. It still appear in v1.4.0(master)

[chicks-net]

Has this been fixed @lbolla or is the project just ignoring issue that are "too old" to worry about?

[lbolla]

mmm Indeed this issue had a relatively recent comment (from 2020). I closed it by mistake!

[alan-wint]

Still seeing this problem - no pool directory created on S3 Just to clarify, the CLI worked fine; things started to go wrong after multiple publishes from a snapshot via the API. Aptly 1.5.0

I was able to publish to S3 properly via the API by deleting all published repos, deleting all snapshots, clearing the local repo, deleting all directories in .aptly/pool, running aptly db cleanup, aptly db recover and restarting the service.