On 18 July 2016 at 06:21, James Cowgill <[email protected]> wrote: > Hi, > > On Sun, 2016-07-17 at 22:16 +0000, [email protected] wrote: >> The following commit has been merged in the master branch: >> commit d3dc4b14057eab6f3bfa09c8388a7c20351ccf95 >> Author: >> Date: Sun Jul 17 17:40:59 2016 -0400 >> >> Rebuild against ffmpeg-3.1.1 (Closes: #831537) >> >> diff --git a/debian/changelog b/debian/changelog >> index 0e3ff7b..1123209 100644 >> --- a/debian/changelog >> +++ b/debian/changelog >> @@ -1,3 +1,9 @@ >> +mpv (0.18.0-2) UNRELEASED; urgency=medium >> + >> + * Rebuild against ffmpeg-3.1.1 (Closes: #831537) >> + >> + -- Nicholas D Steeves <[email protected]> Sun, 17 Jul 2016 17:38:39 -0400 > > This is the wrong way to go about doing this. If you just want to > rebuild a package, then you should ask the release team to binNMU it. > > IMO this warning should be patched out of mpv (and any ABI issues > sorted out). Upstream also seems to have made this warning into a fatal > error in 0.18.1 which is obviously unacceptable for Debian. > > https://github.com/mpv-player/mpv/commit/d057e7a142a327c653f3f0379014567028448b5d
My mistake, I've reverted it. When is "dch -R" appropriate? When I saw the bug report I thought "aha! I know how to fix this, this is what dch -R is for!" because it is a "no-change rebuild" (dch manpage). Also, I thought that even no change rebuilds were supposed to be represented in git... Has someone else already emailed debian-release@lists? Best regards, Nicholas _______________________________________________ pkg-multimedia-maintainers mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
