Re: dpkg-dev: please reject native/non-native version when building native/non-native source packages
Le Tue, Feb 04, 2014 at 02:05:45PM +0000, Dimitri John Ledkov a écrit :
> On 4 February 2014 13:38, Jakub Wilk <jwilk@debian.org> wrote:
> > * Dimitri John Ledkov <xnox@debian.org>, 2014-02-04, 13:30:
> >
> >> Enforcing Debian Policy at dpkg-source -b . level, is not a good idea,
> >> especially when it breaks backwards compat for 3rd parties. We have lintian,
> >> and ftp-master lintian auto-rejects to clense the archive if so is desired.
> >
> > Hear, hear. And I even doubt there's consensus it is desired.
>
> Patch is attached to the new bug filed about this issue
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737634
> Proposed patch adds "--force-native" dpkg-source option for the "3.0
> (Native)" format, which ignores enforcing native version number check.
Hi Dimitri, and everybody,
I fully agree that the behaviour should not be changed without reaching
consensus, and I am very disapointed that the bug that you opened on dpkg was
tagged "wontfix".
The current practice is that there is no strict correspondance between using a
"native" dpkg source format and being "native" to Debian. In that sense, I do
not see the point for forbidding to use non-"native" version numbers with
"non-native" dpkg formats.
The 3.0 (native) format is useful when packaging a work that is developped and
distributed in a Git repository. Please leave us this possibility.
Cheers,
--
Charles Plessy
Tsurumi, Kanagawa, Japan
Reply to: