Bug 1968131
| Summary: | setup and pam have conflict for motd.d | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | James Caldwell <forummail> | ||||||
| Component: | pam | Assignee: | Iker Pedrosa <ipedrosa> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | low | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 34 | CC: | besser82, ipedrosa, karsten, ovasik, pknirsch, pzhukov, tm | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | pam-1.5.2-5.fc35 pam-1.5.1-7.fc34 | Doc Type: | If docs needed, set a value | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2021-09-24 20:32:35 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
Created attachment 1789083 [details]
pam.conf
motd.d ownership was added in PAM 2 years back to resolve https://src.fedoraproject.org/rpms/pam/c/0686daa3fa1c4b4bd24fcf68f8dbcd66d22f44d6?branch=rawhide . At aproximately same time, ownership was added in setup too - https://src.fedoraproject.org/rpms/setup/c/1807a3ca2a00671b0bdb167b401d4f50428d2399?branch=rawhide . My slight preference would be to keep motd.d ownership in setup and revert the ownership in pam, as setup owns (empty) /etc/motd file. However, if pam maintainer prefers to keep it himself, I can drop the ownership in setup. Adding needinfo on him. I agree that the ownership of /etc/motd.d folder should be kept in setup. I'll revert the changes in pam so that the two packages don't collide. FEDORA-2021-42d44e4441 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-42d44e4441 FEDORA-2021-42d44e4441 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-42d44e4441 FEDORA-2021-42d44e4441 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 --advisory=FEDORA-2021-42d44e4441` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-42d44e4441 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2021-42d44e4441 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report. Thank you all that was fantastic to watch. I am grateful to the Fedora developers and community for all of your efforts. FEDORA-2021-549a8efd8c has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-549a8efd8c FEDORA-2021-549a8efd8c has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-549a8efd8c` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-549a8efd8c See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2021-549a8efd8c has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report. |
Created attachment 1789082 [details] setup.conf Description of problem: This is most likely a minor or trivial message. I noticed this error when installing an update. Version-Release number of selected component (if applicable): setup-2.13.7-3.fc34.noarch pam-1.5.1-5.fc34.x86_64 How reproducible: Always when reinstalling setup. Other packages may trigger it but I could not find out which. I did not wish to reinstall pam due to risk aversion. Steps to Reproduce: 1. Reinstall the setup package. 2. 3. Actual results: reinstall setup-2.13.7-3.fc34.noarch.rpm ... Running scriptlet: setup-2.13.7-3.fc34.noarch Cleanup : setup-2.13.7-3.fc34.noarch Running scriptlet: setup-2.13.7-3.fc34.noarch /usr/lib/tmpfiles.d/pam.conf:4: Duplicate line for path "/run/motd.d", ignoring. /usr/lib/tmpfiles.d/setup.conf:2: Duplicate line for path "/run/motd.d", ignoring. Expected results: No error. Additional info: Both conf entries for the motd.d directory are identical. I checked the directory and something is creating it with the same 755 permission.