Bug#836596: libavutil55: borked NMUs with differing changelog

[Mattia Rizzolo]

On Sun, Sep 04, 2016 at 10:50:36AM -0700, Daniel Schepler wrote:
> OK, the "binary-only=yes" is what I missed.  What I actually did was:
> manually schroot into sid-x32-sbuild (after requesting buildd to shut
> down temporarily); then extracted src:ffmpeg and src:chromaprint,
> added the binNMU changelog manually for ffmpeg; then built and
> installed ffmpeg with the stage1 build profile, built and installed
> chromaprint, then did a full build of ffmpeg.

umh, ok, that was a case where you needed to bootstrap ffmpeg, so maybe
using sbuild'd --make-binNMU was not easily accomplished.  Or peraphs
you could have:
    1) sbuild --make-binNMU="Manually built to resolve circular Build-Depends with chromaprint." --binNMU=3 --profile=stage1
    2) upload those binaries somewhere accessible to the buildd (I
       think even uploading them to ports.d.o would have been ok)
    3) schedule a regular binNMU without any build profile (maybe
       through wanna-build, even)

I think that would have brought to the same result (module a higher
binNMU version for the second build), with even less hassle :)

(disclaimer: icbw, I'm not a porter, nor a bootstrapper)

-- 
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/8b9d21d5/attachment.sig>