Re: BinNMU changelog handling for Multi-Arch: same packages
On Tue, 2012-07-17 at 14:25:18 +0200, Philipp Kern wrote:
> On Fri, Jul 13, 2012 at 09:07:00AM +0200, Raphael Hertzog wrote:
> > On Thu, 12 Jul 2012, Philipp Kern wrote:
> > > > #681292 against sbuild. Feel free to clone it if necessary.
> > > I just verified a build in stable and get a bunch of these:
> > >
> > > dpkg-source --after-build hello-2.6
> > > parsechangelog/debian: warning: hello-2.6/debian/changelog(l1): unknown key-value Binary-only
> > > LINE: hello (2.6-1+b1) unstable; urgency=low, binary-only=yes
> > > parsechangelog/debian: warning: unknown information field 'Binary-Only' in input data in parsed version of changelog
> > > dpkg-buildpackage: binary and diff upload (original source NOT included)
> > >
> > > If we add that, dpkg in all supported suites should at least do the right
> > > thing and ignore it.
> > I'm happy to prepare a stable update to fix this. Would you accept it?
> I presume there are no other RC bugfixes for dpkg/stable pending at the
> moment? Could you prepare the diff and post it here?
No there are not, and I could prepare it yes, but I'm not sure there's
any point anyway as this alone (in wheezy) will not solve the
binNMU+multiarch case anyway, and as it's been said I think it's too
late for the other possible fixes.
> (I'd currently tend to accept it, however I'm not yet sure of all the
> consequences of this change.)
This change in itself should not have any consequence as it should not
affect the normal build if the value is not being used, or maybe you
are referring to *when* the value is being used?