[Bug 1209208] New: Postgresql server pulls in systemd
https://bugzilla.suse.com/show_bug.cgi?id=1209208 Bug ID: 1209208 Summary: Postgresql server pulls in systemd Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs@suse.de Reporter: dcermak@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- The postgresql-server package depends on systemd, which is a small annoyance for the BCI containers: we build a postgres server container, where we don't need systemd to be installed. Would it be possible to split the server subpackage into server and server-systemd or something along those lines, so that we can install only postgres-server and don't end up with systemd inside the container as well? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1209208 Dan ��erm��k <dcermak@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dcermak@suse.com Assignee|screening-team-bugs@suse.de |max@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1209208 Dan ��erm��k <dcermak@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|dcermak@suse.com |bci-internal@suse.de -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1209208 https://bugzilla.suse.com/show_bug.cgi?id=1209208#c1 --- Comment #1 from Reinhard Max <max@suse.com> --- I'd like to avoid scattering the PostgreSQL packages even more. Is it really needed to split the package for this, or would it be enough to drop the explicit systemd dependency, but keep shipping the service file in the server package? I guess there is no real need for PostgreSQL to hard require systemd, because it will be part of the base system on installations that need it. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1209208 https://bugzilla.suse.com/show_bug.cgi?id=1209208#c2 --- Comment #2 from Dan ��erm��k <dcermak@suse.com> --- (In reply to Reinhard Max from comment #1)
I'd like to avoid scattering the PostgreSQL packages even more. Is it really needed to split the package for this, or would it be enough to drop the explicit systemd dependency, but keep shipping the service file in the server package? I guess there is no real need for PostgreSQL to hard require systemd, because it will be part of the base system on installations that need it.
That would be fine by me as well. We could even just relax the requires to a recommends, as we do not install recommended packages in the containers. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1209208 https://bugzilla.suse.com/show_bug.cgi?id=1209208#c3 Fabian Vogt <fvogt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fvogt@suse.com --- Comment #3 from Fabian Vogt <fvogt@suse.com> --- Using %{?systemd_requires} is in most cases wrong. Using %{?systemd_ordering} and guarding the calls to systemctl with if [ -x /usr/bin/systemctl ]; then ... fi (like the systemd macros) is preferred. Pretty much all packages do it this way. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1209208 https://bugzilla.suse.com/show_bug.cgi?id=1209208#c4 Reinhard Max <max@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #4 from Reinhard Max <max@suse.com> --- Thanks, I'll have a look. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com