Re: Suggestion to end support for legacy 1024-bit RSA root CAs in Fedora stable

2016-08-18 Thread Yaakov Selkowitz
On Tue, 2016-08-16 at 15:23 +0200, Kai Engert wrote: > On Mon, 2016-08-15 at 22:19 +0200, Kai Engert wrote: > > > > Unless we find good reasons not to do it, I suggest to push the > > legacy > > removals > > to stable around 2016-09-21. > > I just noticed that the Fedora 25 beta freeze is schedul

Re: Testing request: AMD chipset kernel issue

2016-08-18 Thread Luya Tshimbalanga
On 18/08/16 02:45 PM, Adam Williamson wrote: > On Thu, 2016-08-18 at 14:19 -0700, Luya Tshimbalanga wrote: >> On 18/08/16 12:07 PM, Adam Williamson wrote: >>> Hi folks! >>> >>> There is a bug nominated as a Fedora 25 Alpha blocker: >>> >>> https://bugzilla.redhat.com/show_bug.cgi?id=1367321 >> Inte

Re: Testing request: AMD chipset kernel issue

2016-08-18 Thread Zach Villers
Will test tonight and report. On Thu, Aug 18, 2016 at 5:45 PM Adam Williamson wrote: > On Thu, 2016-08-18 at 14:19 -0700, Luya Tshimbalanga wrote: > > On 18/08/16 12:07 PM, Adam Williamson wrote: > > > > > > Hi folks! > > > > > > There is a bug nominated as a Fedora 25 Alpha blocker: > > > > > >

Re: Schedule for Friday's FESCo Meeting (2016-08-19)

2016-08-18 Thread Chris Murphy
Please also add https://fedorahosted.org/fesco/ticket/1615 --- Chris Murphy -- devel mailing list devel@lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: Testing request: AMD chipset kernel issue

2016-08-18 Thread Adam Williamson
On Thu, 2016-08-18 at 14:19 -0700, Luya Tshimbalanga wrote: > On 18/08/16 12:07 PM, Adam Williamson wrote: > > > > Hi folks! > > > > There is a bug nominated as a Fedora 25 Alpha blocker: > > > > https://bugzilla.redhat.com/show_bug.cgi?id=1367321 > Interesting. My desktop system has an identic

Schedule for Friday's FESCo Meeting (2016-08-19)

2016-08-18 Thread Adam Miller
Following is the list of topics that will be discussed in the FESCo meeting Friday at 16:00UTC in #fedora-meeting on irc.freenode.net. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/UTCHowto or run: date -d '2016-08-12 16:00 UTC' Links to all tickets below c

Re: Testing request: AMD chipset kernel issue

2016-08-18 Thread Germano Massullo
I am very busy in these weeks, but if you need other testing cases, I have many AMD machines -- devel mailing list devel@lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: Testing request: AMD chipset kernel issue

2016-08-18 Thread Luya Tshimbalanga
On 18/08/16 12:07 PM, Adam Williamson wrote: > Hi folks! > > There is a bug nominated as a Fedora 25 Alpha blocker: > > https://bugzilla.redhat.com/show_bug.cgi?id=1367321 Interesting. My desktop system has an identical ASUS motherboard from the reporter. The only difference is the cpu, a AMD Pheno

Re: Testing request: AMD chipset kernel issue

2016-08-18 Thread Adam Williamson
On Thu, 2016-08-18 at 17:13 -0300, Fernando Cassia wrote: > On 8/18/16, Adam Williamson wrote: > > > > > There is a bug nominated as a Fedora 25 Alpha blocker: > > > > https://bugzilla.redhat.com/show_bug.cgi?id=1367321 > > > > on affected systems, it prevents boot entirely, which is obviously

Testing request: AMD chipset kernel issue

2016-08-18 Thread Adam Williamson
Hi folks! There is a bug nominated as a Fedora 25 Alpha blocker: https://bugzilla.redhat.com/show_bug.cgi?id=1367321 on affected systems, it prevents boot entirely, which is obviously pretty bad. But we're not sure yet how many systems would be affected by the bug. So we're looking for more feed

[Guidelines change] Changes to the packaging guidelines

2016-08-18 Thread Jason L Tibbitts III
Here are the recent changes to the packaging guidelines. - The Filesystem Layout section of the guidelines was simplified and outdated information was removed. * https://fedoraproject.org/wiki/Packaging:Guidelines * https://fedoraproject.org/wiki/Packaging:Guidelines#Filesystem_Layout * http

Fedora 25 Alpha status is NO-GO

2016-08-18 Thread Jan Kurik
Release status of the Fedora 25 Alpha Go/No-Go Meeting is NO-GO. Due to missing RC and present blockers [1] in the Fedora 25 Alpha, the decision is to slip the Fedora 25 Alpha release for one week. There is going to be one more Go/No-Go meeting the next Thursday, August 25th, 2016 at 5:00PM UTC to

Re: Bugzilla issues

2016-08-18 Thread Coty Sutherland
Done, thanks! On Thu, Aug 18, 2016 at 12:13 PM, Zbigniew Jędrzejewski-Szmek wrote: > On 08/18/2016 11:41 AM, Coty Sutherland wrote: >> Hello all, >> >> I'm trying to get some help with a couple of BZs that look odd to me. >> >> It looks like these two bugs are somehow stuck in an ON_QA state by a

Re: Bugzilla issues

2016-08-18 Thread Zbigniew Jędrzejewski-Szmek
On 08/18/2016 11:41 AM, Coty Sutherland wrote: > Hello all, > > I'm trying to get some help with a couple of BZs that look odd to me. > > It looks like these two bugs are somehow stuck in an ON_QA state by an > obsolete bodhi update. There was an update which resolved them that > was pushed to st

Bugzilla issues

2016-08-18 Thread Coty Sutherland
Hello all, I'm trying to get some help with a couple of BZs that look odd to me. It looks like these two bugs are somehow stuck in an ON_QA state by an obsolete bodhi update. There was an update which resolved them that was pushed to stable a while ago. The two bugs are: https://bugzilla.redhat.

Re: RFC: Round 2 review of Fedora Docker Layered Image Guidelines

2016-08-18 Thread Tim Waugh
On Thu, 2016-08-18 at 09:28 -0400, Tomas Tomecek wrote: >  * Guidelines suggest to use "BZComponent" but upstream label > guidelines mention >    "com.redhat.component"; I would suggest using the latter one > (disclaimer: I >    participated actively in the early history of changes in the label > n

Re: RFC: Round 2 review of Fedora Docker Layered Image Guidelines

2016-08-18 Thread Tomas Tomecek
Quoting Adam Miller (2016-05-31 19:12:47) > Hello all, > I had previously sent out a RFC email about a month ago asking for > feedback on the Fedora Docker Layered Image Guidelines[0]. > > I was asked by FESCo to start a new thread so that this can be > discussed further on the devel mailing l

Re: need help with gcc segfault on i686

2016-08-18 Thread Till Hofmann
On 08/12/2016 11:43 AM, Florian Weimer wrote: > On 08/12/2016 11:36 AM, Till Hofmann wrote: >> Hi all, >> >> gprolog has been FTBFS for a while due to a segfault on i686, see this >> build [1] for an example. I followed advice on [2] to add some debugging >> flags, not sure if they really help thou