You wrote:
> I had this yesterday on my 32bit intrepid installation and it was due to
> me having previously installed from source but this time installing from
> the .deb.   These are the steps that Thomas recommended I take and they
> worked for me:-
> 
> (1) Un-install the .deb
> (2) Grab the source tarball (or use the git checkout) and "sudo make
> uninstall"
> (3) Re-install the .deb

I think this really has to be made a FAQ ;) Some more details so you
know what's going on: "make install" from the gPodder source installs
the gPodder Python modules in a different location than what Debian's
python-support does. So, if you have installed some other version from
source via "make install" and also install gPodder from a .deb package,
you will most likely mix up some modules from here and there, resulting
in such a bug.

On the other hand, this is a good thing, because if it won't fail so
obviously,
it might fail in some other strange way (or even not fail at all, but
just
provide less features and old bugs).

Thomas

_______________________________________________
gpodder-devel mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/gpodder-devel

Reply via email to