On Wed, Jul 21, 2010 at 10:23:34PM +0530, Kartik Mistry wrote: > > The first disclaimer of mine is that I built my own copy, as the > > location above only have one .deb out of three, is that on purpose? > oops. Fixed!
Wonderful, thanks.
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.
> Here is fix:
>
> README for Debian
> -----------------
>
> If gwibber fails to start, please follow these steps:
That's did it, thanks!
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"
- 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?
Nevertheless, I'm now denting with gwibber2 \o/ I'll report further
feedback if anything relevant appears in the next few days.
Thanks!
Cheers.
--
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
z...@{upsilon.cc,pps.jussieu.fr,debian.org} -<>- http://upsilon.cc/zack/
Dietro un grande uomo c'è ..| . |. Et ne m'en veux pas si je te tutoie
sempre uno zaino ...........| ..: |.... Je dis tu à tous ceux que j'aime
signature.asc
Description: Digital signature
