Bug#579758: Explicit zero epoch confuses apt

Goswin von Brederlow goswin-v-b at web.de
Sat May 1 10:41:21 UTC 2010


Salvatore Bonaccorso <salvatore.bonaccorso at gmail.com> writes:

> tag 579758 + pending confirmed
> thanks
>
> Hi Goswin
>
> On Fri, Apr 30, 2010 at 04:54:28PM +0200, Goswin von Brederlow wrote:
>> Package: libconfigreader-simple-perl
>> Version: 1.28-2
>> Severity: minor
>> 
>> Hi,
>> 
>> Package: libconfigreader-simple-perl
>> Architecture: all
>> Version: 1.28-2
>> Conflicts: squidtaild (<< 0:2.1a6-5.4)
>> Depends: perl
>> Replaces: squidtaild (<< 0:2.1a6-5.4)
>> 
>> You explicitly specified a zero epoch for the version of squidtaild.
>> Dpkg automatically surpresses a 0 epoch as that is already implied if
>> no epoch is given and saves dpkg from keeping an extra flag for its
>> presence.
>> 
>> Apt on the other hand uses the raw strings of the fields in a hash
>> function which is then used to check if the available and installed
>> package are the same. With dpkg dropping the zero epoch apt gets
>> confused and considers the installed and available
>> libconfigreader-simple-perl 1.28-2 to be different packages and wants
>> to update it again and again. See Bug#574956.
>> 
>> While we wait for the apt authors to device a fix for this please
>> consider uploading a new package without needlessly specifying the
>> zero epoch to avoid the problem.
>
> Yes, Gregor Hermann aleady fixed that in Debian Perl Group svn
> repository, the upload is pending. I'm tag'ing this as pending.
>
> Bests
> Salvatore

Thanks. I saw that after sending the bugreport. Sorry for wasting time.

MfG

        Goswin





More information about the pkg-perl-maintainers mailing list