Re: Debian part of a version number when epoch is bumped
On Mon, Apr 02, 2018 at 08:41:00PM +0100, Simon McVittie wrote:
>
> A recap of what happened, for those who might have lost track:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887740#10
> > 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.
>
> The newest version of the old tar-in-tar packaging can be seen here:
> https://sources.debian.org/src/moon-buggy/1.0.51-11/
>
> What I would personally have done *then*, from that starting point, would
> be to bump the version to 1.0.51+repack, or maybe 1.0.51+upstream if
> the new orig tarball was something that the upstream developer released,
> or something similar, then package and upload revision 1 of that. That
> would have been fine - no epoch needed.
>
> However, because you previously maintained this as a native package,
> there has been no collision for the filename of the orig.tar.gz, because
> before the epoch was added there *was* no orig.tar.gz; and you've already
> paid the maintenance cost of having an epoch, so you might as well benefit
> from it. So what I'd advise *now* would be to increase the revision to 12
> and carry on from there.
This has been addressed by policy now, does you recommendation still hold?
I understand the explanation for source and binary package, but I wonder if
I have the right interpretation for the upstream source code:
https://www.debian.org/doc/debian-policy/#uniqueness-of-version-numbers
3.2.2. Uniqueness of version numbers
...
Additionally, for non-native packages, the upstream version must not be
reused for different upstream source code, so that for each source package
name and upstream version number there exists exactly one original source
archive contents (see Files).
Since the intial upload was as native package, and the latest as non-native,
this does not apply to moon-buggy and I can upload with revision 12 as you
suggested?
thanks,
Christian
Reply to: