Bug 1170146 - systemd: /usr/share/factory/etc contains inconsistent data
systemd: /usr/share/factory/etc contains inconsistent data
Status: RESOLVED FIXED
Classification: openSUSE
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Basesystem
Current
Other Other
: P5 - None : Normal (vote)
: ---
Assigned To: systemd maintainers
E-mail List
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2020-04-22 07:40 UTC by Ludwig Nussel
Modified: 2020-12-23 08:49 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ludwig Nussel 2020-04-22 07:40:06 UTC
systemd ships several files in /usr/share/factory/etc that are copied to /etc in case those files are missing there. Unfortunately the content does not match the defaults we normally have.

I'd suggest to simply not ship those files in the systemd package but leave the decision to use the mechanism to the individual packages that actually consume those configs (like glibc or pam).
Comment 1 Franck Bui 2020-04-23 13:29:45 UTC
(In reply to Ludwig Nussel from comment #0)
> systemd ships several files in /usr/share/factory/etc that are copied to
> /etc in case those files are missing there. Unfortunately the content does
> not match the defaults we normally have.

Which makes me think that we still haven't solved bsc#1078466...

Wouldn't also make sense for systemd to stop shipping /usr/lib/tmpfiles.d/etc.conf ?
Comment 2 Ludwig Nussel 2020-04-23 14:10:29 UTC
fine with me
Comment 3 Franck Bui 2020-04-23 14:16:03 UTC
but who's gonna take care of the creations of /etc/os-release and /etc/mtab symlinks ?
Comment 4 Ludwig Nussel 2020-04-23 14:24:40 UTC
/etc/os-release is owned by openSUSE-release. /etc/mtab is legacy. mount works without it. I guess we can try without it.
Comment 5 Franck Bui 2020-05-04 06:51:25 UTC
(In reply to Ludwig Nussel from comment #0)
> I'd suggest to simply not ship those files in the systemd package but leave
> the decision to use the mechanism to the individual packages that actually
> consume those configs (like glibc or pam).

Done and let individual packages choose the content of the files used by the factory-reset mechanism (as well as the associated tmpfiles config files).

Thanks.