| Summary: | gq-1.0beta1 ebuild (update of 0.7beta2) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | scott.claridge |
| Component: | New packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
| Status: | RESOLVED TEST-REQUEST | ||
| Severity: | enhancement | CC: | dragonheart |
| Priority: | High | Keywords: | EBUILD |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | 33241 | ||
| Bug Blocks: | |||
| Attachments: | ebuild file for 1.0beta1 | ||
|
Description
scott.claridge
2004-01-13 14:26:54 UTC
Created attachment 23756 [details]
ebuild file for 1.0beta1
Comment on attachment 23756 [details]
ebuild file for 1.0beta1
Actually its exactly the same file as earlier, just named different!
It seems that this version corrects bug #33241. At least it worked with me :) A few points: * I believe the GTK dep should be something like: >=gtk+-2.0 (the configure script shows "min_gtk_version=2.0.0"). * dodoc is forgetting to do 'RELNOTES' (although they are hideously out of date) * I don't know if gdk-pixbuf is handled differently with regard to gtk1 vs gtk2 apps. As far as I can tell, this dependency is still quite valid (for jpegPhoto attribute support I expect). The changes are fully documented here for the (various) interim releases: http://sourceforge.net/project/showfiles.php?group_id=3805 Naturally, it's the post-0.7.0_beta2 notes that are of particular relevance. A fair few bugs have been quashed, and it seems more robust. Note the following warnings for the 1.0 branch: 1.0: * Configuration file syntax The configuration file syntax has changed between 0.7.0 and 1.0 in a backwardly incompatible way. You should backup your old configuration, in case you want/need to go back to a version earlier than 1.0!! * Upgrading to GTK2 & configuration The configuration file up to 0.7.0 was saved in a locale specific encoding. When using GTK2 the UTF-8 encoding gets used. Switching back to an older version may cause configuration data corruption! I imagine that ought to be conveyed in a post-install message. rm -rf ~/.gq should resolve these sorts of issues (by doing so you'll lose server profiles and, in the case of the new version, user-defined "friendy labels" for LDAP attributes). I'll submit a slightly modified ebuild tonight if I remember to do it ;) Would be rather nice to have this in the tree (and a resolution to bug #33241 which I presume applies to the unmasked, "stable" version). Version commited for what its worth. Clicking on the schema tab I get an abort. bash-2.05b$ /usr/bin/gq Gtk-CRITICAL **: file gtkwidget.c: line 2221 (gtk_widget_realize): assertion `GTK_WIDGET_ANCHORED (widget) || GTK_IS_INVISIBLE (widget)' failed aborting... Aborted Any fixes much appreciated. If it works for you all the better. I was going to reply that I didnt have this problem. Then I tried it just to make sure, and found that I got exactly the same problem. I know that this worked fine, as (maybe) two weeks or so ago I was using it without problem. I'd have to say that some recent gtk or X library change has "caused" this. (Or I guess, gq is doing something that it shouldn't.) I guess a review of the emerge log to refresh my memory of gtk changes is in order, and a look at the source to see if it's making "proper" calls. (I see that this has been noted by other gq users - for example http://sourceforge.net/tracker/index.php?func=detail&aid=910612&group_id=3805&atid=103805 ) |
