On Thu, Sep 17, 2015 at 10:27:48PM +0200, Niels Thykier wrote:
> On 2015-09-17 22:25, Santiago Vila wrote:
> > On Thu, Sep 17, 2015 at 09:39:17PM +0200, Niels Thykier wrote:
> >> Source: aegisub
> >> Version: 3.2.2+dfsg-2
> >> Severity: serious
> >>
> >> Hi,
> >>
> >> We have noticed that aegisub is unfortunately not binNMU safe, when we
> >> tried to rebuild it as a part of the GCC-5 transition. The issue is
> >> caused by:
> >>
> >> """
> >> override_dh_installdocs:
> >> dh_installdocs --link-doc=aegisub
> >> """
> >>
> >> This statement makes aegisub-l10n depend strictly on
> >> aegisub (= ${binary:Version}), which is required to ensure the correct
> >> copyright file is always present.
> >
> > Current Depends line for aegisub-l10n is like this:
> >
> > Depends: ${misc:Depends},
> > aegisub (>= ${source:Version}),
> > aegisub (<< ${source:Version}.1~)
> >
> > Is this not binNMU-safe? How it's not?
> >
>
> The resulting package has:
>
> Depends: aegisub (= 3.2.2+dfsg-2)
So whatever clever trick the maintainer put in debian/control
(as in this case) is "spoiled", so to speak, by dh.
If we want to support binNMU (which I think we should deprecate, but
that's another story), why is this not fixed in dh instead?
What you could probably achieve by this bug is that the maintainer
stops using ${misc:Depends}.
