Bug#934132: Unblock elogind 241.3-1+debian1 migration to bullseye

2019-09-10 Thread Mark Hindley
On Thu, Sep 05, 2019 at 06:44:26PM +0100, Mark Hindley wrote: > Julien, > > On Tue, Sep 03, 2019 at 09:03:42PM +0100, Mark Hindley wrote: > > Control: severity 934491 serious > > > > On Tue, Sep 03, 2019 at 09:34:51PM +0200, Julien Cristau wrote: > > > Anyway, I guess if #934491 is upgraded to

Bug#934132: Unblock elogind 241.3-1+debian1 migration to bullseye

2019-09-05 Thread Mark Hindley
Julien, On Tue, Sep 03, 2019 at 09:03:42PM +0100, Mark Hindley wrote: > Control: severity 934491 serious > > On Tue, Sep 03, 2019 at 09:34:51PM +0200, Julien Cristau wrote: > > Anyway, I guess if #934491 is upgraded to RC then I can drop the block > > hint. #934491 is now RC, would you please

Bug#934132: Unblock elogind 241.3-1+debian1 migration to bullseye

2019-09-03 Thread Mark Hindley
Control: severity 934491 serious On Tue, Sep 03, 2019 at 09:34:51PM +0200, Julien Cristau wrote: > Anyway, I guess if #934491 is upgraded to RC then I can drop the block > hint. Thank you. Best wishes Mark

Bug#934132: Unblock elogind 241.3-1+debian1 migration to bullseye

2019-09-03 Thread Mark Hindley
Sam, Many thanks for your input on this. On Tue, Sep 03, 2019 at 03:12:18PM -0400, Sam Hartman wrote: > I do agree with simon that #934491 does leave the system in a really bad > state. And while I agree with you that it is not elogind's fault, it's > a situation that tends to only come up when

Bug#934132: Unblock elogind 241.3-1+debian1 migration to bullseye

2019-09-03 Thread Julien Cristau
On Tue, Sep 3, 2019 at 15:29:49 +0100, Mark Hindley wrote: > On Wed, Aug 14, 2019 at 07:22:47PM +0100, Jonathan Wiltshire wrote: > > I think your summary is fine. However, this is not my area of expertise and > > I'm rather hoping Julien or Ansgar will chime in with an update. > > > > It

Bug#934132: Unblock elogind 241.3-1+debian1 migration to bullseye

2019-09-03 Thread Sam Hartman
> "Mark" == Mark Hindley writes: Mark> Michael, Mark> On Tue, Sep 03, 2019 at 04:56:13PM +0200, Michael Biebl wrote: >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934491 >> >> This bug report should be taken into account here. Not sure why >> this is not

Bug#934132: Unblock elogind 241.3-1+debian1 migration to bullseye

2019-09-03 Thread Mark Hindley
Michael, On Tue, Sep 03, 2019 at 04:56:13PM +0200, Michael Biebl wrote: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934491 > > This bug report should be taken into account here. Not sure why this is > not marked as RC given that it can pretty much hose your system. If you actually read

Bug#934132: Unblock elogind 241.3-1+debian1 migration to bullseye

2019-09-03 Thread Michael Biebl
Am 03.09.19 um 16:29 schrieb Mark Hindley: > On Wed, Aug 14, 2019 at 07:22:47PM +0100, Jonathan Wiltshire wrote: >> I think your summary is fine. However, this is not my area of expertise and >> I'm rather hoping Julien or Ansgar will chime in with an update. >> >> It certainly wouldn't be

Bug#934132: Unblock elogind 241.3-1+debian1 migration to bullseye

2019-09-03 Thread Mark Hindley
On Wed, Aug 14, 2019 at 07:22:47PM +0100, Jonathan Wiltshire wrote: > I think your summary is fine. However, this is not my area of expertise and > I'm rather hoping Julien or Ansgar will chime in with an update. > > It certainly wouldn't be appropriate for me to remove a block put in place > by