Bug#574956: libconfigreader-simple-perl: keeps upgrading - to the same version!

[Ansgar Burchardt]

reassign 574956 aptitude
thanks

Celejar <celejar at gmail.com> writes:
> gregor herrmann <gregoa at debian.org> wrote:
>> On Mon, 22 Mar 2010 09:13:53 -0400, Celejar wrote:
>> >   Version table:
>> >      1.28-2 0
>> >         500 http://localhost sid/main Packages
>> >  *** 1.28-2 0
>> >         100 /var/lib/dpkg/status
>> > 
>> > Aptitude keeps reporting that the package can be updated, from
>> > 1.28-2 to 1.28-2 ?!  When I say go, it claims that it has
>> > successfully upgraded it - but it then reports that the package is
>> > upgradeable - from 1.28-2 to 1.28-2 ... What on earth is going on
>> > here?  I'm not even sure if this is a bug in this package, or in
>> > aptitude, or somewhere else.
>> 
>> Thanks for your bug report, that's interesting indeed :)
>> Some quick thoughts:
>> * I'm sure this is not a problem of the package, the package is not
>>   doing anything else than having a version, the handling of upgrades
>>   etc. is handled by apt* and friends.
>
> I figured as much; I'm just trying to understand why I only see this
> problem with this particular package.
>
>> * I'm not surprised that aptitude offers an upgrade; in my experience
>>   packages from a mirror have precedence over locally installed
>>   packages, even if they have the same version.  
>
> Everything's both localhost and from the mirror; aptitude is pointed
> toward an approx installation running on localhost.
>
>> * The interesting thing now is why the upgrade doesn't happen; some
>>   random thoughts: Do you have some pinning in /etc/apt/preferences{,.d/*}?
>
> No.
>
>>   Does an aptitude update change anything? Doesn apt-get behave the
>
> No change after repeated updates.  Same with apt-get.
>
>>   same way as aptitude? What happens if you exchange localhost with
>>   some "real" mirror?
>
> Same.
>
> So, in summary:
>
> My system endlessly tries to upgrade the package to the same version,
> even after repeated updating, with both apt and aptitude, no pinning,
> and even when cutting approx out of the loop and using a mirror
> directly.

A random idea: Does removing the .deb from /var/cache/apt/archives help?

In any case, bug reassigned to aptitude for now.  The bug might well be
in some library, but the aptitude maintainers should know more about
this than the Perl Group ;)

Regards,
Ansgar