On 4/15/2010 at 1:12, Magnus Boman <captain.magnus@gmail.com> wrote: On Wed, 2010-04-14 at 09:14 +0100, James Ogley wrote: I had a message a couple of days ago from Ryan Paul, lead developer on Gwibber. He was apologising basically for the state of the Couch-based Gwibber and telling me that he's dropping it as soon as that version (to which, I think, Ubuntu are committed for their next release) is out the door.
He's already started working on Gwibber 3.0 which uses SQLite as a backend (and so, doesn't add any new esoteric requirements).
I've done a local build and what I have to say is that, although Ryan says it's a couple of weeks (only a couple of weeks!) off being ready for public consumption, it's already more stable and usable than the Couch version.
I'm inclined to commit it to home:Riggwelter:GNOME for a bit more testing. Given that it's already ahead of the Couch version, I'm also inclined to propose it for 11.3 which would mean we could drop the whole Couch stack too as I don't think anything else uses it (hence all the pain in getting it sorted for Gwibber).
RFC before I commit.
How will that work with the "Feature and version freeze for the complete distribution" that was set to April 9th.
Well, let's all nicely look at Coolo. Gwibber situation can't get worse with the update which does not bring new dependencies to the Distribution (based on SQLIte) as compared to the current gwibber (2.29.9x.. tested up to .95) which in fact does not work reliable at all. @Coolo: I think I would like to take this opportunity for a defined exception from the version freeze to get gwibber 3.0 in. In case this is denied, I would probably have to opt to drop gwibber completely at this time (Which I assume is not what we would really like to do, as we do have an alternative option). Status of gwibber 2.29.95 at this time is: - CouchDB as a system service runs (it passes all it's internal tests. There were issues with the linking of libmozjs.so). But the service itself is not used by gwibber (only the couchdb binaries are. It launches a user session version of the db) - python-desktopcouch: The dbus service sometimes can start up correctly. Best chances are after executing rm -rf ~/.cache/desktop-couch/ ~/.local/share/desktop-couch/ ~/.config/desktop-couch/ But I did not test here neither the just released desktopcouch 0.6.4 - Some of the errors with starting python-desktopcouch actually seem to be errors in python-couchdb, like I see for example http://code.google.com/p/couchdb-python/issues/detail?id=121 very often). That's why I would like to get the exception to move to the new gwibber: with this high complexity of things that can break, chances that gwibber ever get's fully to work are low (the bugtracker at lp shows also very mixed feelings about the success). Dominique -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org