| Summary: | Cannot upgrade Gnome and Gnome-Media due to gst-plugins dependency | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | gtaluvit <gtaluvit> |
| Component: | New packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
| Status: | VERIFIED WORKSFORME | ||
| Severity: | minor | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
gtaluvit
2003-02-10 10:23:17 UTC
Had the suggestion of not using -u. I've tried that with emerge -p gnome and now its dieing on not finding nautilus-2.2.0.2. I'm manually emerging that now and trying that. OK, slight change to this bug. Things work much better without -u. I got the nautilus dependency issue, so I manually emerged nautilus2.2 which worked fine. Then a emerge -p gnome showed all the dependencies and its compiling now. So, the bug is why did I have to manually emerge nautilus2.2 if its not masked? im wondering, can you give me the breaking output of gnome-media ? gnome-media doesn't seem to depend on nautilus at all (and i don't know why it should). And what exactly was 'dieing' on nautilus ? What arch are you on ? x86 ? but gstreamer 0.5.2 and up aren't masked for x86, so it makes little sense. The nautilus issue was with emerge -p gnome or emerge -p world, NOT with gnome-media. The gnome-media issue occured if I used -u. Without -u, as in emerge -p gnome I would get a similar error for dependencies as above, stating that
!!! all ebuilds that could satisfy ">=gnome-base/nautilus-2.2.0.2" have been
masked.
However, I could manually emerge that ebuild with emerge nautilus-2.2.0.2.ebuild and that installed fine and now gnome installs with no problems. My question is, why did I need to install that manually to begin with. emerge gnome should have worked. As an aside, if I do an emerge -s nautilus, here's my nautilus entry.
* gnome-base/nautilus
Latest version available: 2.0.8
Latest version installed: 2.2.0.2
Size of downloaded files: 5,005 kB
Homepage: http://www.gnome.org/
Description: A filemanager for the Gnome2 desktop
2.2 is not masked so why is this happening?
you ask me, it doesnt make sense . stale files ? something in your local distfiles ? bad rsync mirror ? I had cleaned out distfiles, rsynced from multiple mirrors and had the same problem. I don't know what other files could be stale, especially since this system is only a few days old. The original Gnome was installed via GRP. hmmm GRP, maybe that has to do with it.. can you remove /var/cache/edb/dep/* ? See if that makes a difference. That fixed it. -u now seems to work and an emerge -s nautilus now shows the correct package. Thank you very much! I've recently run into this bug on an AMD64 system. Here's what I get: # emerge -pu world These are the packages that I would merge, in order: Calculating world dependencies | !!! all ebuilds that could satisfy "=media-plugins/gst-plugins-vorbis-0.6*" have been masked. !!! possible candidates are: - media-plugins/gst-plugins-vorbis-0.6.4 (masked by: ~keyword) !!! (dependency required by "gnome-extra/gnome-media-2.4.1.1" [ebuild]) !!! Problem with ebuild gnome-base/gnome-2.4.2 !!! Possibly a DEPEND/*DEPEND problem. !!! Depgraph creation failed. **** It looks to me like somebody removed the AMD64-approved gst-plugins-vorbis version from the Portage tree (my system currently has 0.6.3 installed) and changed the gnome-media package description to require 0.6.4. (I've no idea if it really does.) I've tried changing "~amd64" in the gst-plugins-vorbis ebuild to "amd64", and that seems to at least get things building. (The process isn't yet finished on my system, though.) yes and this bug has completely nothind todo with that, so file a new bug and file it to the amd64 team. |
