Re: Wheezy update of libtomcrypt?
2016-09-04 17:51 GMT+02:00 Michael Stapelberg <email@example.com>:
> Thanks for your work on LTS.
> Time does not permit me to do any of this work myself.
> Please go ahead and make any changes as you see fit, there’s no need for my
Thank you for your quick answer.
I (on behalf of the LTS Team since I'm responsible for frontdesk now) take your
answer as covering all future security updates for releases in LTS period
thus we won't contact you for each CVE.
If you happen to change your mind please just send the LTS Team an email
> On Sun, Sep 4, 2016 at 5:38 PM, Thorsten Alteholz <firstname.lastname@example.org>
>> Hello Michael,
>> the Debian LTS team would like to fix the security issues which are
>> currently open in the Wheezy version of libtomcrypt:
>> Would you like to take care of this yourself?
>> If yes, please follow the workflow we have defined here:
>> If that workflow is a burden to you, feel free to just prepare an
>> updated source package and send it to email@example.com
>> (via a debdiff, or with an URL pointing to the source package,
>> or even with a pointer to your packaging repository), and the members
>> of the LTS team will take care of the rest. Indicate clearly whether you
>> have tested the updated package or not.
>> If you don't want to take care of this update, it's not a problem, we
>> will do our best with your package. Just let us know whether you would
>> like to review and/or test the updated package before it gets released.
>> Thank you very much.
>> Thorsten Alteholz,
>> on behalf of the Debian LTS team.
>> PS: A member of the LTS team might start working on this update at
>> any point in time. You can verify whether someone is registered
>> on this update in this file:
> Best regards,