On Wed, Sep 23, 2009 at 12:28:03PM -0700, Russ Allbery wrote: > Josh Triplett <[email protected]> writes: > > On Sat, Sep 19, 2009 at 01:05:21PM -0700, Russ Allbery wrote: > > >> I must be missing something, but doesn't that error message indicate a bug > >> in gtk2-engines, not in gnubg? > > > Except I don't see the problem in any other GTK+ app, just gnubg. > > Yeah, good point. > > >> Hm, this and things similar to it seem to be frequently reported bugs > >> against gtk2-engines, but none of the bug logs provide anything > >> particularly helpful in understanding how to resolve them. > > > So I see. Ow. > > > Perhaps we need some help from upstream? > > The upstream development process for this package is unfortunately a bit > difficult to deal with, since upstream only develops in CVS and > practically never makes an official release. I'm sure all the code has > changed considerably since the 0.90 tarball, and I'm guessing upstream > isn't going to be interested in trying to figure out what's not working > with 0.90.
I actually meant upstream of gtk2-engines. > So, what that means is it's probably time for me to try to find another > stable CVS snapshot and package that. I'd been thinking I was probably > due anyway. I'll try to get to that relatively soon. Happy to test it once you have some experimental packages. - Josh Triplett -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
