Bug 218794 - The great Gnome 2.22 keywording request bug
|
Bug#:
218794
|
Product: Gentoo Linux
|
Version: unspecified
|
Platform: All
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: enhancement
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: gnome@gentoo.org
|
Reported By: eva@gentoo.org
|
|
Component: Ebuilds
|
|
|
URL:
|
|
Summary: The great Gnome 2.22 keywording request bug
|
|
Keywords: KEYWORDREQ
|
|
Status Whiteboard:
|
|
Opened: 2008-04-21 21:27 0000
|
Hello arches, please find in the next attachments packages that needs
(re)keywording for gnome-2.22 to be supported on your favorite platform.
gah missed my announcement effect. Please read comment #0 and #1 :)
This list might be incomplete so in doubt, you can always poke me or the rest
of the team on #gentoo-desktop, by mail, jabber, ...
Thanks in advance.
Remove x86 as there's nothing to do for us. ;)
There is nothing amd64 or x86 related in that list
Created an attachment (id=150724) [details]
Log of failed build against =dev-python/pygtk-2.12.0
Could it be that net-libs/gtk-vnc needs >=dev-python/pygtk-2.12.1 ? I saw
sandbox violations when building against =dev-python/pygtk-2.12.0.
(In reply to comment #7)
> Created an attachment (id=150724) [edit] [details]
> Log of failed build against =dev-python/pygtk-2.12.0
>
> Could it be that net-libs/gtk-vnc needs >=dev-python/pygtk-2.12.1 ? I saw
> sandbox violations when building against =dev-python/pygtk-2.12.0.
>
these kind of sandbox violation happens with migrating from python 2.4 to 2.5
without running python-updater.
(From update of attachment 150724 [details])
(In reply to comment #8)
> these kind of sandbox violation happens with migrating from python 2.4 to 2.5
> without running python-updater.
Ah yes, of course.
added ~ppc64 as far as I could (some missing due to bug #176380)
Additionally the following are necessary for gnome-games (ggz) and totem
(gdata):
>=dev-games/libggz-0.0.14 alpha arm hppa ia64 ppc64 sh
>=dev-games/ggz-client-libs-0.0.14 alpha arm hppa ia64 ppc64 sh
>=dev-python/gdata-1 alpha arm hppa ia64 ppc64 sh
Re-CCing some arches based on that
sparc is also missing dev-python/gdata.
SPARC: Please keyword dev-python/gdata and after that feel free to copy the
GNOME-2.22 unmask block from profiles/arch/x86/package.mask to your profiles in
profiles/arch/sparc/package.mask and profiles/default-linux/sparc/package.mask
(In reply to comment #13)
> sparc is also missing dev-python/gdata.
>
> SPARC: Please keyword dev-python/gdata and after that feel free to copy the
> GNOME-2.22 unmask block from profiles/arch/x86/package.mask to your profiles in
> profiles/arch/sparc/package.mask and profiles/default-linux/sparc/package.mask
>
Added ~sparc for dev-python/gdata-1.0.8 --- it seems fine and its test check
out. As for the big gnome request, I am not in a position to do that (can't
really test).
removed ~ppc64 from gnome-base/gnome-volume-manager-2.22.1. We'll add ~ppc64 to
the remaining packages on the list once bug #176380 is fixed.
~ppc'd. Let me know if I missed something.
(In reply to comment #18)
> ~ppc'd. Let me know if I missed something.
>
DEPEND.bad 17
net-misc/vinagre/vinagre-0.5.1.ebuild: ~ppc(default-linux/ppc/ppc32/2006.1)
['>=net-libs/gtk-vnc-0.3.3']
net-misc/vinagre/vinagre-0.5.1.ebuild: ~ppc(default-linux/ppc/ppc32/2007.0)
['>=net-libs/gtk-vnc-0.3.3']
net-misc/vinagre/vinagre-0.5.1.ebuild:
~ppc(default-linux/ppc/ppc32/2007.0/desktop) ['>=net-libs/gtk-vnc-0.3.3']
net-misc/vinagre/vinagre-0.5.1.ebuild:
~ppc(default-linux/ppc/ppc32/2007.0/G3) ['>=net-libs/gtk-vnc-0.3.3']
net-misc/vinagre/vinagre-0.5.1.ebuild:
~ppc(default-linux/ppc/ppc32/2007.0/G3/Pegasos) ['>=net-libs/gtk-vnc-0.3.3']
net-misc/vinagre/vinagre-0.5.1.ebuild:
~ppc(default-linux/ppc/ppc32/2007.0/G4) ['>=net-libs/gtk-vnc-0.3.3']
etc etc etc
~hppa ['>=dev-libs/totem-pl-parser-2.22.2',
'>=gnome-extra/gnome-power-manager-2.22.1', '>=media-video/totem-2.22.1']
~ppc ['>=gnome-extra/gnome-power-manager-2.22.1']
besides ppc64 that needs fixes for hal, hppa and ppc still need to fix the
above packages. sparc, ia64, alpha got their ticket for unmasking.
(In reply to comment #20)
> ~hppa ['>=dev-libs/totem-pl-parser-2.22.2',
> '>=gnome-extra/gnome-power-manager-2.22.1', '>=media-video/totem-2.22.1']
> ~ppc ['>=gnome-extra/gnome-power-manager-2.22.1']
>
> besides ppc64 that needs fixes for hal, hppa and ppc still need to fix the
> above packages. sparc, ia64, alpha got their ticket for unmasking.
totem doesn't seem to work for HPPA, continuously spitting out this message:
(totem:27645): GLib-GObject-CRITICAL **: g_signal_handler_disconnect: assertion
`handler_id > 0' failed
I haven't been able to trace where exactly it goes wrong, but it would seem
this is a glib function that is at fault.
What does "doesn't work" mean? The warning is a warning. It can happen while
everything is working fine too, so not really descriptive. The warning happens
when an event signal is tried to be disconnected (probably temporarily) but
that exact signal doesn't exist to disconnect. So if there's a real problem,
then it might be related if a signal isn't connected and therefore something
doesn't work, but otherwise maybe doesn't even matter much.
HPPA, I copied the GNOME-2.22 mask to your profiles, so that I can unmask it
globally while the HPPA keywording is sorted out. However I will look later
into unmasking most of it if possible, as lack of totem-2.22 just means the
meta can't be keyworded, but the rest of GNOME-2.22 could be there if you
keyworded the rest (sans totem-2.22 experience with its new features).
(In reply to comment #24)
> How is this bug related to bug #236971 and bug #236971? Except for totem, HPPA
> is all done, I think.
Sorry, yes, you might be done with the rest, as your keyword level is testing
right now for GNOME-2.22. I'll try to unmask most of GNOME-2.22 for you soon
then, I assume that's fine. Then you can start thinking about stabilization
when you feel it suitable, considering it will enter ~hppa only now, 2.22 has
been out for half a year and we are likely to be asking GNOME-2.24
stabilization from arches in 6 weeks from now, so I'm not sure the 30 days in
~arch should apply here once unmasked.
With totem having dropped HPPA keywords and totem-pl-parser having no HPPA
keyword at all, and the gnome-2.22* ebuilds having their HPPA keywords dropped
(to make repoman happy), HPPA is done here. Once the totem problem has been
resolved I will readd it.
shouldnt x11-libs/gtk+-2.14.3 be in the mask as well since it requires
gail-1000+
(In reply to comment #27)
> shouldnt x11-libs/gtk+-2.14.3 be in the mask as well since it requires
> gail-1000+
gtk+-2.14.3 and gail-1000 are recent things that GNOME-2.24 uses. gtk+-2.14.3
now ships gail libraries itself, hence the gail-1000. We have always tried to
keep gtk+ not masked anyhow even if GNOME is I think, because gtk+ is not for
only GNOME but many other apps and XFCE4 too.
gtk+-2.14.3 was added 4-5 days ago to tree, and unmasked 8 hours ago as a
normal big gtk+ upgrade for all apps to benefit with new API and features.
(In reply to comment #27)
> shouldnt x11-libs/gtk+-2.14.3 be in the mask as well since it requires
> gail-1000+
Oh, I get it what you mean. You are having >=gail-2.22 p.masked, but that
includes gail-1000. I think we can simply remove that one p.mask entry our of
many from all profiles because this is a low-level thing that should work fine
with GNOME-2.20 as welll
(In reply to comment #29)
> I think we can simply remove that one p.mask entry our of
> many from all profiles because this is a low-level thing that should work fine
> with GNOME-2.20 as well
I've done that now
PPC should be all set here...
arm done and s390 has nothing to do here.
sh waiting for totem
bsd should be done here except for badindev deps in nautilus