--(#:~)-- emerge -s mozilla [ Results for search key : mozilla ] [ Applications found : 1 ] * net-www/mozilla Latest version Available: 1.1_beta Latest version Installed: 1.0-r2 Homepage: http://www.mozilla.org Description: The Mozilla Web Browser --(#:~)-- emerge -p -u world These are the packages that I would merge, in order. Calculating world dependencies ...done! as you can see... portage can find a new version but dosn't want to "update world"....
what version of portage?
what is your world file ... did you emerge mozilla yourself or did another package bring it down
I use... * sys-apps/portage Latest version Available: 2.0.13 Latest version Installed: 2.0.13 Homepage: http://www.gentoo.org Description: Portage ports system I havn't modified my world file... nor asked any application for a newer mozulla.... also it didn't want to update to -r03 I also discovered that on another package - but sadly I didn't noted down which one... but I assume it's either an ebuild or portage problem (or feature?)
what i mean is, did you do `emerge mozilla` yourself to install it the first time, or did another application's dependency install it if it is the second case than this is a known issue and i think a bug already exists for it
yepp.. that might be the issue (installed through galeon :) sorry, for the duplicate entry in the bug-database, I searched it but obviously not hard enough. Anyway, I would consider this problem quite grave, as almost anyone expects to be up2date after a "emerge world".... what I second miss, and I know the gentto-dev is aware of it is that I have a way to get galeon also to be recompiled when I had choosen to recompile mozilla... - yep. there's a nice script in "Tips 'n Tricks" which partly helps to reduce the problem. I just wanted to note the problem for anybody who "passes by" ans also wondered... if anybody has the bug# handy which I didn't found please fill it in here... Thanks & Greetings xor
