Bug#649521: dpkg-dev: Patches got unapplied automatically, no way to turn this wierd behaviour off

2011-11-21 Thread Robert Luberda
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

Bug#649521: dpkg-dev: Patches got unapplied automatically, no way to turn this wierd behaviour off

2011-11-21 Thread Robert Luberda
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

Bug#649521: dpkg-dev: Patches got unapplied automatically, no way to turn this wierd behaviour off

2011-11-21 Thread Jonathan Nieder
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

Bug#649521: dpkg-dev: Patches got unapplied automatically, no way to turn this wierd behaviour off

2011-11-21 Thread Jonathan Nieder
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

Processed: Re: dpkg-dev: Patches got unapplied automatically, no way to turn this wierd behaviour off

2011-11-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: clone 649521 -1 Bug#649521: dpkg-dev: Patches got unapplied automatically, no way to turn this wierd behaviour off Bug 649521 cloned as bug 649531. retitle -1 dpkg-buildpackage -Ttarget should call dpkg-source --before-build first Bug #649531

Bug#649521: dpkg-dev: Patches got unapplied automatically, no way to turn this wierd behaviour off

2011-11-21 Thread Robert Luberda
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

Bug#649521: dpkg-dev: Patches got unapplied automatically, no way to turn this wierd behaviour off

2011-11-21 Thread Jonathan Nieder
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

Processed: merging requests for --no-unapply-patches (Re: dpkg-dev: Patches got unapplied automatically, no way to turn this wierd behaviour off)

2011-11-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: reassign 643043 dpkg-dev 1.16.1 Bug #643043 {Done: Raphael Hertzog hert...@debian.org} [dpkg] dpkg: new feature breaks stuff, leaves meaningless option, leaves no way to override Bug reassigned from package 'dpkg' to 'dpkg-dev'. Bug No longer

Bug#647915: dpkg-deb: xz compression does not support extreme variants

2011-11-21 Thread Guillem Jover
On Tue, 2011-11-08 at 09:13:16 +0100, Philipp Kern wrote: On Tue, Nov 08, 2011 at 06:46:40AM +0100, Guillem Jover wrote: Hmm, this has several issues. The first of which is that currently -z 0 is equivalent to -Z none, so modifying that is an interface change. This is not documented in the

Bug#649531: Bug#649521: dpkg-dev: Patches got unapplied automatically, no way to turn this wierd behaviour off

2011-11-21 Thread Raphael Hertzog
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