On 2013-03-31 19:18 +0200, Nick Black wrote:

> Sven Joachim left as an exercise for the reader:
>> Is it possible that the package you installed locally is different from
>> the one on http://www.sprezzatech.com/apt/, despite having the same
>> version number?  Compare your output with what I get here:
>
> it is possible that i installed a different one at some point earlier with
> the same version number, yes, but right now i am definitely installing the
> same one.
>
> [skynet](0) $ sha1sum /var/cache/apt/archives/apt_0.9.7.8-SprezzOS1_amd64.deb 
> 8ddc78c3d5e913a36846ea05b340c95bc4c1ada8  
> /opt/sprezzatura/apt/pool/main/a/apt/apt_0.9.7.8-SprezzOS1_amd64.deb
> [skynet](0) $ qemfd sha1sum 
> /opt/sprezzatura/apt/pool/main/a/apt/apt_0.9.7.8-SprezzOS1_amd64.deb
> 8ddc78c3d5e913a36846ea05b340c95bc4c1ada8  
> /var/cache/apt/archives/apt_0.9.7.8-SprezzOS1_amd64.deb
> [skynet](0) $ 
>
> also, i've got users who're seeing this same issue, and who never should have
> had any different package, leading me to suspect the package. you can inspect 
> it, if
> you'd like, via
>
>       http://www.sprezzatech.com/apt/swip/amd64-apt.html
>
>
>> By default, "aptitude show" only prints the status of the "candidate"
>> version, and if that one is different from the installed version, you'll
>> see that the package is "not installed", see #539978ยน.  You can request
>> it to show all versions with the -v option.
>
> Ahhh and indeed ... interesting. There's three entries: the Debian 0.9.7.8, 
> the
> currently installed 0.9.7.8-SprezzOS1, and another 0.9.7.8-SprezzOS1. The 
> first
> has no hash listed(!), and a compressed size of 0.

This seems to be the root of the problem, but I don't see how running
into it is possible.

> So I accept that I most likely installed some handmade package during
> development.

I do this regularly with packages that I maintain, and I still cannot
reproduce your problem with them.

> My question would be: is this state useful/desirable? Would you
> like a patch that, say...I'm not sure still exactly what the issue is,
> really. Nor do I understand how it affected people beyond my dev box >:|.

Well, I don't either.  If I find time in the next days I may add the
SprezzOS repo to my apt sources in a throwaway chroot to try and
reproduce this problem, unless somebody beats me to it.

Cheers,
       Sven


--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to