Hi,
Currently, if the upstream code is changed (anything other than
debian/*).. When dpkg-buildpackage is run, an automated patch is
created. This is a really nice feature, but it is very easy to miss
this. I have seen multiple uploads where these auto-generated patches
have been included
On Wednesday, June 15, 2011 12:40:27 PM Dave Walker wrote:
Hi,
Currently, if the upstream code is changed (anything other than
debian/*).. When dpkg-buildpackage is run, an automated patch is
created. This is a really nice feature, but it is very easy to miss
this. I have seen multiple
On 06/15/2011 07:40 PM, Dave Walker wrote:
Currently, if the upstream code is changed (anything other than
debian/*).. When dpkg-buildpackage is run, an automated patch is
created. This is a really nice feature, but it is very easy to miss
this. I have seen multiple uploads where these
On 16/06/2011 04:52, Micah Gersten wrote:
[...]
I actually use this as a feature. I modify the upstream code, create a source
package, then rename the patch and add DEP-3 info.
I think it should be opt-in rather than opt-out. I've had too many occasions
where I accidentally introduced a new
