Re: evilwm_1.1.0-1~bpo70+1_amd64.changes REJECTED
On 09/03/2013 04:12 PM, Alexander Wirt wrote:
>> I'm not sure whether I can follow you here. I was pretty sure Mateusz
>> included all the changes since 1.0.0-1 as evilwm has been rejected
>> for that reason from wheezy-backports before. I checked the changelog
>> and I thought it was ok.
> No. He merged just everything into the latest changelog entry, which is
> Adding those old entrys is done via the "-v" option of dpkg-buildpackage.
Ok, I see. Is there some documentation on that which I can read? This
is my first upload to backports so I'm still not a 100% sure what I am
The changelog entry for 1.1.0-1~bpo70+1 contains all the changes since
1.0.0-1, so I am not sure what's missing.
I'm sorry, I currently feel a bit dumb for not grasping the problem ;).
>> Also, I'm not sure what do you mean with changes not done for the
>> backport. The backport contains all the same changes that were applied
>> to the latest unstable version.
> And thats wrong. The backports entry should only contain the changes done for
> the backports version.
Which were none, in fact. The package is just rebuilt in a Wheezy
So, if I get it right, in order to backport, one:
- creates a changelog entry with all the changes between the unstable
version and the backport
- builds the package with pbuilder --debbuildopts -v1.0.0-1
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - email@example.com
`. `' Freie Universitaet Berlin - firstname.lastname@example.org
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913