[Pkg-privacy-maintainers] RFS: codecrypt, the post-quantum cryptography tool

[Ximin Luo]

u:
> Hi,
> 
> Holger Levsen:
>> On Wed, Apr 20, 2016 at 08:36:28PM +0200, Ximin Luo wrote:
>>> Hey Mirek, I see you've successfully created a git repo and pushed to it.
>>> Everything looks good from my end. Shall I upload it to Debian? 
> 
> 
>>> (The changelog needs to be squashed as a single entry, with version 1.7.4-1
>>> since this would be the first Debian release, but I can do that myself when
>>> I upload.)
>>
>> while you are absolutly free to do so (and I also think it is nicer if you
>> do), there is no must requirement to do so. :)
>>
>> changelogs are pretty much free form, as long as they are syntactically
>> correct, anything goes, technically.
> 
> Correct. With tails-installer we have such a weird changelog which also
> contains releases which were done for tails only:
> https://git-tails.immerda.ch/liveusb-creator/tree/debian/changelog?h=debian/sid
> 

All of this is true, but I was worried about a particular default behaviour of dpkg-genchanges that only includes *some* entries from debian/changelog. This would cause the ITP bug not to be automatically closed by the upload, creating extra work. If we squash it down to one entry, we don't need to do this extra work.

If you noticed that sometimes you need to manually close bugs even if you put a "Closes: #####" in your changelog, this might be the reason. To avoid this, either make sure you have only one changelog entry since the last release to Debian, or you need to give -v${last_released_version} to dpkg-genchanges (or dpkg-buildpackage or gbp-buildpackage).

Anyway I already fixed it in git. :)

X

-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
git://github.com/infinity0/pubkeys.git