On Sun, Sep 4, 2016 at 9:41 AM, Mattia Rizzolo <mat...@debian.org> wrote: >> 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).
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. -- Daniel
