Summary: | libxfcegui4-4.2.2 incompatible with gtk+-2.8 ; patch included | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Alexandre Rostovtsev (RETIRED) <tetromino> |
Component: | [OLD] Unspecified | Assignee: | XFCE Team <xfce> |
Status: | RESOLVED FIXED | ||
Severity: | major | CC: | amne, andrew, crusaderky, jakub, r3pek, shindo, sqrammi |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
4.2.2-taskbar-gtk-2.8.patch
Screenshot before patching libxfcegui4 |
Description
Alexandre Rostovtsev (RETIRED)
2005-08-17 15:24:51 UTC
Created attachment 66186 [details, diff] 4.2.2-taskbar-gtk-2.8.patch This is derived from a patch in upstream bugzilla (http://bugzilla.xfce.org/show_bug.cgi?id=1099), but it has been changed slightly because the upstream patches don't work quite right. Created attachment 67851 [details]
Screenshot before patching libxfcegui4
I had this problem after upgrading to gtk 2.8. Applying the patch fixes it!
The screenshot I've attached shows how it looked like before patching.
*** Bug 107315 has been marked as a duplicate of this bug. *** Applied, thank you :) Reopening this bug. With gtk 2.8.8 being stable and both libxfcegui4.2.2 and 4.2.2-r1 stable on most arches, this bug affects all stable users that do not update their systems via emerge -uD world (or have libxfcegui in their world file). Wouldn't it be a good idea to bump them to -r1? *** Bug 112435 has been marked as a duplicate of this bug. *** had the same gtk+ compile error on amd64. the following procedure worked: emerge cairo emerge pango emerge gtk+ *** Bug 119559 has been marked as a duplicate of this bug. *** *** Bug 121808 has been marked as a duplicate of this bug. *** (In reply to comment #5) > Wouldn't it be a good idea to bump them to -r1? What do you want to bump, actually? Doesn't make sense. What needs to be stabilized? (In reply to comment #10) > What do you want to bump, actually? Doesn't make sense. What needs to be > stabilized? As i said in #5, it's already stable, but unless you manually emerge -u1 libxfcegui or emerge -uD world (which not all people do necessarily), you won't get the fixed version. That's a potential problem, so i suggested to bump those users to -r1. And by bumping i didn't mean making the already stable -r1 stable, but doing something else that automatically triggers the update (e.g. removing/masking the broken version, would that trigger an upgrade on emerge -u world? Not sure, but that's not my decision to make anyway) Not really an issue any more because dostrow (iirc) said some newer version will go stable soon anyway. Closing again. *** Bug 122062 has been marked as a duplicate of this bug. *** |