On Friday, September 23, 2011 08:17:54 AM Raphael Hertzog wrote: > * “dpkg-source -b” on a “2.0” or “3.0 (quilt)” source package will fail > if it detects upstream changes which are not managed by a quilt patch. > > You are expected to call “dpkg-source --commit” if you want to > record those changes permanently. In this process, you will have > to give a patch name and you will be invited to edit the DEP-3 > headers[1] of the new patch.
I can see where this might be useful for final work before an upload, what is one expected to do when one is doing successive builds where things change every time while working on a package? dpkg-buildpackage -b, "Oh, fail", "dpkg-source --commit", "no, no DEP-3, it's not a permenent patch, please go away", dpkg-buildpackage -b is getting tiring very quickly. Scott K -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/13443571.3WdoJ55DQj@scott-latitude-e6320