| Summary: | lots of X11 stuff bloating a minimal (non-graphic) server install due to rpm dependencies | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Xavier Matz <c934w-xavm493b> |
| Component: | Release (media or process) | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | ennael1, mageia, mageia, pmdenielou, sysadmin-bugs, thierry.vignaud, tmb |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | 3beta1 | ||
| Source RPM: | plymouth, desktop-common-data | CVE: | |
| Status comment: | |||
|
Description
Xavier Matz
2012-12-20 18:48:58 CET
claire robinson
2012-12-20 19:09:40 CET
Whiteboard:
(none) =>
3beta1
Thierry Vignaud
2012-12-21 09:06:26 CET
CC:
(none) =>
mageia, thierry.vignaud That's not "lots of X11 dependencies" (a utility (xprop), a couple libs & a couple fonts) dracut > plymouth > desktop-common-data > xdg-utils > xprop,xset > lib64x11_6, lib64xt6 > x11-font-daewoo-misc, x11-font-isas-misc, x11-font-jis-misc So there're several things we could do: 1) make dracut suggests & not requires plymouth (we'd to make sure bcd includes it on cds) 2) make libxt suggests & not requires fonts (we'd to make sure bcd includes them on cds) 3) move libxt requires on fonts into task-x11 (those manually installing X11 packages may have this issue but if they don't want task-x11, that's their own issue) 4) remove desktop-common-data requires from plymouth I would be in favor of both #1 and (#3 or #4): - #1 enables to not have plymouth - #4 enables to not have x11 packages b/c of plymouth For #2 & #3: Those fonts were added by p. zanoni: http://svn.mandriva.com/viewvc/packages/cooker/libxt/current/SPECS/libxt.spec?revision=603126&view=markup http://svn.mandriva.com/viewvc/packages/cooker/libxt/current/SPECS/libxt.spec?r1=603125&r2=603126& http://qa.mandriva.com/show_bug.cgi?id=60967 "Require x11-font-daewoo-misc, x11-font-isas-misc and x11-font-jis-misc If the fonts required by libxt are not present, xlib can spend a lot of time looking for them, which makes simple apps like "xmessage" and "xcalc" take almost 10 seconds to start on systems with a lot of fonts. This case is usually triggered by Xt apps that call XtSetLanguageProc on UTF-8 systems. Since UTF-8 is the default, require the fonts." For #4: The require on desktop-common-data was added by fred crozat: "Use mandriva.png from desktop-common-data now (Mdv bug #52973)" http://svn.mandriva.com/viewvc/packages/cooker/plymouth/current/SPECS/plymouth.spec?revision=417963&view=markup Colin, do plymouth still needs that? CC:
(none) =>
ennael1 Ahh crap, I keep meaning to drop the requires from dracut and keep forgetting :s I'm also not 100% sure that the plymouth stuff really needs the d-c-d png file these days - mageia-theme should contain everything needed I think. OK, I just dropped the requires on desktop-common-data (mga#8455) from plymouth. I also dropped the requires(pre) in dracut on plymouth which seems useless. I replaced the requires by the suggests (mdv did the same thing then dropped it). Xavier, could you try again with our latest Beta 4? It should be ok now. CC:
(none) =>
pierre-malo.denielou Closing (Presumed fixed (at least for Mageia 4)). Status:
NEW =>
RESOLVED maybe not (but not related to package listed here)
seen on irc:
blino > tmb: our bootloader-config helper used by kernel post scripts is
pulling many X11 deps because of Xconfig::resolution which is in
drakx-kbd-mouse-x11, I was thinking of splitting this module in
a separate drakx-kbd-mouse-x11-text to remove the X11 deps from
kernel, do you think it is ok to do that for Mga 4 ?
Just check a real install. If you still see this bug, please reopen I think that split will be needed indeed. Status:
RESOLVED =>
UNCONFIRMED Blino's suggestion in comment #6 is nice however we've a bigger issue where libalsa is pulling the X.org stack through: libalsa > libalsa-plugins > libavcodec > libav1 > libGL > libx* Without suggests, the require cycle is broken between libalsa & libalsa-plugins. A solution would be to: 1) drop thee libalsa-plugins suggests from libalsa, relying only on rpmsrate: 5 TYPE"64bit" DRIVER"^snd_" lib64alsa-plugins 2) alter rpmsrate so that alsa-plugins is only pulled if X11 is selected: 5 !TYPE"64bit" DRIVER"^snd_" libalsa-plugins 5 TYPE"64bit" DRIVER"^snd_" lib64alsa-plugins becoming: 5 CAT_X !TYPE"64bit" DRIVER"^snd_" libalsa-plugins 5 CAT_X TYPE"64bit" DRIVER"^snd_" lib64alsa-plugins CC:
(none) =>
mageia, tmb After testing, only the libalsa-plugins suggests is an issue. Splitting Xconfig::res* is not needed. It only pulls libdrakx-kbd-mouse-x11 whose only extra requires is drakxtools-backend which is already required by bootloader-utils anyway. And this does _NOT_ pull any part of the X.org stack. Only libalsa > libalsa-plugins is now bloating... Eventually drak3 & drakx-kbd-mouse-x11 do need to be splited. @Colin: Then another issue is that drakxtools-curses now require polkit which pulls gvfs/gtk/oxygen/ through polkit > libgio > libgvfs > gvfs* > libgtk > gtk > oxygen ... I would recommend dropping the suggests on libgvfs0 from gio & move it to gtk+ Just Fixed Status:
UNCONFIRMED =>
RESOLVED Right, I was mislead, drakx-kbd-mouse-x11 does not need to be split, we should revert the change. It doesn't hurt. I eventually did that split b/c it did brings one lib through: drakx-kbd-mouse-x11 > monitor-edid > libx86_1 Not that a big deal though... |