Thanks for noticing the version switcheroo. Something is off with bodhi: it proposed just this .f42 build, and I clicked on it without looking too closely.
- file /usr/libexec/p7zip from install of 7zip-24.09-3.fc43.x86_64 conflicts with file from package p7zip-plugins-16.02-32.fc42.x86_64
dmraid will be handled by https://src.fedoraproject.org/rpms/fedora-obsolete-packages/pull-request/111 and https://src.fedoraproject.org/rpms/fedora-obsolete-packages/pull-request/112. I'm waiting for an answer there.
Thanks, with the new build the warning is gone.
The test fails with
Traceback (most recent call last):
File "/var/ARTIFACTS/work-stsjwsj35vq/plans/sts/discover/default-0/tests/tests/iscsi/parameters/iscsi_params.py", line 10, in <module>
from sts import fio, iscsi, linux, lio, mp, scsi
ImportError: cannot import name 'linux' from 'sts' (/opt/sts-venv/lib64/python3.13/site-packages/sts/__init__.py)
Shared connection to 18.220.145.144 closed.
I asked in fedora-ci, and got the reply that:
Seems like an issue with the package test themselves probably outdated from https://gitlab.com/rh-kernel-stqe/sts/-/blob/fedora/tests/iscsi/parameters/iscsi_params.py?ref_type=heads
I'll waive the tests.
This upgrade has borked udev rules, causing udev to complain on every rule reload:
systemd-udevd[731687]: /usr/lib/udev/rules.d/61-gdm.rules:39 GOTO="gdm_disable_wayland" has no matching label, ignoring. systemd-udevd[731687]: /usr/lib/udev/rules.d/61-gdm.rules:39 The line has no effect any more, dropping.
Please fix ;)
I also started criu-4.0-4.fc43 for rawhide so that we get the update in both places.
I'm not sure if the tests will run properly. I results seem to have disappeared and the jenkins page doesn't allow me to restart the run. If criu-4.0-4.fc43 passes, then I'll just waive the one failed test result.
This update was unushed to avoid weiredness around branching. Submitting it again.
This update has been unpushed.
As discussed in https://github.com/fedora-silverblue/issue-tracker/issues/636, rpm-ostree does not support sysusers yet, and needs the compat macros. So let's not push this change in systemd to F42 yet. I'll drop this update and rebuild with the macro restored.
I cannot find any logs from the purported upgrade attempt. I looked at the various attached files and the compressed /var/log directory with the journal file…
I have no idea why the tests would fail. It's the exact same spec as for rawhide, and there the tests passed. And the packages install fine here on my laptop. The logs in the QA output don't seem to contain any useful information, unless I'm just looking in the wrong place.
But there is nothing pressing in this update. It's completely fine if it waits a few days.
OK, most of the tests passed. There are two failed mandatory tests and one that is still running. The ones that failed failed because of infra problems. This rebuild just adds some additional audit events, and I don't think our CI even tests any of this, so I'll waive the results.
503 for https://pagure.io/fedora-kickstarts.git :(
:: [ 10:24:09 ] :: [ BEGIN ] :: Verifying package 'filesystem' :: actually running 'rpm -V filesystem'
.M....... g /usr/sbin
:: [ 10:24:09 ] :: [ FAIL ] :: Verifying package 'filesystem' (Expected 0, got 1)
This is a real failure. On upgraded systems /usr/sbin will be directory, not a symlink. I guess we could try to somehow adjust the %files list in filesystem. But this is not a regression in this update, but a pre-existing problem that only surfaced now when the tests are running properly again.
⚠ Guest couldn't be provisioned: Artemis resource ended in 'error' state
I don't think this is caused by the changes in this build.
{"status": "error", "errors": [{"location": "querystring", "name": "update", "description": "Cannot submit rpm ('0', '4.20.0', '4.fc42') to stable since it is older than ('0', '4.20.0', '5.fc42')"}]}
Yikes.
Problem 1: package coreutils-9.5-12.fc42.x86_64 from @commandline conflicts with coreutils-single provided by coreutils-single-9.5-12.fc42.x86_64 from @commandline - conflicting requests Problem 2: package systemd-257.2-7.fc42.x86_64 from @commandline conflicts with systemd-standalone-tmpfiles provided by systemd-standalone-tmpfiles-257.2-7.fc42.x86_64 from @commandline - conflicting requests Problem 3: package systemd-standalone-repart-257.2-7.fc42.x86_64 from @commandline conflicts with systemd-udev provided by systemd-udev-257.2-7.fc42.x86_64 from @commandline - conflicting requests Problem 4: package systemd-257.2-7.fc42.x86_64 from @commandline conflicts with systemd-standalone-shutdown provided by systemd-standalone-shutdown-257.2-7.fc42.x86_64 from @commandline - package systemd-container-257.2-7.fc42.x86_64 from @commandline requires libsystemd-shared-257.2-7.fc42.so()(64bit), but none of the providers can be installed - package systemd-container-257.2-7.fc42.x86_64 from @commandline requires libsystemd-shared-257.2-7.fc42.so(SD_SHARED)(64bit), but none of the providers can be installed - package systemd-container-257.2-7.fc42.x86_64 from @commandline requires systemd(x86-64) = 257.2-7.fc42, but none of the providers can be installed - conflicting requests Problem 5: package systemd-257.2-7.fc42.x86_64 from @commandline conflicts with systemd-standalone-sysusers provided by systemd-standalone-sysusers-257.2-7.fc42.x86_64 from @commandline - package systemd-journal-remote-257.2-7.fc42.x86_64 from @commandline requires libsystemd-shared-257.2-7.fc42.so()(64bit), but none of the providers can be installed - package systemd-journal-remote-257.2-7.fc42.x86_64 from @commandline requires libsystemd-shared-257.2-7.fc42.so(SD_SHARED)(64bit), but none of the providers can be installed - package systemd-journal-remote-257.2-7.fc42.x86_64 from @commandline requires systemd(x86-64) = 257.2-7.fc42, but none of the providers can be installed - conflicting requests Problem 6: package glusterfs-resource-agents-11.1-7.fc42.noarch from @commandline requires resource-agents, but none of the providers can be installed - package resource-agents-4.16.0-1.fc42.x86_64 from testing-farm-tag-repository requires /usr/sbin/mount.nfs, but none of the providers can be installed - package resource-agents-4.16.0-1.fc42.x86_64 from testing-farm-tag-repository requires /usr/sbin/mount.nfs4, but none of the providers can be installed - package resource-agents-4.16.0-1.fc42.x86_64 from rawhide requires /usr/sbin/mount.nfs, but none of the providers can be installed - package resource-agents-4.16.0-1.fc42.x86_64 from rawhide requires /usr/sbin/mount.nfs4, but none of the providers can be installed - cannot install both nfsv4-client-utils-1:2.8.2-0.rc1.fc42.1.x86_64 from @commandline and nfsv4-client-utils-1:2.8.2-0.rc1.fc42.x86_64 from testing-farm-tag-repository - cannot install both nfsv4-client-utils-1:2.8.2-0.rc1.fc42.1.x86_64 from @commandline and nfsv4-client-utils-1:2.8.2-0.rc1.fc42.x86_64 from rawhide - cannot install both nfs-utils-coreos-1:2.8.2-0.rc1.fc42.1.x86_64 from @commandline and nfs-utils-coreos-1:2.8.2-0.rc1.fc42.x86_64 from testing-farm-tag-repository - cannot install both nfs-utils-coreos-1:2.8.2-0.rc1.fc42.1.x86_64 from @commandline and nfs-utils-coreos-1:2.8.2-0.rc1.fc42.x86_64 from rawhide - cannot install both nfs-utils-1:2.8.2-0.rc1.fc42.1.x86_64 from @commandline and nfs-utils-1:2.8.2-0.rc1.fc42.x86_64 from testing-farm-tag-repository - cannot install both nfs-utils-1:2.8.2-0.rc1.fc42.1.x86_64 from @commandline and nfs-utils-1:2.8.2-0.rc1.fc42.x86_64 from rawhide - conflicting requests
1–5 are bogus, but 6 is a real problem. I'll rebuild nfs-utils with more compat provides.
This update has been unpushed.
https://github.com/fedora-selinux/selinux-policy/pull/2716