Control: reassign -1 unattended-upgrades 0.98 Hi, On Wed, Jan 10, 2018 at 02:46:05AM +0100, Balint Reczey wrote: > commit 355e1aceac1dd05c4c7daf3420b09bd860fd169d (HEAD, refs/bisect/bad) This commit also drops support for "legacy filenames" as a comment was dubbing them… I wanted to do that in a separate commit, but forgot about it and then it has fallen through the cracks it seems… Problem is that your Packages file says: | Package: test-package | Architecture: all | Version: 2.0.test.pkg | Description-en: test package | Filename: test-package_2.0_all.deb The "legacy" filename is the filename mentioned in the Packages file. The filename apt will use to store a package on disk in its directory is PKGNAME_VERSION_ARCH.deb, so in your case the filename you use for the package in archives/ should be test-package_2.0.test.pkg_all.deb. Usually (and that is actually the only case I was expecting) this is only a matter with epochs as most repositories don't include the epoch in the filename (as working with ":" in a filename is fun). I don't think it is a good idea to bring back support for reading these legacy filenames as a) apt isn't creating those files & the directory it reads them from can easily be considered a private interface and b) this legacy support creates problems for us in super-edgecases like a test-package available in two repositories in version "0:2.0" and in version "1:2.0" which both would carry it as "2.0". I am therefore reassigning to unattended-upgrades and would suggest as a quickfix to fix either the versionumber or the filename in the test. Best regards David Kalnischkies
Attachment:
signature.asc
Description: PGP signature