Re: Accepted libdaemons-ruby 1.0.9-1~bpo40+1 (source all i386)
Alexander Wirt wrote:
> Micah Anderson schrieb am Tuesday, den 08. January 2008:
>> I guess I do not understand the instructions on the website:
>> Include all changelog entries since the last version on backports.org or
>> since stable if it’s the first version.
> Yes, thats what meaned with the part of
> Include all changelog entries since the last version on backports.org or
> since stable if it’s the first version. You should to this by passing
> “-v<version>” to dpkg-buildpackage. Eg: ‘debuild -sa -v0.7.5-2’, where
> ‘0.7.5-2’ is the version in stable.
> Which is meaned like include the changes done in testing since the last
> version in backports.
What happens if the version given to dpkg-buildpackage does not exist in the Changelog ?
I mean, for example :
Version 0.6-1 in stable (changelog has 0.6-1)
Version 0.7-1 in testing (changelog has 0.6-1 and 0.7-1)
Version 0.7-1~bpo40+1 in backport (changelog has 0.6-1, 0.7-1 and 0.7-1~bpo40+1)
=> note one tool (lintian ?) complain here because 0.7-1 > 0.7-1~bpo40+1
but I think it is normal to ignore
Version 0.8-1 in testing (changelog has 0.6-1, 0.7-1 and 0.8-1)
Version 0.8-1~bpo40+1 in backport
=> changelog has 0.6-1, 0.7-1, 0.8-1 and 0.8-1~bpo40+1
but not 0.7-1~bpo40+1 because I do not use this 'branch' at all to make
my backport. I start again with the latest package from testing. If needed
I read the 0.7-1~bpo40+1 changelog to know which change I need to make
but I remake (and recheck) these changes.
So, I think I need to include 0.8-1 and 0.8-1~bpo40+1 changes when uploading
Am I right ?
And does dpkg-buildpackage will do the right thing with -v0.7-1~bpo40+1 (I do not
think so but I do not tried yet) ? I think the correct parameter will be -v0.7-1
PS: I think the fundamental problem is that the changelog is linear whereas
backporting involves branches. And that a backport is done AFTER the testing
package but it needs a version BEFORE the one from testing package.