[Debian-med-packaging] [kevin at kdmurray.id.au: Fwd: Re: Dawg ready for review]
Andreas Tille
andreas at an3as.eu
Wed Dec 2 11:34:47 UTC 2015
Hi Kevin,
----- Forwarded message from Kevin Murray <kevin at kdmurray.id.au> -----
> Date: Wed, 2 Dec 2015 22:22:48 +1100
> From: Kevin Murray <kevin at kdmurray.id.au>
>
> > Unfortunately there is another problem. When inspecting the patches I
> > even stumbled upon it when reading 0004-Chmod-x-examples.patch since it
> > looked new to me that quilt should be able to chmod files. I guess the
> > patches were created from some "Git to Quilt" magic (the guess is also
> > supported by the file names).
> >
> > WHen I try to build it results in
> >
> > ...
> > No file to patch. Skipping patch.
> > dpkg-source: info: the patch has fuzz which is not allowed, or is malformed
> > dpkg-source: info: if patch '0004-Chmod-x-examples.patch' is correctly applied by quilt, use 'quilt refresh' to update it
> > dpkg-source: error: LC_ALL=C patch -t -F 0 -N -p1 -u -V never -E -b -B .pc/0004-Chmod-x-examples.patch/ --reject-file=- < dawg-1.2.orig.L6hmVM/debian/patches/0004-Chmod-x-examples.patch gave error exit status 1
> > dpkg-buildpackage: error: dpkg-source -i.git -I.git -b dawg-1.2 gave error exit status 2
> > gbp:error: '~/bin/git-pbuilder' failed: it exited with 2
> >
>
> Hmm, very strange. I cannot reproduce this.
Even more strange...
> And, a linitan warning which
> complained that these files were executable in the binary package went away
> after implementing this patch.
The *intention* you were following is pretty clear - you just want to
fix permissions.
> How are you using gbp? I just do a standard gbp
> buildpackage with a amd64 sid git-pbuilder.
Same here called from an up to date Stretch (=testing) machine.
> > I personally do not no an other solution for the problem you try to
> > solve with this patch than
> >
> > override_dh_fixperms:
> > dh_fixperms
> > chmod -x debian/$(DEBPKGNAME)/...
> >
>
> OK, so you' prefer I remove the patch and put this in d/rules?
Well, if someone else can build and sponsor I'd be fine with
it but I simply can not build otherwise.
Kind regards
Andreas.
--
http://fam-tille.de
More information about the Debian-med-packaging
mailing list