Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: pam_mount from EPEL 9 has one or more unresolved dependencies, causing it to be uninstallable. Version-Release number of selected component (if applicable): pam_mount-2.20-2.el9 How reproducible: always Steps to Reproduce: 1. dnf install pam_mount Actual results: Error: Problem: conflicting requests - nothing provides hxtools needed by pam_mount-2.20-2.el9.x86_64 from epel Expected results: successful installation
Gonna deal with it soon. Last time the dependency FTBFS because of errors in infrastructure of ARM, and I forgot about it.
hxtools scratch builds from both the rawhide and epel9 branches now succeed on all architectures. https://koji.fedoraproject.org/koji/taskinfo?taskID=145972000 https://koji.fedoraproject.org/koji/taskinfo?taskID=145972038 Is there a reason why the epel9 branch has a newer version than the rawhide branch? That's not appropriate, rawhide should be updated to a newer version first, then older branches can be fast-forwarded as needed (within the limits of the update policies).
Because the original maintainer is missing and I only got access to epel branches.
You should at least attempt to get the update into rawhide first via pull request. Even if the maintainer doesn't respond, a proven packager can merge the pull request and create a build. Updating epel9 to a newer version before rawhide just because you have access to that branch isn't the right approach. If the maintainer isn't reachable at all, you can use the non-responsive maintainer process to orphan their packages so that other maintainers such as yourself can adopt them. That involves several steps where the maintainer can speak up and retain control. https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/ Alternatively, there is a lightweight process to just get access to a single package. https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/#stalled-request-process
I've untagged pam_mount-2.20-2.el9 to remove the uninstallable package from the repos. If you're able to get the dependencies sorted out, you can re-add pam_mount by creating a new build and submitting a bodhi update for it. If you're not able to fix this, then please follow the steps below to retire the epel9 branch. https://docs.fedoraproject.org/en-US/epel/epel-policy-retirement/#process_no_time_or_desire