Re: Summary/Minutes from today's FESCo Meeting (2017-02-10)

2017-02-12 Thread Jan Pokorný
On 11/02/17 02:08 +0100, Kevin Kofler wrote: > Justin Forbes wrote: >> * AGREED: Allow the update, encourage everyone to work through the >> process better next time (7,0,0) (jforbes, 16:51:10) > > The context: > https://pagure.io/fesco/issue/1675 > #1675 Libglvnd update breaking F25 > is m

Re: Summary/Minutes from today's FESCo Meeting (2017-02-10)

2017-02-11 Thread Rob Clark
On Sat, Feb 11, 2017 at 5:50 AM, Kevin Kofler wrote: > Justin Forbes wrote: >> There are really no more technical road blocks in this update. There are >> several advantages to having it. To deny it at this point would be >> entirely punitive. To me, that did not seem warranted at this time, thou

Re: Summary/Minutes from today's FESCo Meeting (2017-02-10)

2017-02-11 Thread Kevin Kofler
Justin Forbes wrote: > There are really no more technical road blocks in this update. There are > several advantages to having it. To deny it at this point would be > entirely punitive. To me, that did not seem warranted at this time, though > if it is a continuing problem, it may well be the next

Re: Summary/Minutes from today's FESCo Meeting (2017-02-10)

2017-02-10 Thread Justin Forbes
On Feb 10, 2017 7:09 PM, "Kevin Kofler" wrote: Justin Forbes wrote: > * AGREED: Allow the update, encourage everyone to work through the > process better next time (7,0,0) (jforbes, 16:51:10) The context: https://pagure.io/fesco/issue/1675 #1675 Libglvnd update breaking F25 is missing the

Re: Summary/Minutes from today's FESCo Meeting (2017-02-10)

2017-02-10 Thread Kevin Kofler
Justin Forbes wrote: > * AGREED: Allow the update, encourage everyone to work through the > process better next time (7,0,0) (jforbes, 16:51:10) The context: https://pagure.io/fesco/issue/1675 #1675 Libglvnd update breaking F25 is missing there. This is essentially giving the GNOME develop

Re: LVM RAID (was Re: Summary/Minutes from today's FESCo Meeting (2017-02-10))

2017-02-10 Thread Subhendu Ghosh
On Feb 10, 2017 16:27, "Chris Murphy" wrote: On Fri, Feb 10, 2017 at 12:27 PM, Chris Nope. The monitoring works with dmeventd, but I'm not sure how sophisticated the monitoring is or what messaging method it uses (dbus?) or what monitors it (udisksd or storaged?). But again, the loss of email no

Re: LVM RAID (was Re: Summary/Minutes from today's FESCo Meeting (2017-02-10))

2017-02-10 Thread Chris Murphy
On Fri, Feb 10, 2017 at 12:27 PM, Chris Adams wrote: > Once upon a time, Justin Forbes said: >> * AGREED: Discussion on anaconda LVM change is delayed until 2-17 >> provided open questions get answered (+1:6,0:0,-1:0) (jforbes, >> 17:24:33) > > So, not sure if this is in the "open ques

LVM RAID (was Re: Summary/Minutes from today's FESCo Meeting (2017-02-10))

2017-02-10 Thread Chris Adams
Once upon a time, Justin Forbes said: > * AGREED: Discussion on anaconda LVM change is delayed until 2-17 > provided open questions get answered (+1:6,0:0,-1:0) (jforbes, > 17:24:33) So, not sure if this is in the "open questions", but on the mailing list I brought up the fact that MD