From: Kevin Buzzard on 12 Sep 2009 02:44
Theo Markettos <theom+news(a)chiark.greenend.org.uk> wrote:
> Sometimes, when faced with this situation, I've grabbed the source package
> from Debian testing/unstable and tried to munge the control file enough...
Maybe I've misunderstood you; my problem here was that even the testing
fetchmail package contained the buglet.
In the end I uninstalled the fetchmail package, downloaded the current
fetchmail tarball and did compile/make/make install. I still feel a bit dirty
about this but at least my email works now.
The remaining annoying thing is that, to undirty myself, I want to
install a new fetchmail package when debian sees fit to release one.
Is there a more clever way of noticing when this happens short of
searching for fetchmail .deb files at the standard places every few days?
From: Kevin Buzzard on 12 Sep 2009 04:21
Paul Martin <pm(a)nowster.org.uk> wrote:
>> The remaining annoying thing is that, to undirty myself, I want to
>> install a new fetchmail package when debian sees fit to release one.
> I swear by (and often at) aptitude.
But if I run
aptitude install fetchmail
I'll be back to square 1 as it will trample over my custom installation.
Aah, I see: I want
aptitude show fetchmail