Summary: | app-admin/gnome-system-tools-2.14.0 (masked by: package.mask) for Gnome 2.20 but it shouldn't | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Wolf Canis <wolf.canis> |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED WONTFIX | ||
Severity: | major | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | diff |
Description
Wolf Canis
2008-04-13 15:09:46 UTC
(In reply to comment #0) I figured the following out. If the mask in /usr/portage/profiles/package.masks is: >app-admin/gnome-system-tools-2.14.0 >app-admin/system-tools-backends-1.4.2-r1 Then the problem is gone. The intention was to mask all gnome-system-tools versions, as >2.14 was already masked earlier. Any explanations on the reasoning I'll leave to Gilles who is familiar with the problems. Created attachment 149562 [details, diff]
diff
That should fix the problem.
(In reply to comment #2) So far I that understand, is the intention to mask the required version by Gnome 2.22 not for Gnome 2.20. Because Gnome 2.20.3 is the stable version. Or what is it what I'm missing? Thanks. Same here. My laptop is running stable gnome (2.20) and gnome-system-tools-2.14 have to be unmasked and added to the world file although they work fine. you might want to add something like !<app-admin/gnome-system-tools-2.22* to the DEPEND part of the gnome-2.22 ebuild Let's get this straight once and for all : 1) g-s-t 2.14 is _broken_ and _unmaintained_ by upstream. We don't want to fix it, and we'd rather people didn't use those as they have serious issues. 2) gst 2.20 is masked because it may have some bugs and it could use more testing. The plan is to get 2.20 or newer out of p.mask once we feel it's ready. 2.14 will disappear because it just doesn't work. Thanks for understanding PS, Gilles, if I got this wrong, please correct me :p (In reply to comment #6) I'm sorry, I haven't any issues with g-s-t 2.14. What are the issues? Thanks. you sum up it well :) I'll add the although g-s-t 2.14 might appear to work, it already had tweaks and was still not working fully. With the arrival of gnome-2.22, it _will_ break once and for all (see bug #216019). It is not that is it not fixable, nobody will do it and it is highly preferable to make >=2.20 work as this is where upstream wants to go. (In reply to comment #8) I understand that for Gnome 2.22 g-s-t 2.14 is broken, but first Gnome 2.20 isn't masked and second if g-s-t 2.14 is broken for Gnome 2.22, and that is obvious, why must g-s-t 2.14 masked for Gnome 2.20? Why you can't mask the way I suggested? I have to missing something, but I don't know what, perhaps someone can clarify this? Only for the record, I'm not a Linux newbie, I have about 15 years experience with several distributions. Something like that I didn't experienced ever. Thanks in advance. One thing should be noted : p.masking a package in Gentoo can mean several things. In our case, we are currently masking gnome-system-tools because we, as maintainers, feel that the quality of the Gentoo backend of system-tools is not good enough. That doesn't mean you can't use it if you know what you're doing. It just means that _for_now_, we don't want people to think that g-s-t is safe to use. Some tools work, some don't, and some others we don't really know. That's what the mask means in this case. Now please, let's stop the discussion about the masking. If you want to help fix g-s-t, please search our bugzilla for bugs that have been reported or just try the newer versions and report bugs if you find any. G-s-t _will_ stay masked until we, as maintainers, feel it's good enough for our users. Thanks for understanding |