Re: Proposing new release criteria

> I don't know the formal process for proposal but here is a shot at a bare > minimum > start for trying to add containers to the existing release criteria. This is > a suggestion > after we found podman can't pull containers from a registry in f31 [1]. > > New section for Containers and Contain

Re: Fedora-Workstation x86_64-31-20190828 installs in VM but boots to Ooops

On Sat, Aug 31, 2019, 8:16 AM Ed Greshko wrote: > > Is this a known issue? I'm guessing it has to do with an > Wayland issue and the VBox Video drivers. However, I don't know how > to prove that. Ah. And it happens on baremetal as well FWIW Somebody knows from where this screen comes from?

Re: Fedora-Workstation x86_64-31-20190828 installs in VM but boots to Ooops

On 8/31/19 1:30 PM, Alessio wrote: > On Sat, Aug 31, 2019, 6:51 AM Ed Greshko > wrote: > > Is this a known issue?  I'm guessing it has to do with an Wayland issue > and the VBox Video drivers.  However, I don't know how to prove that. > > > Same issue here. > Bu

Re: Fedora-Workstation x86_64-31-20190828 installs in VM but boots to Ooops

On Sat, Aug 31, 2019, 6:51 AM Ed Greshko wrote: > Is this a known issue? I'm guessing it has to do with an Wayland issue > and the VBox Video drivers. However, I don't know how to prove that. > Same issue here. But it should be this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1746563 Cia

Re: Fedora-Workstation x86_64-31-20190828 installs in VM but boots to Ooops

On 8/31/19 12:51 PM, Ed Greshko wrote: > Just started to test F31.  The Xfce and KDE spins are going OK.  I'm using > VirtualBox-6.0-6.0.10 directly from Oracle on the host. > > Fedora-Workstation-Live-x86_64-31-20190828.n.0.iso boots fine and the Install > to boot completes without error. > > Ho

Fedora-Workstation x86_64-31-20190828 installs in VM but boots to Ooops

Just started to test F31.  The Xfce and KDE spins are going OK.  I'm using VirtualBox-6.0-6.0.10 directly from Oracle on the host. Fedora-Workstation-Live-x86_64-31-20190828.n.0.iso boots fine and the Install to boot completes without error. However, when booting to the installed system I get t

Re: Proposing new release criteria

On 8/30/19 9:36 AM, Kamil Paral wrote: > On Thu, Aug 29, 2019 at 4:33 PM Dusty Mabe > wrote: > > I don't know the formal process for proposal but here is a shot at a bare > minimum > start for trying to add containers to the existing release criteria. This

Fedora 31 compose report: 20190829.n.0 changes

OLD: Fedora-31-20190828.n.0 NEW: Fedora-31-20190829.n.0 = SUMMARY = Added images:1 Dropped images: 2 Added packages: 3 Dropped packages:23 Upgraded packages: 0 Downgraded packages: 0 Size of added packages: 7.13 MiB Size of dropped packages:245.40 MiB Size

Fedora-31-20190829.n.0 compose check report

No missing expected images. Failed openQA tests: 18/152 (x86_64), 1/2 (arm) Old failures (same test failed in Fedora-31-20190828.n.0): ID: 438981 Test: x86_64 Server-dvd-iso modularity_tests URL: https://openqa.fedoraproject.org/tests/438981 ID: 438989 Test: x86_64 Workstation-live-iso

Fedora 31 Beta blocker status email #4

Action summary Accepted blockers - 1. dracut-modules-olpc — Cannot be installed due to unsatisfied 'bitfrost' dependency — NEW ACTION: releng to make Pungi config changes 2. desktop-backgrounds — Fedora 31 still using Fedora 30 backgrounds — NEW ACTION: deskto

Re: Proposing new release criteria

On Thu, Aug 29, 2019 at 4:33 PM Dusty Mabe wrote: > I don't know the formal process for proposal but here is a shot at a bare > minimum > start for trying to add containers to the existing release criteria. This > is a suggestion > after we found podman can't pull containers from a registry in f3

Fedora rawhide compose report: 20190830.n.0 changes

OLD: Fedora-Rawhide-20190829.n.0 NEW: Fedora-Rawhide-20190830.n.0 = SUMMARY = Added images:0 Dropped images: 0 Added packages: 10 Dropped packages:11 Upgraded packages: 90 Downgraded packages: 0 Size of added packages: 3.43 MiB Size of dropped packages

Fedora-Rawhide-20190830.n.0 compose check report

No missing expected images. Compose FAILS proposed Rawhide gating check! 11 of 45 required tests failed, 6 results missing openQA tests matching unsatisfied gating requirements shown with **GATING** below Unsatisfied gating requirements that could not be mapped to openQA tests: FAILED: compose.cl