On Thu, Jan 25, 2018 at 08:07:52PM +0100, 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.
Epochs were mainly intended for handling the case where upstream changed their version numbering sequence in some way. I don't think the goal of "restart Debian revision numbering sequence" was one that was considered in their design; after all the Debian maintainer can always just use bigger integers, of which there's an indefinite supply. I generally think of the Debian revision as being a sequence independent of epochs. > I doubt that I am the first to fall into this trap. You are not. > I think it is a ubuntu bug, so you should forward it to ubuntu. Speaking as a Launchpad developer, this is highly unlikely to ever be changed in Launchpad; it's one of our fundamental safety checks. The best that could be done in Ubuntu would be to use a different version number, taking care to ensure that if there's ever a new upstream release then we'll be able to get back in sync then. (This is obviously ugly.) > But you showed me that snapshot.debian.org has absolutely no problem to keep > track of every single upload by using separate directories that include the > epoch in the directory name. Or is this a bug as well? snapshot.debian.org doesn't aim to publish a single pool containing both old and new versions. It's essentially happenstance that this didn't break something in Debian. > > > You did not look at the files it seems. > > > > 1.0.51-11 contains moon-buggy_1.0.51-11.tar.gz > > Switching to 3.0 (quilt) gives you moon-buggy_1.0.51.orig.tar.gz > > > > 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? Sure you can. The constraint (applied by both the Debian and Ubuntu archives, with the only material difference being how much history they remember) is that you can't cause a file name in the pool to have different contents from a previous upload of the same file name. (moon-buggy_1.0.51-1.dsc has previously existed, but moon-buggy_1.0.51.orig.tar.gz has not.) -- Colin Watson [[email protected]]
