Bug#871056: transition: openssl
On 12/10/17 10:56, Emilio Pozuelo Monfort wrote:
> On 21/09/17 21:39, Sebastian Andrzej Siewior wrote:
>> On 2017-09-13 18:51:43 [+0200], Emilio Pozuelo Monfort wrote:
>>> tags 871056 confirmed
>>> thanks
>>
>> just noticed that this bug has been confirmed. Does this mean anything
>> for the openssl transition? Usually this confirmed comes with "Go ahead"
>> which leads to an upload to unstable and the severity of the blocker
>> bugs is raised to serious.
>> Should the severity of the blocker bugs be raised or do we keep things
>> as they are for now?
>
> As we discussed on the last release team meeting: let's do this, but first send
> a 'warning' saying that the bugs will be bumped in a month, and do the bump
> later. That will give maintainers more time to react before the auto-removal
> kicks in.
We're getting close. According to the transition tracker, the remaining rdeps in
testing are:
netty-tcnative - fixed upstream
omniorb-dfsg - fixed in experimental
ruby2.3 - ongoing transition to ruby2.5, then this will be removed
xml-security-c - no fix, but upstream said it would get fixed "this year"
ipsec-tools - no fix, but due for autoremoval
openssh - Kurt has worked on a fix with upstream
qtbase-opensource-src - fixed in experimental, we need a Qt transition
curl - transition pending
kopete - no fix upstream, optional for jingle (call) support in XMPP
xmltooling - same as xml-security-c
zurl - blocked on curl
Hopefully we get those transitions done soon and the rest get some progress too.
Cheers,
Emilio
Reply to: