| View previous topic :: View next topic |
| Author |
Message |
einheitlix
Tux's lil' helper
Joined: 03 Aug 2004
Posts: 144
Location: Saarbrücken, Germany
|
 Posted: Wed Sep 24, 2008 4:56 am Post subject: [SOLVED] Strange update behaviour with Portage and Firefox |
 |
|
Hi,
I'm running an amd64 box and since Firefox 3 still isn't marked as stable, I edited /etc/portage/package.keywords to allow the ~amd64 version of the www-client/mozilla-firefox package (and its dependencies), so I can emerge it anyway.
While I was at it, I ran an 'emerge --sync' and an 'emerge -vuaD world' to update my whole system, not only Firefox (or so I thought). I noticed that although there is a 3.0.1 ebuild marked with ~amd64, portage still would not update to this version of Firefox when updating world. After my system update, my Firefox version was still 2.0.0.16. Another 'emerge -vuaD world' reported there was nothing more to update.
So I ran 'emerge -av mozilla-firefox' explicitly. Now portage would update my Firefox:
| Code: |
ririu ~ # emerge -av mozilla-firefox
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild N ] media-libs/lcms-1.17 USE="jpeg python tiff zlib" 878 kB
[ebuild N ] app-text/hunspell-1.2.6 USE="ncurses nls readline" 757 kB
[ebuild N ] net-libs/xulrunner-1.9.0.1 USE="dbus gnome ipv6 java startup-notification -custom-optimization" 33,169 kB
[ebuild U ] www-client/mozilla-firefox-3.0.1 [2.0.0.16] USE="dbus%* gnome ipv6 java startup-notification%* xulrunner%* -bindist -custom-optimization% -iceweasel -mozdevelop -restrict-javascript (-debug%) (-filepicker%) (-moznopango%) (-xforms%) (-xinerama%) (-xprint%)" LINGUAS="de es fr -af -ar -be -ca -cs -da -el -en -en_GB -en_US -es_AR -es_ES -eu -fi -fy -fy_NL -ga -ga_IE -gu -gu_IN -he -hu -id% -it -ja -ka -ko -ku -lt -mk -mn -nb -nb_NO -nl -nn -nn_NO -pa -pa_IN -pl -pt -pt_BR -pt_PT -ro -ru -si% -sk -sl -sq% -sr% -sv -sv_SE -tr -uk -zh -zh_CN -zh_TW (-bg%)" 11,656 kB
Total: 4 packages (1 upgrade, 3 new), Size of downloads: 46,459 kB
|
So, I did this and Firefox 3 is running just fine. But running another 'emerge -vuaD world' shows that portage again wants to downgrade it:
| Code: |
ririu ~ # emerge -vuaD world
These are the packages that would be merged, in order:
Calculating world dependencies... done!
[ebuild UD] www-client/mozilla-firefox-2.0.0.16 [3.0.1] USE="gnome ipv6 java -bindist -debug% -filepicker% -iceweasel -mozdevelop -moznopango% -restrict-javascript -xforms% -xinerama% -xprint% (-custom-optimization%) (-dbus%*) (-startup-notification%*) (-xulrunner%*)" LINGUAS="de es fr -af -ar -be -bg% -ca -cs -da -el -en -en_GB -en_US -es_AR -es_ES -eu -fi -fy -fy_NL -ga -ga_IE -gu -gu_IN -he -hu -it -ja -ka -ko -ku -lt -mk -mn -nb -nb_NO -nl -nn -nn_NO -pa -pa_IN -pl -pt -pt_BR -pt_PT -ro -ru -sk -sl -sv -sv_SE -tr -uk -zh -zh_CN -zh_TW (-id%) (-si%) (-sq%) (-sr%)" 39,783 kB
Total: 1 package (1 downgrade), Size of downloads: 39,783 kB
|
Now I'm wondering, how is this possible? I can emerge mozilla-firefox-3.0.1 just fine, portage doesn't complain, it even selects this version automatically when running 'emerge -av mozilla-firefox'. But when I run a system update, for some weird reason it tries to downgrade Firefox again. This is not only bizarre, it is actually annoying, since now portage will downgrade my Firefox each time I upgrade my system. Of course I can manually hardmask any Firefox versions below 3.0*, but this would be more of a workaround, not a real solution. I want to understand the source of the problem.
Do any of you understand why portage can emerge mozilla-firefox-3.0.1, but still wants to downgrade it when running a system update? That would really help me out., because I've got no idea.. 
_________________
Collecting data is only the first step toward wisdom. But sharing data is the first step toward community.
Last edited by einheitlix on Wed Sep 24, 2008 6:22 am; edited 1 time in total |
|
| Back to top |
|
 |
VoidMage
l33t
Joined: 14 Oct 2006
Posts: 995
|
| Posted: Wed Sep 24, 2008 5:08 am Post subject: |
|
|
That's been discussed so many times, it's boring.
You need to set xulrunner useflag globally and re-emerge packages that have it,
by now in the unstable it's all you need to do. |
|
| Back to top |
|
|
einheitlix
Tux's lil' helper
Joined: 03 Aug 2004
Posts: 144
Location: Saarbrücken, Germany
|
| Posted: Wed Sep 24, 2008 6:21 am Post subject: |
|
|
Whoops - sorry if this has been brought up before... just didn't find it 
Anyway, your solution worked great! Thanks a lot!
Cheers,
Malte
_________________
Collecting data is only the first step toward wisdom. But sharing data is the first step toward community. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Portage & Programming
