Hi there! On Wed, 16 May 2012 09:50:50 +0200, Gerfried Fuchs wrote: > * Luca Capello <luca@pca.it> [2012-05-15 17:48:04 CEST]: >> - what about previous debian/changelog entries for a package that was in >> lenny-backports, it has now a major version and it has also changed >> uploader? >> <http://backports-master.debian.org/Contribute/#index5h3> > > Depends on how you would see the "branching" going on. Personally I > keep my packaging in git. When creating the squeeze-backports branch > from a package formerly backported to lenny-backports, I create it off > the versioned tag for testing, and not from the lenny-backports branch > and *then* merge in the versioned tag from testing. [...] > so I tend to > consider starting off "fresh" for squeeze-backports is the better > approach. > > The upload would have to contain the changelog since squeeze in the > changes file anyway, not since the lenny-backports version, so ... Got it, thanks. > I think you might have picked up this part wrongly here: > > ,------------------------------> quote <------------------------------ > | • Include all changelog entries since the last version on debian-backports or > | since stable if it's the first version. You should do this by passing "-v" > | to dpkg-buildpackage. Eg: "debuild -sa -v0.7.5-2", where "0.7.5-2" is the > | version in stable. If the package wasn't in stable or backports before you > | don't have include the changelog entrys (but you are free to do so). > `------------------------------> quote <------------------------------ > > This is a requirement about the *changes* file, not about the changelog > itself. You were right, I read "changelog entries" without really thinking about the -v meaning, thank you very much! Thx, bye, Gismo / Luca
Attachment:
pgpUICUiKdmgi.pgp
Description: PGP signature