Bug#874663: Document +dfsg as extenson when repacking upstream sources
On Fri, 08 Sep 2017 at 10:38:54 -1000, David Prévot wrote:
> Le 08/09/2017 à 07:44, Simon McVittie a écrit :
> > This made me think that we should maybe only be doing this when
> > a *pre-existing* upstream version needs to be repacked.
> > […] when upstream releases
> > foo/1.2.4, even if the non-freeness has not been fixed, the
> > maintainer would repack it as 1.2.4 rather than 1.2.4+dfsg.
>
> That is be a bit misleading: since we are not using the upstream
> version, using the same version is a lie.
In general we are not using the upstream version anyway, and that's why
we append a Debian revision. The practical difference between, for
example, yquake2 7.01 and 7.01~dfsg1-2 is a lot smaller than the
difference between, for example, openssh 7.5p1 and openssh 7.5p1-5 (the
latest on sources.debian.net); so why does yquake2 need a special marker
that openssh does not?
(yquake2 drops Windows and Mac support files that would not affect the
Linux binary anyway, but its only patches are minor and to the Makefile;
openssh patches the code significantly, adding large new features.)
Regards,
smcv
Reply to: