Hello, On Thu, 25 Jan 2018, Christian T. Steigies wrote: > If I can not use an epoch to start version > numbers from scratch, then the whole implementation of epochs is broken. > I doubt that I am the first to fall into this trap.
epochs are meant to go backwards when upstream changes their versioning scheme... upstream did not change anything here and using an epoch was thus not the correct choice. > > Those file names are not the same and therefore it would have been > > fine. You absolutely do not need an epoch when switching from a native > > package to a non-native package. > > But I can not upload two 1.0.51 versions with different tar files, can I? Jérémy is correct. You definitely can because the filenames are different. And even when you use a filename conflict you can update the tarball just by using a different compression, i.e. using orig.tar.xz instead of orig.tar.gz. To me it also looks entirely wrong to go from 1.0.51-11 to 1:1.0.51-1. In particular since users interfaces are expected to not show the epoch to end-users. When you see an upgrade: 20121312 -> 1.0.51 you understand that upstream changed their versioning scheme and you ask yourself no questions. When you see an upgrade 1.0.51-11 -> 1.0.51-1 then you ask yourself what's going wrong here... So I would also suggest to bump version to 1:1.0.51-12. Not for launchpad, but for end users. Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: https://www.freexian.com/services/debian-lts.html Learn to master Debian: https://debian-handbook.info/get/
