On Thu, Jul 22, 2010 at 12:56 PM, Stefano Zacchiroli <[email protected]> wrote: > So, re-doing the upgrade gwibber 1.x -> gwibber 2.x, I've re-noticed the > following (and this time grabbed the log): > > Preparing to replace gwibber 1.2.0+bzr358-3 (using gwibber_2.31.2-1_all.deb) > ... > rm: cannot remove `/etc/indicators/messages/applications/gwibber.indicator': > No such file or directory > rmdir: failed to remove `/etc/indicators/messages/applications/': No such > file or directory > Unpacking replacement gwibber ... > > It does not cause an upgrade failure, but it smells of something that > should be double checked in some pre* script.
I'll take care of it with next update! > Just a couple of suggestions: > > - you might want to be more precise like "if gwibber fails to start due > to XXXXX, please follow these steps" Sure. > - I wonder, can't this be automated for the user? I believe quite some > people unfamiliar with (desktop)couch will it that nail. Is that a bug > / missing configuration generality in couchdb by any means? This bug is mostly related to separation of couchdb and couchdb-bin packages. I'm looking closely now for more details. > Nevertheless, I'm now denting with gwibber2 \o/ I'll report further > feedback if anything relevant appears in the next few days. The most known issues are, - missing tweets - facebook updates / receiving updates - pidgin integration (you already reported this) etc -- Kartik Mistry Debian GNU/Linux Developer IRC: kart_ | Identica: @kartikm -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
