| 1 |
On 12/30/2009 12:11 PM, Robert Bradbury wrote: |
| 2 |
> For the last week or so, there have been packages in the "world" |
| 3 |
> distribution list which previously installed fine which currently do |
| 4 |
> not, these include ruby-gdkpixbuf2, ruby-pango, ruby-gtk2, |
| 5 |
> ruby-gnomecanvas2, ruby-gnome2 and ruby-libglade2 (this is on an x86 |
| 6 |
> system). My reading of the bug reports suggest that this is a problem |
| 7 |
> with the ruby/gentoo config scripts. If so, ok fine, then pull them |
| 8 |
> from the "world" distribution until such scripts/ebuilds/patches are |
| 9 |
> available. Please do not leave them in the world distribution list when |
| 10 |
> they are known to be defective. It appears that there may be some |
| 11 |
> oversight/direction lacking with respect to what makes up the QA with |
| 12 |
> respect to distributed (e.g. "approved") packages which have known problems. |
| 13 |
> |
| 14 |
|
| 15 |
You need to understand what the world set means. The world set is the |
| 16 |
packages in /var/lib/portage/world and the sets from |
| 17 |
/var/lib/portage/world_sets . From this follows that we can't change the |
| 18 |
content of the world set as it's a user specific configuration issue. |
| 19 |
Just make sure nothing in those files pulls in the packages that you |
| 20 |
have issues with and they are no longer part of your world set. What |
| 21 |
really should happen is that bug reports are filed on things that don't |
| 22 |
build and they are package.masked if they can't be fixed in a reasonable |
| 23 |
time frame. |
| 24 |
|
| 25 |
Regards, |
| 26 |
Petteri |
Archives