On Fri, Aug 09, 2019 at 01:13:58PM +0200, Svante Signell wrote: > On Fri, 2019-08-09 at 12:06 +0100, Jonathan Wiltshire wrote: > > On Fri, Aug 09, 2019 at 12:55:02PM +0200, Svante Signell wrote: > > > On Fri, 2019-08-09 at 11:41 +0100, Adam D. Barratt wrote: > > > > Control: severity -1 normal > > > > > > > > On 2019-08-09 11:33, Debian Bug Tracking System wrote: > > > > > Processing commands for cont...@bugs.debian.org: > > > > > > > > > > > severity 934132 important > > > > > Bug #934132 [release.debian.org] unblock: elogind/241.3- > > > > > 1+debian1 > > > > > Severity set to 'important' from 'normal' > > > > > > > > No. release.d.o bugs are normal at most unless the team decide > > > > otherwise. Please leave them like that. > > > > > > Might be so. But explain why this package is still blocked, buster > > > was > > > released several weeks ago! > > > > Because it's nothing to do with buster. We're working on bullseye > > now. > > So elogind has been excluded from the bullseye release? Maybe you can > explain that decision.
For the time being, yes, and for the reasons outlined in the initial bug report. You seem very intent on believing that this is a permanent state. In fact there are probably nearly two years in which the problems outlined in this bug can be resolved. If they are, I see no reason why elogind couldn't be in bullseye in the fullness of time. Please take a little time to study the background before you make alarmist conclusions like this. Thanks, -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51