[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: developer's guide to security updates



Thanks Wichert, very informative.

On Thu, Jun 13, 2002 at 09:10:26PM +0200, Wichert Akkerman wrote:
[...]
> Please note that if secrecy is needed you can also not upload a fix
> to unstable (or anywhere else), since the changelog information for
> unstable is public information
[...]
> 
> * Make sure the version number is proper. It has to be higher than the
>   current package, but lower than package versions in later
>   distributions. For testing this means there has to be a higher version
>   in unstable. If there is none yet (testing and unstable have the same
>   version for example) upload a new version to unstable first.

There is a potential conflict here - you may have to upload a new
version to unstable so that the -security version number is acceptable,
but you may not be allowed to upload it to unstable due to secrecy
requirements.


Hamish
-- 
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>


-- 
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org



Reply to: