Bug#351056: many packages involved, not just python-twisted

[Goswin von Brederlow <brederlo@informatik.uni-tuebingen.de>]

Andrew Schulman <andrex@alumni.utexas.net> writes:

>> > I run apt-get clean, and then every time I run apt-get
>> > dist-upgrade it wants to reinstall the same list of packages.  A.
>>
>> Does 'apt-cache policy foobar' list a version twice for the packages?
>
> Yes:
>
> $ apt-cache policy screen
> screen:
>   Installed: 4.0.2-4.1
>   Candidate: 4.0.2-4.1
>   Version table:
>      4.0.2-4.1 0
>         300 http://http.us.debian.org unstable/main Packages
>      4.0.2-4.1 0
>         200 http://amd64.debian.net stable/main Packages
>      4.0.2-4.1 0
>         990 http://amd64.debian.net testing/main Packages
>  *** 4.0.2-4.1 0
>         100 /var/lib/dpkg/status
>
> Same for all of the other packages in the list.  So is this apt-get's 
> fault, or the package archives?  If it's the package archives, then all 
> users with these same lines in their sources.list files should be having 
> the same symptoms as me.
>
> Thanks, Andrew.

Compare the md5sums of the debs. They should all differ (to produce
this output).

I don't get why stable and testing differ though. That should not even
be possible. They are the same file on the same fs.

goswin@ivanova:~$ grep-dctrl -X -P screen /org/amd64.debian.net/ftp/debian/dists/{stable,testing}/main/binary-amd64/Packages -s Package,Version,MD5sum   
Package: screen
Version: 4.0.2-4.1
MD5sum: 4913a5102ecb102d6ec43109084d1232

Package: screen
Version: 4.0.2-4.1
MD5sum: 4913a5102ecb102d6ec43109084d1232


In what order do you have them in sources.list? Maybe they only get
merged properly in some orders.

Which package does apt-get download? The amd64.debian.net one as the
pining dictates or the ftp.debian.org one as it is first? Maybe it
wants one but the downloader screws up and picks the other since it
has the same version.

MfG
        Goswin