Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Acquire-by-hash doesn't work for S3 repositories #692

Closed
fpytloun opened this issue Jan 10, 2018 · 0 comments · Fixed by #697
Closed

Acquire-by-hash doesn't work for S3 repositories #692

fpytloun opened this issue Jan 10, 2018 · 0 comments · Fixed by #697

Comments

@fpytloun
Copy link

fpytloun commented Jan 10, 2018 •
edited
Loading

When updating publish on s3 using Acquire-by-hash, it will fail with following error:

aptly_api.1.r6tek0dbsch1@cz7108    | [GIN] 2018/01/10 - 13:33:03 | 500 |  1.175944957s |    172.16.48.50 |  PUT     /api/publish/s3:aptcdn:xenial_elastic/nightly
aptly_api.1.r6tek0dbsch1@cz7108    | Error #01: unable to update: unable to build hash file: Acquire-By-Hash: error checking exists of file xenial/elastic/dists/nightly/main/binary-amd64/by-hash/SHA256/68b0d591147674c0002e9dd976e7f48f0579e6c847e2f1d21853dbf944e31d2b: NotFound: Not Found

by-hash directory doesn't exist on s3 at all. But it works fine for local publishes.

Using aptly version 1.2.0+2+g1aa8870
@pjediny pjediny mentioned this issue Jan 17, 2018
Merged
@smira smira closed this as completed in #697 Feb 9, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Issues 692 pjediny/aptly
1 participant
@fpytloun