I know it's probably too soon, but will open this for tracking purposes and start thinking on a version that could go stable when Gnome 3.10 is going too. I think this one is the first working properly on ia64
At 20 Feb will make a month in the tree, maybe we could CC arches at that time... or does it have more pending problems?
Ive been waiting to hear back from ia64 etc, but nothing negative so far. All good in my opinion. Im on the road so i can CC arches next week or pls go ahead. we recommend stabilizing polkit at the same time too.
(We will need to track this as it's a depend of latest gjs from gnome-3.10 :)) What polkit stuff is needed for this? polkit-0.112-r1? In that case, should I CC freedesktop (in this case ssuominen ;)) to confirm he is ok or is it simply waiting for this to go to stable? Thanks!
@freedesktop, any problems with stabilizing pokit-1.112-r1 with this?
(In reply to Pacho Ramos from comment #4) > @freedesktop, any problems with stabilizing pokit-1.112-r1 with this? no. I've been asked about this many times already. Just stabilize latest polkit when you need it. Latest is greatest.
sys-auth/polkit isn't keyworded for HPPA, bug #502124 may or may not be fixed since a newer version appears to be working better, permitted it's patched (bug #497900), so dev-lang/spidermonkey-17* need not go stable for HPPA.
amd64 stable
x86 stable
arm stable
Sorry if i'm writing in the wrong place, but on amd64, updgrading from sys-auth/polkit-0.112 to sys-auth/polkit-0.112-r1 force to install spidermonkey:17 while it has previously worked with spidermonkey-1.8.5-r4:0 This is intentional? There are really problems on amd64 using polkit-0.112 with spidermonkey-1.8*? Thanks in advance.
(In reply to Fabio Bonfante from comment #10) > Sorry if i'm writing in the wrong place, but on amd64, updgrading from > sys-auth/polkit-0.112 to sys-auth/polkit-0.112-r1 force to install > spidermonkey:17 while it has previously worked with spidermonkey-1.8.5-r4:0 > > This is intentional? Yes. 17.* is an upgrade over 1.8.*. As in, latest supported version is used in purpose. > There are really problems on amd64 using polkit-0.112 with spidermonkey-1.8*? Yes, that's right, but instead of forcing polkit to use older spidermonkey, efforts should be put in fixing anything using 1.8* to use also 17* or newer so you can uninstall the older version of spidermonkey As in, we are moving forward, not backwards
Woops... 17 > 1.8 and not 1.7 < 1.8 ...that's the point! :p Thanks Samuli.
Merge in 3.10 bug due: https://bugs.gentoo.org/show_bug.cgi?id=499954#c1 *** This bug has been marked as a duplicate of bug 499954 ***
Bleh, spidermonkey was done in bug 507568 but I forgot polkit there :S, sorry for the inconvenience
*** This bug has been marked as a duplicate of bug 508862 ***