A bug in RCS causes filtering locked files by username to not work, this was patched by Redhat in RHEL7 [1] but not filtered upstream to Fedora or GNU [2]. I mirrored the Fedora package [3] in my organization local Gitlab, added this patch to the epel9 branch and bumped the Epoch and Release numbers so my in-house build will override the Fedora EPEL one, and the patch applied cleanly and fixed the problem. It's a pretty small and straightforward patch, so whether it gets applied upstream or local to Fedora probably depends on the availability of maintainers and willingness to bump the minor version in EPEL if upstream is responsive and cuts a v5.10.2. # incorrect behavior, showing locked files by both mtinberg and bbadger [mtinberg@rhel9 rcs-test]$ rcs log -L -R -lmtinberg *,v test-locked-bbadger-author-bbadger,v test-locked-bbadger-author-mtinberg,v test-locked-mtinberg-author-bbadger,v test-locked-mtinberg-author-mtinberg,v # upgrade to local build Upgrading : rcs-1:5.10.1-4.el9.x86_64 1/2 Cleanup : rcs-5.10.1-3.el9.x86_64 # correct behavior, only showing files locked by mtinberg [mtinberg@rhel9 rcs-test]$ rcs log -L -R -lmtinberg *,v test-locked-mtinberg-author-bbadger,v test-locked-mtinberg-author-mtinberg,v - [1] https://bugzilla.redhat.com/show_bug.cgi?id=1696716 - [2] https://savannah.gnu.org/bugs/index.php?67093 - [3] https://src.fedoraproject.org/rpms/rcs.git
Seems also minor and obvious to me. Will patch it downstream in the meantime.
FEDORA-EPEL-2025-c4025d0c28 (rcs-5.10.1-12.el9) has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-c4025d0c28
FEDORA-EPEL-2025-e17f3e5c3c (rcs-5.10.1-12.el8) has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-e17f3e5c3c
FEDORA-2025-425fad2f25 (rcs-5.10.1-12.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2025-425fad2f25
FEDORA-2025-6348b37c7f has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-6348b37c7f` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-6348b37c7f See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2025-e17f3e5c3c 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-2025-e17f3e5c3c See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2025-c4025d0c28 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-2025-c4025d0c28 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-425fad2f25 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-2025-425fad2f25` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-425fad2f25 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2025-e17f3e5c3c (rcs-5.10.1-12.el8) 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-2025-c4025d0c28 (rcs-5.10.1-12.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-2025-425fad2f25 (rcs-5.10.1-12.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2025-6348b37c7f (rcs-5.10.1-12.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.