Bug#836596: libavutil55: borked NMUs with differing changelog

Mattia Rizzolo mattia at debian.org
Sun Sep 4 16:41:02 UTC 2016


On Sun, Sep 04, 2016 at 07:45:07AM -0700, Daniel Schepler wrote:
> On Sun, Sep 4, 2016 at 4:40 AM, Thorsten Glaser <tg at mirbsd.de> wrote:
> > tglase at tglase:~ $ diff -u clog-*
> > --- clog-i386   2016-08-28 12:12:00.000000000 +0200
> > +++ clog-x32    2016-09-03 16:36:00.000000000 +0200
> > @@ -1,3 +1,10 @@
> > +ffmpeg (7:3.1.3-1+b3) unstable; urgency=medium
> > +
> > +  * Binary-only NMU: Rebuild against against libchromaprint1.
> > +  * Manually built to resolve circular Build-Depends with chromaprint.
> > +
> > + -- x32 Build Daemon (frobozz) <buildd_x32-frobozz at buildd.debian-ports.org>  Sat, 03 Sep 2016 07:36:24 -0700
> > +
> >  ffmpeg (7:3.1.3-1) unstable; urgency=medium
> >
> >    * Team upload.
> 
> Sorry about that, I did in fact have to do manual builds for the
> reason mentioned (and it looks like essentially the same situation
> still exists on hppa and sparc64).  I thought the build system would
> automatically separate out the binNMU log into
> /usr/share/doc/*/changelog.x32.gz.

It indeed happens automatically.

What you did wrong is probably *how* that binNMU was scheduled.  sbuild
(and pbuilder too nowadays) have their options to do it, and they do it
right, so I really wonder what you did, because yes, dpkg (=> the "build
system" of yours above :)) splits automatically the binNMU changelog.

You are missing the 'binary-only=yes' "option" on it; the first line
should have been:

    ffpmeg (7:3.1.3-1+b3) unstable; urgency=low, binary-only=yes

(or another urgency; the urgency field for binNMUs is pretty
indifferent).

> At this point, I can't really see any way to fix the issue, though
> (short of scheduling another binNMU for all architectures).

good question :)

-- 
regards,
                        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540      .''`.
more about me:  https://mapreri.org                             : :'  :
Launchpad user: https://launchpad.net/~mapreri                  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/attachments/20160904/76fefb1f/attachment-0001.sig>


More information about the pkg-multimedia-maintainers mailing list