Package: dpkg-dev
Version: 1.16.1.1
Severity: important
While working on my package, I've noticed that the
debuild -nc -b
command no longer works properly - i.e. it recompiles
almost everything instead of just use already built files.
It's because dpkg-source automatically unapplied patches
as
Hi,
I've just came up with another reason why the current behavious is
wrong: let's imagine that maintainer modifies the clean action of
upstream's Makefile (see the latest bsd-mailx for example). Than a
`debuild clean' (or dpkg-buildpackage -Tclean) won't run the modified
clean target.
For
Hi Robert,
Robert Luberda wrote:
While working on my package, I've noticed that the
debuild -nc -b
command no longer works properly - i.e. it recompiles
almost everything instead of just use already built files.
It's because dpkg-source automatically unapplied patches
as a part of the
clone 649521 -1
retitle -1 dpkg-buildpackage -Ttarget should call dpkg-source
--before-build first
quit
Robert Luberda wrote:
I've just came up with another reason why the current behavious is
wrong: let's imagine that maintainer modifies the clean action of
upstream's Makefile (see the
Jonathan Nieder wrote:
Hi,
On one hand, in dpkg's source format v3, the patched source is considered
to be standard unpacked form. So if you run
dpkg-source -x foo.dsc
cd foo-*
dpkg-buildpackage; # just builds the package
then patches will be applied in the first
retitle 649521 please add dpkg-buildpackage --no-unapply-patches, to keep
patches applied
severity 649521 wishlist
unarchive 643043
forcemerge 649521 643043
quit
Robert Luberda wrote:
I can even modify my debuild script to do `quilt push -a',
but it won't change the fact that unapplying
On Mon, 21 Nov 2011, Jonathan Nieder wrote:
Robert Luberda wrote:
I've just came up with another reason why the current behavious is
wrong: let's imagine that maintainer modifies the clean action of
upstream's Makefile (see the latest bsd-mailx for example). Than a
`debuild clean' (or
7 matches
Mail list logo