>> This seems to break dpkg-genchanges, e.g. when building acpid: > And it will break many infrastructure tools. I know that various QA tools > build the path name directly from the package name and the version without > referring to any "Packages" files. And they explicitely strip the epoch > when doing so...
Uh, yes, such a major change shouldn't make it into any dpkg in use until it got properly discussed and tools adapted. > It means the archive will be inconsistent during quite a long time with > packages where the epoch is and is not in the filename. The archive won't "break", I think, from a quick look - it will just refuse to process any upload of a package with files with an epoch in it for not finding the files. No wonder, they unexpectedly changed names. > IMO this change needs further discussion and buy in before being deployed. Ack. -- bye, Joerg Bart, with $10,000, we'd be millionaires! We could buy all kinds of useful things like...love! -- To UNSUBSCRIBE, email to debian-dpkg-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87y5pyjner....@gkar.ganneff.de
