Bug#940034: elogind and the release team block

2019-09-11 Thread Adam Borowski
On Wed, Sep 11, 2019 at 09:15:58AM -0400, Sam Hartman wrote: > I reached out to jcristau to talk about his block hint. > Based on our IRC discussion, it sounds like he was having trouble > bringing himself to remove the hint presumably because he doesn't think > the broader issue was being dealt wi

Bug#940034: elogind and the release team block

2019-09-11 Thread Sam Hartman
> "Adam" == Adam Borowski writes: Adam> On Wed, Sep 11, 2019 at 09:15:58AM -0400, Sam Hartman wrote: >> I reached out to jcristau to talk about his block hint. Based on >> our IRC discussion, it sounds like he was having trouble bringing >> himself to remove the hint presumab

Bug#940034: elogind and the release team block

2019-09-11 Thread Mark Hindley
Julien, On Wed, Sep 11, 2019 at 03:07:51PM +0100, Mark Hindley wrote: > I would hope we can all accept those. If so, there is no requirement for a > manual block: at the moment there are RC bugs which prevent migration. If or > when they are resolved migration can occur based on the release teams

Bug#940034: elogind and the release team block

2019-09-11 Thread Mark Hindley
Sam, Thanks On Wed, Sep 11, 2019 at 09:15:58AM -0400, Sam Hartman wrote: > I reached out to jcristau to talk about his block hint. > Based on our IRC discussion, it sounds like he was having trouble > bringing himself to remove the hint presumably because he doesn't think > the broader issue was

Bug#940034: elogind and the release team block

2019-09-11 Thread Sam Hartman
Dear Mark: I reached out to jcristau to talk about his block hint. Based on our IRC discussion, it sounds like he was having trouble bringing himself to remove the hint presumably because he doesn't think the broader issue was being dealt with. I suggested that he might open his concerns as an