Hello, I've tried to pull the latest gnome packages which I unmasked in package.mask. gnome-base also belongs to my world file so it should update any new versions of the gnome packages if unmasked in package.mask or "officially" released. That doesn't work. If I unmask a package in package.mask which isn't actually installed on my system and try to install it then portage grabs this unmasked version of this package. When updating existing installed packages it won't. Summary: Im am not able to update my "world" packages with a simple emerge -u world. I have to go directly to new ebuild and emerge it. Cheers, tobias
I've also seen this behavior and have tried to work around it with a ebuild of the "offending" masked package. Then a later 'emerge --update world' complains about the masked package being unavailable to satisfy a dependency. Or something like that.
im not sure i know what you're talking about ... the way i see it, everything is acting the way it should ...
When a package is unblocked it still can't be installed... Even when there are no obvious things blocking it.
root@rux0r etc # emerge -s grub Searching... [ Results for search key : grub ] [ Applications found : 1 ] * sys-apps/grub Latest version available: 0.90-r7 Latest version installed: 0.90-r7 Homepage: http://www.gnu.org/software/grub Description: GNU GRUB boot loader root@rux0r etc # nano /usr/portage/profiles/package.mask <remove grub masking> root@rux0r etc # emerge grub -up These are the packages that I would merge, in order. Calculating dependencies ...done! [ebuild U ] sys-apps/grub-0.92 to / root@rux0r etc # emerge grub -u <installs grub-0.92>
root@rux0r etc # grub --version grub (GNU GRUB 0.92) root@rux0r etc # emerge --version Portage 2.0.36 if you look at my previous comment you'll see that masking does work ... maybe you could post the version of emerge you have, and then post the entries that you removed from package.mask finally, can you post the emerge command you are using ? (i.e. what package are you trying to emerge)
I (now) have the same version of portage as I'm upgrading my only Gentoo machine to 1.4. This was with a 1.1a installation. I wasn't disputing that masking worked, it just worked too well. I couldn't do what you did with grub. It's possible that it's been fixed with 2.0.35 but I can't tell anymore as I've upgraded to it. I'll have to leave it to Tobias to validate if it's broken this way in the earlier version.
Hm...I also don't have the possibility to check this behavior with previous versions of portage as I don't like to downgrade portage. Here are few output snippets: stella:/home/tobias# emerge --version Portage 2.0.36 ----snap---- stella:/home/tobias# less /var/cache/edb/world ... gnome-base/gnome ... ----snap---- stella:/home/tobias# vim /usr/portage/profiles/package.mask <unmasking all relevant new gnome packages including "=gnome-base/gnome-2.0.2_pre1"> ----snap---- stella:/home/tobias# emerge -pu world These are the packages that I would merge, in order. Calculating world dependencies ...done! ----snap---- I don't know if this a portage issue or a gnome ebuild version "conflict" whatsoever..
what if you do `emerge gnome -p` and `emerge gnome -pe` ? does it show the expected output ? if not, see if you can look into exactly what versions of gnome packages you have installed ? `qpkg -I` might be of help ... get that from running this: `emerge gentoolkit`
Some output again: stella:~# emerge gnome -p These are the packages that I would merge, in order. Calculating dependencies ...done! [ebuild R ] gnome-base/gnome-2.0.1 to / ----snap---- On my box the command "emerge gnome -pe" lists all packages which gnome depends on and vice versa. But new package versions are included in that output.. Thanks a lot for your help though...perhaps I'm going to merge the latest gnome2 common ebuild directly..: stella:/usr/portage/gnome-base/gnome# emerge -p gnome-2.0.2_pre1.ebuild These are the packages that I would merge, in order. Calculating dependencies ...done! [ebuild U ] net-libs/linc-0.5.3 to / [ebuild U ] gnome-base/ORBit2-2.4.3 to / [ebuild U ] dev-libs/libxml2-2.4.24 to / [ebuild U ] media-sound/esound-0.2.29 to / [ebuild U ] gnome-base/gnome-mime-data-2.0.1 to / [ebuild U ] gnome-base/gnome-vfs-2.0.4 to / [ebuild U ] dev-libs/libxslt-1.0.20 to / [ebuild U ] gnome-base/libgnome-2.0.4 to / [ebuild U ] gnome-base/libglade-2.0.1 to / [ebuild U ] gnome-base/libgnomecanvas-2.0.4 to / [ebuild U ] gnome-base/libbonoboui-2.0.3 to / [ebuild U ] gnome-base/libgnomeui-2.0.5 to / [ebuild U ] x11-libs/libwnck-0.17 to / [ebuild U ] gnome-extra/gnome-system-monitor-2.0.2 to / [ebuild U ] media-gfx/eog-1.0.3 to / [ebuild U ] gnome-base/gnome-desktop-2.0.8 to / [ebuild U ] gnome-base/gnome-panel-2.0.9 to / [ebuild U ] gnome-extra/gnome-games-2.0.4 to / [ebuild U ] gnome-extra/libgtkhtml-2.0.2 to / [ebuild U ] gnome-extra/gnome-utils-2.0.5 to / [ebuild U ] gnome-base/gnome-applets-2.0.2 to / [ebuild U ] gnome-extra/gnome-media-2.0.2.5 to / [ebuild U ] gnome-base/eel-2.0.6 to / [ebuild U ] app-editors/gedit-2.0.5 to / [ebuild U ] gnome-extra/gconf-editor-0.3.1 to / [ebuild U ] gnome-base/gdm-2.4.0.11 to / [ebuild U ] gnome-extra/yelp-1.0.6 to / [ebuild U ] gnome-base/nautilus-2.0.6 to / [ebuild U ] gnome-base/gnome-session-2.0.7 to / [ebuild U ] gnome-base/control-center-2.0.1.1 to / [ebuild U ] gnome-base/gnome-2.0.2_pre1 to / This should do the trick but it's only a workaround for not getting gnome up2date via emerge -pu world.. I think its not portage's fault as I can see that , for example, the xfree update also works. I think it has something to do with gnome ebuild itself. Investigating this..
...But new package versions are included in that output....I meant "are not" :)
Friends, I've found the problem. It has something to do with the keywords used in the latest gnome-2.0.2_pre1.ebuild. There is no "x86" included in that file but only "ppc". That's the reason why portage ignores this update as my box is an x86 one. I've added the "x86" and now everything works like it should. Thanks to the program diff to let me get to this point. Cheers, tobias
So I installed the gnome-2.0.2 ebuilds..my hole applications menu has gone now. :/ I removed all gnome user settings and restarted it but with no effect. Which program does gnome use to generate its menu and where is this menu structure defined?
This isn't the bug that is used to be. THIS WAS NOT SPECIFIC TO THIS GNOME PACKAGE, it behaved the same way with apache2 and mm. Since it works with Portage 2.0.35 I guess I don't care anymore but you guys jumped the gun on this one.
actually it is ... the original bug reporter had a problem utilizing gnome2 due to a x86 bug as for the apache2 thing ... unmasking and trying to emerge it worked for me and if the bug has been fixed by a newer version of portage, then developers will not bother making ebuilds work with older versions of portage ... the policy with portage is, if it doesnt work with the latest version of portage, then its a bug ... otherwise, do what you want chill out ;)
KEYWORDS is fixed for the gnome package, closing this bug as it has rolled offtopic for me :)
