Re: wicd fails to start after upgrade

["Wayne <linuxtwo@gmail.com>" <linuxtwo@gmail.com>]

Sebastian wrote:
> On Fri, Jan 29, 2010 at 02:36PM -0500, Wayne <linuxtwo@gmail.com> wrote:
>
> > > > Sebastian wrote:
> > > > > After the last upgrade wicd fails to start. It also stopped writing it's logs and when I call it directly by just entering 'wicd' I get following error:

<---Snip--->
> >   [...snip...]
> >  I first run apt-listbugs on all of
> > those packages before I download any of them
>
> Yes, I have apt-listbugs installed and working here as well, yet I
> can't remember any bugs for wicd coming up before the upgrade - of
> course it was late in the night and who knows what I was seeing ;-)
>
> Anyway, I removed unstable from the sources.list and tried removing
> and re-installing wicd but I can still only get 1.7.0-2
>
> > Yes 'apt-cache policy wicd' will show the packages in every dist you
> > have in the sources.list, I believe. Here it shows both
> > testing/unstable.
>
> thanks, 'apt-cache policy wicd' shows
> wicd:
>   Installed: 1.7.0-2
>   Candidate: 1.7.0-2
>   Version table:
>  *** 1.7.0-2 0
>         700 http://ftp.ie.debian.org testing/main Packages
>         100 /var/lib/dpkg/status
>
> hmmm... 1.7.0-2 is testing??? And no 1.6...?
> Getting more and more confused here... - Any hints?
> ]

Humm....  After removing unstable from sources.list did you do another
aptitude update?

I just did another update, here it is:
VT/dev/pts/0 wtopa@dj-SQUEEZE]
~$ policy wicd
wicd:
  Installed: 1.6.2.2-4
  Candidate: 1.7.0-2
  Version table:
     1.7.0-2 0
        990 http://mirrors.geeks.org squeeze/main Packages
        600 http://mirror.rit.edu unstable/main Packages
 *** 1.6.2.2-4 0
        100 /var/lib/dpkg/status
Note that I have aliased apt-cache policy in my .bashrc
as policy.

It seems that wicd has migrated to squeeze/testing since we started this 
discussion.  One thing I have noticed in the last 4-6 months though is 
that there seems to be more packages entering testing that fail 
apt-listbugs then there used to be.

So to test that, I tried apt-listbugs, which I recall had it's own bugs 
after my last upgrade. ;_(  I had to upgrade it, again now, to test my 
theory so... Note my alias for apt-listbugs used here:

[VT/dev/pts/0 wtopa@dj-SQUEEZE]
~$ bugs list wicd=1.6.2.2-4 wicd=1.7.0-2
Reading package fields... Done
Reading package status... Done
Retrieving bug reports... Done
Parsing Found/Fixed information... Done

That says that both versions should work. To see which one will be 
installed I did

aptitude -s install wicd

Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Reading task descriptions... Done
The following NEW packages will be installed:
  python-wicd{a} wicd-daemon{a} wicd-gtk{a}
The following packages will be REMOVED:
  python-urwid{u}
The following packages will be upgraded:
  wicd
1 packages upgraded, 3 newly installed, 1 to remove and 12 not upgraded.

That is version 1.7.0-2.

As I am not having a problem with my current version, I won't upgrade 
wicd for a while.  You, on the other hand, can do an aptitude update and 
then safe-upgrade and, it might have been fixed.  I say might because it 
just migrated and I am leery of packages coming into testing, as I 
mentioned above.

> Thanx a mil Wayne

No problem Sabestian, just hope it goes well for you, this time.

Wayne