Re: flow of things rules/debhelper (still confused)

>> I am still confused about my initial question when which binary-* >> target in debian/rules is called. > > Very simple: binary-arch to build all arch-dependent packages from that > source and binary-indep to build all arch-independent packages. The > binary target should then depend on binary-ar

Re: flow of things rules/debhelper (still confused)

Guys, I am still confused about my initial question when which binary-* target in debian/rules is called. This also concerns: - http://www.debian.org/doc/maint-guide/ch-dreq.en.html#s-rules - http://www.debian.org/doc/debian-policy/ch-source.html#s-debianrules which seem to be out of sync. The pol

Re: flow of things rules/debhelper

is more or less what happens: debian/rules build dh build [...] fakeroot debian/rules binary [...] dpkg-deb: building package... No sign of debian/binary-arch and/or debian/binary-indep here. Probably because I did not write down a specific rule binary: binary-arch binary-indep dh $@

flow of things rules/debhelper

Hello there, today, I have a question regarding the maintainers guide, which says: "fakeroot debian/rules binary" runs "fakeroot dh binary" which in turn runs "fakeroot dh binary-arch" and "fakeroot dh binary-indep"... It does indeed work that way, but hadn't it better be: "debian/rules binary"

Re: correctly upgrading a package's source format to 3.0(quilt)

Well, let's first speak in general terms: The facts are that .orig files should be UNMODIFIED upstream archives, and unless really necessary (whatever that means), should only be modified by patches (debian/patches), so that the modifications made to upstream are transparent to every package maint

pbuilder --build --binary-arch invokes 'build' target

Hi, I'm trying to address bug #521918 . When I run pbuilder as pbuilder --build --binary-arch eprover_1.0.004-1.dsc so that it should build only the binary target, it seems to me that it still invokes the 'debian/rules build' target, instead of 'build-arch'