On Mon, Aug 10, 2009 at 10:24:27PM +0300, Jari Aalto wrote: > Guido Günther <a...@sigxcpu.org> writes: > > >> If possible, just peek the debian/chnagelog for existing string. Or > >> check output of dpkg-parsechnagelog to determine if dch call is needed. > > This can be done but I don't see why one would adjust the changelog > > first and import the orig later? This is the opposite of gbp's suggested > > workflow. > > You see, it's possible that the error sin debian/* directory are being > worked on *before* the upgrade is done. The debian/chnagelog is already > in state of being prepared for the next release, with version numbers > and all. > > When the debian/* structure is ok (perhaps fixing lintian errors when > policy has since chnaged), the user may decided "Now I upgrade the > tarball". > > Thus, debian/chnagelog conflict. This does not happen if you use git-dch in snapshot mode. Doing otherwise really doesn't fit the gbp workflow nicely. But I get your point. Cheers, -- Guido
-- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
