On Fri, Jan 19, 2018 at 10:07:26AM -0500, Jeremy Bicha wrote: > Source: moon-buggy > Version: 1:1.0.51-1 > > moon-buggy can't be automatically synced to Debian because Launchpad > gives this error: > > moon-buggy 1:1.0.51-1 in buster (moon-buggy_1.0.51-1.dsc already > exists in destination archive with different contents.) > > I believe all you need to do to fix this is to upload a new version as > 1:1.0.51-12 so that the non-epoch version has a different (and in this > case, higher) version number.
As far as I understand 1:1.0.15-1 is larger than 0:1.0.15-whatever. The package has migrated to testing, what else needs to be synced in Debian? What is Launchpad? https://packages.qa.debian.org/m/moon-buggy.html I do not know why the source package does not include the epoch in the dsc filename, but thats how it came out of git buildpackage. > By the way, I don't see any reason why you needed to add or bump the epoch > here. I was asked to remove ESD support. The old source package contained two tar balls, the "real" tarball plus a separate one with patches (upstream wanted things separate). The build script was, say, not optimal, and I also made the mistake of uploading it as debian native package. By bumping the epoch and repackaging from scratch, I tried to fix all the mistakes I had made a long time ago. What is the purpose of an epoch if I need to increase the Debian version nevertheless? Christian
