search

lucidsoftware / apt-boto-s3

The fast and simple S3 transport for apt.
Apache License 2.0
56 stars 13 forks source link

1.4 deb package built as 1.3 version #24

Open soudaburger opened 6 years ago

soudaburger commented 6 years ago

Architecture: all Depends: python-pip Description: The fast and simple S3 transport for apt Maintainer: Lucid Software ops@lucidsoftware.com Package: apt-boto-s3 Priority: optional Section: base Version: 1.3 Filename: pool/main/a/apt-boto-s3/apt_boto_s3_1.4.deb SHA1: 25481954d9e6f7dfaa78e36a7d46ce09a605130a SHA256: 00b9ade87ddefc4a332e088683d4d3ff7234d0ee8132978843c3c53c60bd2aa9 Size: 4242

Architecture: all Depends: python-pip Description: The fast and simple S3 transport for apt Maintainer: Lucid Software ops@lucidsoftware.com Package: apt-boto-s3 Priority: optional Section: base Version: 1.3 Filename: pool/main/a/apt-boto-s3/apt_boto_s3_1.3.deb SHA1: 62dfae417529b8b20ff0863b2fad0542bdeea5f5 SHA256: 4a8da0b0fde8e8421f508efa8f4432d4fadb4c449e48deabf96c7c52917a379f Size: 3824

So apparently you guys built TWO 1.3 packages. Things have been breaking for the last couple of days. We have seen the apt update process hang as well as "invalid authorization headers" even though everything was working fine for months.

Can we get a valid 1.4 built as well as the malformed 1.3 package removed to ensure we can better identify WHICH package is broken all of a sudden?

soudaburger commented 6 years ago

Manual installation of the original 1.3 package works perfectly fine.

soudaburger commented 6 years ago

Can we get the new 1.5 version and/or the proper 1.4 version pushed to the lucidsoftware deb repo ?

soudaburger commented 6 years ago

Apparently 1.5 is built as "1.3" as well... seriously can we get this fixed????

From "debian/control" in the source tarball: Architecture: all Depends: python-pip Description: The fast and simple S3 transport for apt Maintainer: Lucid Software ops@lucidsoftware.com Package: apt-boto-s3 Priority: optional Section: base Version: 1.3

Raclaw commented 6 years ago

Can we have an update on this issue?

eesperan commented 6 years ago

This can be fixed by editing debian/control and incrementing the Version to 1.5 (or whatever the current release is). This version will need to be updated for each subsequent release.

eesperan commented 6 years ago

@pauldraper you appear to be the most recent committer, can you make this update?