Why did that lower the version number? The previous release was 0.20.3, this is now 0.20.1. dnf won't downgrade by default. Can you please fix the version number?
Works out of the box under wayland, even in toolbox. Nice one, thanks Major!
Nack, this breaks kdump. After an opps, the crash dump is not generated, and kdump.service fails:
● kdump.service - Crash recovery kernel arming
Loaded: loaded (/usr/lib/systemd/system/kdump.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Fri 2021-05-21 04:48:50 UTC; 23s ago
Process: 582 ExecStart=/usr/bin/kdumpctl start (code=exited, status=1/FAILURE)
Main PID: 582 (code=exited, status=1/FAILURE)
CPU: 185ms
May 21 04:48:49 localhost systemd[1]: Starting Crash recovery kernel arming...
May 21 04:48:50 localhost kdumpctl[896]: /usr/lib/dracut/dracut-functions.sh: line 237: get_maj_min_cache_file: parameter null or not set
May 21 04:48:50 localhost kdumpctl[895]: /usr/lib/dracut/dracut-functions.sh: line 241: get_maj_min_cache_file: parameter null or not set
May 21 04:48:50 localhost kdumpctl[902]: /usr/bin/kdumpctl: line 504: perror: command not found
May 21 04:48:50 localhost kdumpctl[598]: kdump: Starting kdump: [FAILED]
May 21 04:48:50 localhost systemd[1]: kdump.service: Main process exited, code=exited, status=1/FAILURE
May 21 04:48:50 localhost systemd[1]: kdump.service: Failed with result 'exit-code'.
May 21 04:48:50 localhost systemd[1]: Failed to start Crash recovery kernel arming.
Installs, upgrades, and works fine. VM deletion crash is fixed.
Installs, upgrades, and works fine. Deletion crash is fixed.
Install and upgrade from 242-1 went fine. I went through all the pages, and they behave as expected.
I just pushed a new build in FEDORA-2021-811491ace1 that fixes the file conflict with selinux-policy-doc.
First I upgraded to Fedora 34 (as the coreos/testing branch is still F33):
ostree rebase fedora:fedora/x86_64/coreos/next
reboot
Then I confirmed the bug with current F34 dpkg:
rpm-ostree install dpkg
# [..]
# error: Running %post for dpkg: bwrap(/bin/sh): Child process killed by signal 1; run `journalctl -t 'rpm-ostree(dpkg.post)'` for more information
Test the proposed update:
rpm-ostree install https://kojipkgs.fedoraproject.org//packages/dpkg/1.20.7.1/2.fc34/x86_64/dpkg-1.20.7.1-2.fc34.x86_64.rpm
# succeeded!
reboot
dpkg --help
Cheers!
Investigating in https://github.com/cockpit-project/cockpit-machines/pull/110 , this smells like a regression in libvirt 7.2.0
previous CI run failure flaked TestMachinesNICs.testNICAdd
. Retrying for comparison.
I downloaded from the current 241-1.fc34 to 242.1-1.fc34. The upgrade worked fine, the Page works, and there is no visual difference (as intended).
Confirming that this package works well together with the new tmt in https://copr.fedorainfracloud.org/coprs/frantisekz/testcloud-wip/packages/ for running in toolbox with session qemu. Splendid, thank you!
I ran all of cockpit's realmd tests (FreeIPA and AD) against this update, and it works fine again. Thank you!
@kalev: Ack, sorry about that. Thank you! I rebuilt my tree with -8, and firefox works.
New package dropped the libXt dependency, which is still needed. Firefox does not start up any more. Reported as https://bugzilla.redhat.com/show_bug.cgi?id=1922935
Thanks a lot @spot for your work in maintaining chromium. I can assure you that we (cockpit team) depend on having a good Chromium Fedora package, and that your effort is much appreciated!
Honestly I have a hard time shedding a lot of emotions about this. People who care about not using Google proprietary stuff (like me, although I use Firefox on desktop and phone) shouldn't/won't use the proprietary bookmark sync either; and people who don't care will either not care much about using chrome vs. chromium?
My current fedora-32 VM still has pam-1.3.1-28.fc32.x86_64. I don't see the root:wheel/0640 cockpit motd for neither unprivileged nor wheel users.
Upgrading to pam 1.3.1-29.fc32 in updates, same result.
Upgrading to 1.3.1-30.fc32 in updates-testing (this bodhi update), I see the motd for a wheel user, but not for an unpriv user. So this works exactly as advertised. Thank you!
Without this fix, the upgrade fails:
$ podman run -it --rm registry.fedoraproject.org/f33/fedora-toolbox:33 dnf install -y vim
[..]
Error: Transaction test error:
file /etc/profile.d/vim.sh from install of vim-enhanced-2:8.2.2115-1.fc33.x86_64 conflicts with file from package vim-minimal-2:8.2.1885-1.fc33.x86_64
With this fix, it works fine:
$ podman run -it --rm registry.fedoraproject.org/f33/fedora-toolbox:33 dnf install --enablerepo=updates-testing -y vim
[...]
Preparing : 1/1
Installing : gpm-libs-1.20.7-24.fc33.x86_64 1/6
Installing : vim-filesystem-2:8.2.2143-1.fc33.noarch 2/6
Installing : vim-common-2:8.2.2143-1.fc33.x86_64 3/6
Installing : vim-enhanced-2:8.2.2143-1.fc33.x86_64 4/6
Upgrading : vim-minimal-2:8.2.2143-1.fc33.x86_64 5/6
Cleanup : vim-minimal-2:8.2.1885-1.fc33.x86_64 6/6
Running scriptlet: vim-minimal-2:8.2.1885-1.fc33.x86_64 6/6
Verifying : vim-common-2:8.2.2143-1.fc33.x86_64 1/6
Verifying : vim-enhanced-2:8.2.2143-1.fc33.x86_64 2/6
Verifying : vim-filesystem-2:8.2.2143-1.fc33.noarch 3/6
Verifying : gpm-libs-1.20.7-24.fc33.x86_64 4/6
Verifying : vim-minimal-2:8.2.2143-1.fc33.x86_64 5/6
Verifying : vim-minimal-2:8.2.1885-1.fc33.x86_64 6/6
Upgraded:
vim-minimal-2:8.2.2143-1.fc33.x86_64
Installed:
gpm-libs-1.20.7-24.fc33.x86_64 vim-common-2:8.2.2143-1.fc33.x86_64 vim-enhanced-2:8.2.2143-1.fc33.x86_64
vim-filesystem-2:8.2.2143-1.fc33.noarch
Thanks!
Missing comma in this commit:
--- /usr/share/containers/seccomp.json 1970-01-01 01:00:00.000000000 +0100
+++ /tmp/seccomp.json 2020-10-25 20:09:18.724815976 +0100
@@ -760,7 +760,7 @@
"names": [
"settimeofday",
"stime",
- "clock_settime"
+ "clock_settime",
"clock_settime64"
],
"action": "SCMP_ACT_ALLOW",
Still doesn't work. Upgrading from Fedora 34 picks up the higher version number: