Bug 1149569 - doesn't include /usr/lib/os-release
Summary: doesn't include /usr/lib/os-release
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 21
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1149568
TreeView+ depends on / blocked
 
Reported: 2014-10-06 05:59 UTC by Rahul Sundaram
Modified: 2015-01-31 16:57 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-01-31 16:57:17 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Rahul Sundaram 2014-10-06 05:59:58 UTC 
Description of problem:

according to the man page, /etc/os-release should be a symlink to /usr/lib/os-release.  however the latter file is not included by systemd

fedora-release bug report to create the symlink

https://bugzilla.redhat.com/show_bug.cgi?id=1149568
Comment 1 Zbigniew Jędrzejewski-Szmek 2014-10-07 12:36:22 UTC 
I think that the /etc/os-release link should be packaged in fedora-release*, because the /usr/lib/os-release file is there.
Comment 2 Rahul Sundaram 2014-10-07 12:44:38 UTC 
I am not sure how to parse that.  fedora-release does NOT have /usr/lib/os-release

rpm -ql fedora-release
/etc/fedora-release
/etc/issue
/etc/issue.net
/etc/os-release
/etc/redhat-release
/etc/system-release
/etc/system-release-cpe
/usr/lib/rpm/macros.d/macros.dist
/usr/share/licenses/fedora-release
/usr/share/licenses/fedora-release/Fedora-Legal-README.txt
/usr/share/licenses/fedora-release/LICENSE

Dennis (see the linked bug report) is of the opinion that /etc/os-release not being a symlink isn't a problem.
Comment 3 Rahul Sundaram 2014-10-07 12:45:54 UTC 
Oh, never mind.  I see that you have already commented on the linked bug report.
Comment 4 Zbigniew Jędrzejewski-Szmek 2015-01-31 16:57:17 UTC 
I still think this should go into fedora-release. Let's pursue it there.
Note You need to log in before you can comment on or make changes to this bug.