Bug 21139 - rpm requires dbus and X11 libs on chroot-minimal system due to rpm plugins not being split out
Summary: rpm requires dbus and X11 libs on chroot-minimal system due to rpm plugins no...
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: RPM stack maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-06-24 14:08 CEST by Neal Gompa
Modified: 2017-07-31 01:51 CEST (History)
1 user (show)

See Also:
Source RPM: rpm-4.13.0.1-2.mga6.src.rpm
CVE:
Status comment:


Attachments

Description Neal Gompa 2017-06-24 14:08:49 CEST
Description of problem:
The rpm package requires dbus and X11 libraries in a chroot minimal environment because the rpm plugins aren't split out into their own subpackages.

Please split them out into subpackages and make them required only on a full base system, similar to how Fedora has it done[1].

[1]: http://pkgs.fedoraproject.org/cgit/rpms/rpm.git/tree/rpm.spec

Version-Release number of selected component (if applicable):
4.13.0.1-2.mga6

How reproducible:
Always
Comment 1 Thierry Vignaud 2017-07-30 23:41:51 CEST
This is totally bogus and hasn't been tested.
This doesn't solve anything.
If you would have tested, you would have seen that systemd would still have pulled dbus in minimal chroot...

CC: (none) => thierry.vignaud

Comment 2 Rémi Verschelde 2017-07-31 00:05:06 CEST
(In reply to Thierry Vignaud from comment #1)
> This doesn't solve anything.
> If you would have tested, you would have seen that systemd would still have
> pulled dbus in minimal chroot...

The fact that it does not fix *all* issues does not mean that it's pointless. We need to start somewhere.
Comment 3 Thierry Vignaud 2017-07-31 01:51:12 CEST
Seriously?
The bug description is bogus.
The suggested fix is bogus and has NOT been tested.

If you seriously wants to remove dbus from the minimal chroot, you'd better analyze the deps and propose a plan.
None of that was done.

If you don't have a plan, doing such blind changes is useless and risk breaking things.

Please analyze deps first and then explain why purging systemd from the minimal chroot is wanted.
And just try running "rpm -e systemd --test" in a minimal chroot

Then once you've a justification and a plan, you can start a real serious discussion.

Status: NEW => RESOLVED
Resolution: (none) => INVALID


Note You need to log in before you can comment on or make changes to this bug.