Bug 858735
| Summary: | Revert timezone file every glibc-common update | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Bastien Nocera <bnocera> |
| Component: | systemd | Assignee: | systemd-maint |
| Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 18 | CC: | jakub, johannbg, kalevlember, law, lnykryn, lpoetter, metherid, msekleta, notting, pfrankli, plautrba, rjones, schwab, spoyarek, systemd-maint, vpavlin, yaneti |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-10-07 22:50:16 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: | |||
|
Description
Bastien Nocera
2012-09-19 14:22:35 UTC
Sounds like systemd screwup to me. /etc/localtime is owned by glibc and shouldn't be modified by other utilities. The right file for them to be updating is /etc/sysconfig/clock. (In reply to comment #2) > /etc/localtime is owned by glibc and shouldn't be modified by other > utilities. The right file for them to be updating is /etc/sysconfig/clock. And what will update /etc/localtime once I've changed /etc/sysconfig/clock? I was not aware that glibc is fiddling with /etc/localtime. We are trying to move everything over to use /etc/localtime now, and read /etc/sysconfig/clock only for compat reasons, but never update it. Jakub, can I convince you to drop the code %post code that overwrites the /etc/localtime symlink? Lennart, If y'all want systemd to own /etc/localtime, that's fine with me. It's a bit of a PITA anyway and I'm happy to drop it out of glibc. Let me know when you've updated systemd to own that file and I'll update glibc appropriately. jeff But note that you'll then need to deal with the upgrade consequences thereof, e.g. from the long times when /etc/localtime was a file copy instead of a symlink, so some %post needs to convert it from a file copy into a symlink depending on /etc/sysconfig/clock. And tools that change only /etc/localtime and not /etc/sysconfig/clock should be fixed anyway. (In reply to comment #3) > (In reply to comment #2) > > /etc/localtime is owned by glibc and shouldn't be modified by other > > utilities. The right file for them to be updating is /etc/sysconfig/clock. > > And what will update /etc/localtime once I've changed /etc/sysconfig/clock? I'm guessing that the answer is "reinstall glibc-common" after having changed /etc/sysconfig/clock. Those who live in glasshouses shouldn't be throwing stones. (In reply to comment #5) > Lennart, > > If y'all want systemd to own /etc/localtime, that's fine with me. It's a > bit of a PITA anyway and I'm happy to drop it out of glibc. > > Let me know when you've updated systemd to own that file and I'll update > glibc appropriately. I have now updated the RPM to take possession of /etc/localtime and to implement the symlink migration logic. It's in bodhi for F18 (systemd-190). systemd-190-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/systemd-190-1.fc18 I have also filed bugs against system-config-date and anaconda to stop creating /etc/sysconfig/clock. Excellent. From looking at the glibc.spec file something should own updating /var/spool/postfix/etc/localtime as well, presumably systemd. As far as I can tell, it should be a copy of /etc/localtime. I've got fresh glibc builds spinning. (In reply to comment #11) > Excellent. From looking at the glibc.spec file something should own > updating /var/spool/postfix/etc/localtime as well, presumably systemd. As > far as I can tell, it should be a copy of /etc/localtime. > > I've got fresh glibc builds spinning. Should probably be in the same update as systemd. Agreed. I've never had to issue an update with multiple packages. Do we just tack it on as another build to Lennart's existing update? If so, the right build is glibc-2.16-17.fc18. Package systemd-191-2.fc18, rtkit-0.11-3.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-191-2.fc18 rtkit-0.11-3.fc18' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-14581/rtkit-0.11-3.fc18,systemd-191-2.fc18 then log in and leave karma (feedback). Added the glibc update to the bodhi ticket! Thanks everybody! Package glibc-2.16-17.fc18, systemd-192-1.fc18, selinux-policy-3.11.1-23.fc18, rtkit-0.11-3.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing glibc-2.16-17.fc18 systemd-192-1.fc18 selinux-policy-3.11.1-23.fc18 rtkit-0.11-3.fc18' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-14581/selinux-policy-3.11.1-23.fc18,rtkit-0.11-3.fc18,systemd-192-1.fc18,glibc-2.16-17.fc18 then log in and leave karma (feedback). Package glibc-2.16-17.fc18, rtkit-0.11-3.fc18, systemd-193-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing glibc-2.16-17.fc18 rtkit-0.11-3.fc18 systemd-193-1.fc18' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-14581/rtkit-0.11-3.fc18,systemd-193-1.fc18,glibc-2.16-17.fc18 then log in and leave karma (feedback). |