> Even though the patch itself is trivial we need to think about how the > program changes when it has been applied, instead of just the simple > mechanical changes in the patch. The resulting change isn't a trivial > two line bugfix, applying the patch actually means enabling a new > feature that hasn't existed before (about 40 lines of previously > disabled code). > > In my mind this is more comparable to a new upstream version entirely,
Thanks for looking into this. In my view, the crucial difference to a new upstream release is that we're talking about a feature which is documented to work in the version shipped with squeeze, so users might burn their time trying to track down why it doesn't. So, personally, I'd at least add a note to the README.Debian file stating that this feature is broken in squeeze. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
