On 23-08-15 20:43, Johan Van de Wauw wrote:
> On Sun, Aug 23, 2015 at 1:19 PM, Sebastiaan Couwenberg wrote:
>> I've manually binNMU'ed fiona (1.6.0-1) on the amd64 porterbox to
>> resolve this issue without intervention of the Release Team to process
>> the nmu request.
> Just wondering - is this something I could have done as well (as as
> DM, not DD)? Just running dpkg-buildpackage -b (from a fresh sid) and
> uploading the changes?
Yes, most of the magic that makes a package a binNMU is in the
changelog, for binNMU you create them with `dch --bin-nmu`. And building
the source with all quilt patches applied using `dpkg-buildpackage -B`,
note -B vs -b, see dpkg-buildpackage(1):
The procedure is described from the porter point of view in the
Developer's Reference, besides the above URL see also:
Most important aspect is ensuring that the build environment is clean
and up-to-date. The schroot procedure takes care of that:
But this requires a guest account on the porterbox in question.
Since amd64 was the problem, you can also use your regular sid-amd64
cowbuilder chroot, e.g. by using the --login option and building the
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Pkg-grass-devel mailing list