Please branch and build pam_mount in epel9.
As suggested here https://docs.fedoraproject.org/en-US/epel/epel-package-request/ I ask once again: Will you be able to branch and build pam_mount in epel9?
I am not able to do this right now. I am happy with any other maintainer maintaining this in EPEL 9, so please go ahead and ask on epel-devel.
I'll branch it in a day or two, and update to latest upstream in this week.
Missing libHX. Now blocked by bug 2154296 .
*** Bug 2279680 has been marked as a duplicate of this bug. ***
libHX now appears to be in the EPEL 9 repo - is there any updates on building pam_mount? (Thanks for your help on this!)
Will you be able to branch and build pam_mount in epel9?
FEDORA-EPEL-2024-46ddeca2fa (pam_mount-2.20-2.el8) has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-46ddeca2fa
FEDORA-2024-3b34c10a54 (pam_mount-2.20-2.fc39) has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2024-3b34c10a54
FEDORA-EPEL-2024-872c6eb3ab (pam_mount-2.20-2.el9) has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-872c6eb3ab
FEDORA-2024-eb80af0d1e (pam_mount-2.20-2.fc40) has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2024-eb80af0d1e
FEDORA-EPEL-2024-872c6eb3ab 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-2024-872c6eb3ab See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-3b34c10a54 has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-3b34c10a54` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-3b34c10a54 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-cd7105063c has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-cd7105063c` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-cd7105063c See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-eb80af0d1e has been pushed to the Fedora 40 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-eb80af0d1e` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-eb80af0d1e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2024-46ddeca2fa 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-2024-46ddeca2fa See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2024-872c6eb3ab (pam_mount-2.20-2.el9) has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2024-3b34c10a54 (pam_mount-2.20-2.fc39) has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2024-eb80af0d1e (pam_mount-2.20-2.fc40) has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2024-46ddeca2fa (pam_mount-2.20-2.el8) has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report.
It is still not possible to install pam_mount because hxtools are missing: dnf install pam_mount.x86_64 Last metadata expiration check: 0:13:04 ago on Fri Sep 13 07:56:53 2024. Error: Problem: conflicting requests - nothing provides hxtools needed by pam_mount-2.20-2.el9.x86_64 from epel (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
FEDORA-2024-cd7105063c (pam_mount-2.20-2.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.
Really sad. Now blocked by bug 2312323
For posterity, this is the problem causing this bug to depend on bug 2312323. Error: Problem: conflicting requests - nothing provides hxtools needed by pam_mount-2.20-2.el9.x86_64 from epel In case you weren't aware, there is an unfortunate feature gap in bodhi currently. If you look at the "automated tests" tab of a Fedora update, there is an item for fedora-ci.koji-build.installability.functional. This is non-blocking, but it does at least provide a visual indicator of a failed test. However, this installability check is not even run for EPEL updates. I've been asking for this to be fixed for a while, but so far I haven't been able to make progress on it. I'd like to get that check run for EPEL, and ideally even have a failing check cause the automatic push by time/karma to be disabled. Until then, please ensure that EPEL updates are manually installable before allowing them to push to stable.
Meanwhile, to make the situation more misery, fedora-ci on el8 is broken and will always fail because of EOL of centos-8-stream. Encountered it when I'm trying to PR. https://github.com/fedora-ci/installability-pipeline/issues/40
That's actually the same root problem. The Fedora CI team says they don't have access to RHEL, which is probably why they used CentOS Stream 8. I warned them checking EPEL 8 updates with CentOS Stream 8 would lead to both false positives and false negatives, but it appears that warning was ignored. The shorter lifecycle is another reason why it's not a valid solution.
@Carl George Besides that, stream contains beta releases which is not identical with RHEL. Really not a solid ground to stand on. And sadly the issue hasn't got any notice from the developer of pipelines after half a month.
CentOS Stream is the major version branch of RHEL, so it is quite solid ground to stand on. We built the initial set of EPEL 9 packages with it before RHEL 9 was available. EPEL 10 is building against it as well, and will continue to build against it even after RHEL 10 is available because of changes in the architecture. https://discussion.fedoraproject.org/t/epel-10-proposal/44304 The problem with it from the CI perspective is not that it's unstable or contains beta releases (neither of which are true), it's that it has reflects the content of a different minor version (one minor version ahead of RHEL), and has a shorter lifecycle than RHEL (5.5 versus 10 years). We need both available in CI, used at different times, to test things correctly.