[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: dpkg-buildpackage, dpatch and wrong permissions...



Claudio Moratti wrote:
Hi *!

I've a strange problem:
I've a package with 2 patches, created with dpatch...

I compile it with a classic
$ fakeroot dpkg-buildpackage
but...
===
fakeroot dpkg-buildpackage
dpkg-buildpackage: source package is k9copy
dpkg-buildpackage: source version is 1.0.3.2-1
dpkg-buildpackage: source changed by Claudio Moratti <maxer@knio.it>
dpkg-buildpackage: host architecture i386
 debian/rules clean
dh_testdir
dh_testroot
rm -f build-stamp
rm -f po/*.gmo
rm -f config.sub
rm -f config.guess
/usr/bin/make distclean
make[1]: Entering directory `/home/maxer/toremove/k9copy-1.0.3.2'
make[1]: *** No rule to make target `distclean'.  Stop.
make[1]: Leaving directory `/home/maxer/toremove/k9copy-1.0.3.2'
make: [clean-patched] Error 2 (ignored)
dh_clean
dpatch  deapply-all
02_libtool not applied to ./ .
01_dotdesktop not applied to ./ .
rm -rf patch-stamp patch-stampT debian/patched
 dpkg-source -b k9copy-1.0.3.2
dpkg-source: building k9copy using existing k9copy_1.0.3.2.orig.tar.gz
dpkg-source: building k9copy in k9copy_1.0.3.2-1.diff.gz
dpkg-source: warning: executable mode 0755 of `debian/patches/02_libtool.dpatch' will not be represented in diff dpkg-source: warning: executable mode 0755 of `debian/patches/01_dotdesktop.dpatch' will not be represented in diff
===

I checked twice the permissions of debian/patches/* files, and before the build, are correct (-rw-r--r--) after...ehm...not:

===
$ ls -l debian/patches/*
-rw-r--r-- 1 maxer maxer      39 2006-02-22 13:50 debian/patches/00list
-rwxr-xr-x 1 maxer maxer 618 2006-02-22 13:50 debian/patches/01_dotdesktop.dpatch -rwxr-xr-x 1 maxer maxer 1425968 2006-02-22 13:50 debian/patches/02_libtool.dpatch
===

I have, in the parent directory, only the sources dir and the .orig.tar.gz file.. nothing else...

dpkg-dev and dpatch are up to date:
ii  dpatch                              2.0.18
ii  dpkg-dev                            1.13.16

I'm not able to find how fix this problem...

suggestions?

Thx a lot ;-)

Claudio


This is not really a problem. The point is that diff can't see in a diff file if a file is executable yes or no, before diff didn't shout this warning. Anyway my build here goes ok and have also some warnings about "0755 cannot be represented in diff" warnings. But they shouldn't harm the build.

Regards,

Matthijs Mohlmann



Reply to: