Would be nice to have it on EPEL 9
Will you be able to branch and build munin in epel9?
FEDORA-EPEL-2022-921b01f72f has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-921b01f72f
FEDORA-2022-e29734a743 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-e29734a743
FEDORA-2022-cd5df20ab1 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-cd5df20ab1
FEDORA-EPEL-2022-25ceadbf26 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-25ceadbf26
FEDORA-EPEL-2022-3e07cbe62c has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-3e07cbe62c
Please test EPEL 9 build, I don't have any test system available right now.
FEDORA-EPEL-2022-25ceadbf26 has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-25ceadbf26 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
I installed this from epel testing, and it looks to be working well. The only issue I ran into was an error with the munin-node package, where I encountered an error like this: Error in tempfile() using template /var/lib/munin/plugin-state/root/XXXXXXXXXX: Could not create temp file /var/lib/munin/plugin-state/root/2Onyek2qTp: Permission denied Which I resolved like this: chown root /var/lib/munin/plugin-state/root My test system is like this: [root@testbox ~]# uname -a Linux testbox 5.14.0-70.17.1.el9_0.x86_64 #1 SMP PREEMPT Tue Jun 14 11:32:10 EDT 2022 x86_64 x86_64 x86_64 GNU/Linux [root@testbox ~]# cat /etc/*release NAME="Red Hat Enterprise Linux" VERSION="9.0 (Plow)" ID="rhel" ID_LIKE="fedora" VERSION_ID="9.0" PLATFORM_ID="platform:el9" PRETTY_NAME="Red Hat Enterprise Linux 9.0 (Plow)" ANSI_COLOR="0;31" LOGO="fedora-logo-icon" CPE_NAME="cpe:/o:redhat:enterprise_linux:9::baseos" HOME_URL="https://www.redhat.com/" DOCUMENTATION_URL="https://access.redhat.com/documentation/red_hat_enterprise_linux/9/" BUG_REPORT_URL="https://bugzilla.redhat.com/" REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 9" REDHAT_BUGZILLA_PRODUCT_VERSION=9.0 REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux" REDHAT_SUPPORT_PRODUCT_VERSION="9.0" Red Hat Enterprise Linux release 9.0 (Plow) Red Hat Enterprise Linux release 9.0 (Plow
> Error in tempfile() using template > /var/lib/munin/plugin-state/root/XXXXXXXXXX: Could not create temp file > /var/lib/munin/plugin-state/root/2Onyek2qTp: Permission denied > > Which I resolved like this: > > chown root /var/lib/munin/plugin-state/root Interesting. Do you remember who was the owner before chown? Spec file says: %attr(-, root, root) %dir %{_sharedstatedir}/munin/plugin-state/root So it should be root:root.
That is interesting, the spec file looks correct. On my system, it was owned by munin:munin.
I installed on a fresh test box and the ownership of /var/lib/munin/plugin-state/root was correct (root:root), so this may have been an issue with the test box I used the first time.
I installed Alma Linux 9 and tested it. Owner for /var/lib/munin/plugin-state/root is root:root. Could you please verify owner of /var/lib/munin/plugin-state directory on both of your test boxes? It should also be root:root. There's actually a small problem with this directory. It should be /var/lib/munin-node/plugin-state but SElinux doesn't allow it. I could semanage-fix it on install but I'm bit lazy... As long as /var/lib/munin/plugin-state works I'll keep it as it is.
Here's what I have: [root@testbox1-rhel-9 ~]# ls -la /var/lib/munin/plugin-state total 0 drwxr-xr-x. 5 root root 45 Jul 21 10:31 . drwxr-xr-x. 5 munin munin 51 Jul 21 10:29 .. drwxr-xr-x. 2 munin munin 6 Jul 20 12:58 munin drwxr-xr-x. 2 root munin 6 Jul 20 12:58 root [root@testbox2-rhel-9 ~]# ls -la /var/lib/munin/plugin-state total 0 drwxr-xr-x. 5 root root 45 Jul 21 10:31 . drwxr-xr-x. 5 munin munin 51 Jul 21 10:29 .. drwxr-xr-x. 2 munin munin 6 Jul 20 12:58 munin drwxr-xr-x. 2 root munin 6 Jul 20 12:58 root
FEDORA-EPEL-2022-3e07cbe62c has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-3e07cbe62c See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2022-921b01f72f has been pushed to the Fedora EPEL 7 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-921b01f72f See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
> drwxr-xr-x. 2 munin munin 6 Jul 20 12:58 munin > drwxr-xr-x. 2 root munin 6 Jul 20 12:58 root That's strange. After rpm install they should be: [root@guest-00-vm ~]# ls -la /var/lib/munin/plugin-state total 0 drwxr-xr-x. 4 root root 31 Jul 21 17:44 . drwxr-xr-x. 5 munin munin 51 Jul 21 17:44 .. drwxr-xr-x. 2 munin root 6 Jul 20 19:58 munin drwxr-xr-x. 2 root root 6 Jul 20 19:58 root I guess they were deleted accidentally or by some program. Maybe by rhel9's systemd tmpfilesd? Munin-node will create them with group=munin if they are missing. Oh well, I'll move plugin-state to /var/lib/munin-node, just to make things easier later on.
FEDORA-2022-cd5df20ab1 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-cd5df20ab1` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-cd5df20ab1 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-e29734a743 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-e29734a743` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-e29734a743 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-d5e6bb81f1 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-d5e6bb81f1
FEDORA-2022-25ec0f4293 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-25ec0f4293
FEDORA-EPEL-2022-5ca4e29abd has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-5ca4e29abd
FEDORA-EPEL-2022-3feef95cf0 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-3feef95cf0
> [root@guest-00-vm ~]# ls -la /var/lib/munin/plugin-state > total 0 > drwxr-xr-x. 4 root root 31 Jul 21 17:44 . > drwxr-xr-x. 2 munin root 6 Jul 20 19:58 munin > drwxr-xr-x. 2 root root 6 Jul 20 19:58 root ... > Oh well, I'll move plugin-state to /var/lib/munin-node, just to make things > easier later on. This is now done in -5 release. Are your /var/lib/munin-node and /var/lib/munin-node/plugin-state now root:root, and subdirs as above?
Yes, the ownership looks correct.
FEDORA-2022-25ec0f4293 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-25ec0f4293` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-25ec0f4293 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2022-9ad121d6a3 has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-9ad121d6a3 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-d5e6bb81f1 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-d5e6bb81f1` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-d5e6bb81f1 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2022-5ca4e29abd has been pushed to the Fedora EPEL 7 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-5ca4e29abd See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2022-3feef95cf0 has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-3feef95cf0 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-25ec0f4293 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2022-9ad121d6a3 has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2022-3feef95cf0 has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2022-5ca4e29abd has been pushed to the Fedora EPEL 7 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-d5e6bb81f1 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.