Fedora 31 compose report: 20191024.n.2 changes

2019-10-24 Thread Fedora Branched Report
OLD: Fedora-31-20191024.n.0 NEW: Fedora-31-20191024.n.2 = SUMMARY = Added images:1 Dropped images: 1 Added packages: 0 Dropped packages:0 Upgraded packages: 6 Downgraded packages: 0 Size of added packages: 0 B Size of dropped packages:0 B Size of upgraded

Fedora-31-20191024.n.2 compose check report

2019-10-24 Thread Fedora compose checker
No missing expected images. Failed openQA tests: 3/153 (x86_64), 1/2 (arm) New failures (same test not failed in Fedora-31-20191024.n.0): ID: 476418 Test: x86_64 KDE-live-iso base_update_cli URL: https://openqa.fedoraproject.org/tests/476418 ID: 476497 Test: x86_64 universal

Re: The operation would result in removing the following protected packages: kernel-core, systemd

2019-10-24 Thread Samuel Sieb
On 10/24/19 11:54 AM, Felix Miata wrote: Adam Williamson composed on 2019-10-24 11:10 (UTC-0700): On Thu, 2019-10-24 at 11:07 -0700, Samuel Sieb wrote: Felix Miata wrote: $SUBJECT is the output. No, it's not. dnf prints out a lot more than that and to find out what's happening, we need to se

Re: The operation would result in removing the following protected packages: kernel-core, systemd

2019-10-24 Thread stan via test
On Thu, 24 Oct 2019 14:54:12 -0400 Felix Miata wrote: > The new kernel gets used during the upgrade? If not, why should it be > out of bounds? It used to work. The "old" kernel 5.3.7-200.fc30 > installed minutes earlier remains installed, and boots. I wouldn't > expect 5.3.7-301.fc31 to be materi

Re: The operation would result in removing the following protected packages: kernel-core, systemd

2019-10-24 Thread stan via test
On Thu, 24 Oct 2019 13:53:46 -0400 Felix Miata wrote: > Commands included: > > dnf system-upgrade download --refresh --releasever=31 > dnf system-upgrade download --refresh --releasever=31 --allowerasing > dnf system-upgrade download --refresh --releasever=31 --allowerasing > --best dnf system-u

Re: The operation would result in removing the following protected packages: kernel-core, systemd

2019-10-24 Thread Felix Miata
Adam Williamson composed on 2019-10-24 11:10 (UTC-0700): > On Thu, 2019-10-24 at 11:07 -0700, Samuel Sieb wrote: >> Felix Miata wrote: >> > $SUBJECT is the output. >> No, it's not. dnf prints out a lot more than that and to find out >> what's happening, we need to see it. How to find what yo

Re: The operation would result in removing the following protected packages: kernel-core, systemd

2019-10-24 Thread Felix Miata
Adam Williamson composed on 2019-10-24 11:10 (UTC-0700): > On Thu, 2019-10-24 at 11:07 -0700, Samuel Sieb wrote: >> Felix Miata wrote: >> > $SUBJECT is the output. >> No, it's not. dnf prints out a lot more than that and to find out >> what's happening, we need to see it. How to find what yo

Re: The operation would result in removing the following protected packages: kernel-core, systemd

2019-10-24 Thread Adam Williamson
On Thu, 2019-10-24 at 11:07 -0700, Samuel Sieb wrote: > On 10/24/19 10:53 AM, Felix Miata wrote: > > Samuel Sieb composed on 2019-10-24 08:15 (UTC-0700): > > > > > Felix Miata wrote: > > > > This has been rather routine here in recent weeks trying to > > > > system-upgrade to f31 > > > > from a f

Re: The operation would result in removing the following protected packages: kernel-core, systemd

2019-10-24 Thread Samuel Sieb
On 10/24/19 10:53 AM, Felix Miata wrote: Samuel Sieb composed on 2019-10-24 08:15 (UTC-0700): Felix Miata wrote: This has been rather routine here in recent weeks trying to system-upgrade to f31 from a freshly upgraded f30. This is with/without allowerasing and/or best and/or skip-broken o

Re: The operation would result in removing the following protected packages: kernel-core, systemd

2019-10-24 Thread Felix Miata
Samuel Sieb composed on 2019-10-24 08:15 (UTC-0700): > Felix Miata wrote: >> This has been rather routine here in recent weeks trying to system-upgrade >> to f31 >> from a freshly upgraded f30. This is with/without allowerasing and/or best >> and/or >> skip-broken options. Does it happen to oth

Re: The operation would result in removing the following protected packages: kernel-core, systemd

2019-10-24 Thread Samuel Sieb
On 10/23/19 9:30 PM, Felix Miata wrote: This has been rather routine here in recent weeks trying to system-upgrade to f31 from a freshly upgraded f30. This is with/without allowerasing and/or best and/or skip-broken options. Does it happen to others? Is there a known workaround? Is there a way

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

2019-10-24 Thread Fedora compose checker
No missing expected images. Failed openQA tests: 5/153 (x86_64), 1/2 (arm) New failures (same test not failed in Fedora-31-20191023.n.0): ID: 475942 Test: x86_64 KDE-live-iso apps_startstop URL: https://openqa.fedoraproject.org/tests/475942 ID: 476012 Test: x86_64 universal support_ser

Fedora 31 compose report: 20191024.n.0 changes

2019-10-24 Thread Fedora Branched Report
OLD: Fedora-31-20191023.n.0 NEW: Fedora-31-20191024.n.0 = SUMMARY = Added images:0 Dropped images: 1 Added packages: 0 Dropped packages:3 Upgraded packages: 2 Downgraded packages: 0 Size of added packages: 0 B Size of dropped packages:7.47 MiB Size of

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

2019-10-24 Thread Fedora compose checker
No missing expected images. Compose FAILS proposed Rawhide gating check! 4 of 45 required tests failed, 2 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.clo

Fedora rawhide compose report: 20191024.n.0 changes

2019-10-24 Thread Fedora Rawhide Report
OLD: Fedora-Rawhide-20191023.n.0 NEW: Fedora-Rawhide-20191024.n.0 = SUMMARY = Added images:1 Dropped images: 1 Added packages: 1 Dropped packages:23 Upgraded packages: 111 Downgraded packages: 0 Size of added packages: 12.27 MiB Size of dropped packages