| Summary: | GConf2 should not require polkit-agent, this pulls GUI packages on servers | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Samuel Verschelde <stormi-mageia> |
| Component: | RPM Packages | Assignee: | Shlomi Fish <shlomif> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | doktor5000, marja11 |
| Version: | 5 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | GConf2-3.2.6-4.mga4.src.rpm | CVE: | |
| Status comment: | |||
|
Description
Samuel Verschelde
2015-07-23 17:45:16 CEST
What about Mageia 5 and Cauldron? They probably have the same GConf2 to polkit-agent dependency, but java 8 doesn't requires GConf2 according to David Walser, so only people who need GConf2 for another reason are likely to be concerned. Fixed in Cauldron at «Release : %mkrel 10» - I don't see too much point in fixing it on Mageia 4. Do you? Status:
NEW =>
ASSIGNED (In reply to Shlomi Fish from comment #3) > Fixed in Cauldron at «Release : %mkrel 10» - I don't see too much point in > fixing it on Mageia 4. Do you? On the contrary. The recent update to java pulled lots of GUI packages to my server, it would be good to avoid that it happens to other users. Mageia 4 is still supported, I think an update would be nice. Besides just removing the dependency from GConf2, we should figure out why it was put there and where it should be instead. Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
Florian Hubold
2015-10-07 20:56:27 CEST
CC:
(none) =>
doktor5000 If this bug didn't get fixed in Mageia 5, then we regret that. Closing as OLD, because Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/ This bug was fixed for Mageia 6 cauldron, so Mageia 6 shouldn't have it. Resolution:
(none) =>
OLD |