Bug#365584: mailman installs, but is still reported as upgradeable afterwards
On Mon, May 01, 2006 at 02:11:08PM +0200, Artur R. Czechowski wrote:
> On Mon, May 01, 2006 at 10:27:41AM +0100, Martin A. Brooks wrote:
>> hannon:~# apt-get install mailman
>> Reading package lists... Done
>> Building dependency tree... Done
>> Suggested packages:
>> python2.3-korean-codecs python2.2-korean-codecs python-japanese-codecs
>> listadmin
>> The following packages will be upgraded:
>> mailman
>> shannon:~# apt-get upgrade
>> Reading package lists... Done
>> Building dependency tree... Done
>> The following packages will be upgraded:
>> mailman
> [cut]
>> Preparing to replace mailman 2.1.7-2.1.8rc1-1 (using
>> .../mailman_0%3a2.1.7-2.1.8rc1-1_i386.deb) ...
> [cut]
>> ...and so on. Subsequent upgrades simply repeat the installation
>> procedure.
> I noticed the same behavior using aptitude. I suspect that the reason is
> misinterpretting epoch by APT library.
Indeed. I've submitted a patch to the same APT library. Because
dak/katie uses the very same apt library to compare versions, it
suffers from the same bug and I cannot work around the problem by
uploading an epoch-less version until apt is fixed (and the fixed
version on ftp-master, which could take as long as release of etch?).
--
Lionel
Reply to: