Release file wrong? (problems with apt-get 0.5.0)

[Brian May <bam@debian.org>]

Hello,

I notice that the release file for some distributions has stable:

Archive: stable
Component: main
Version: 2.2r2
Origin: Debian
Label: Debian
Architecture: i386

where in other places it has potato:

Archive: potato
Component: updates/main
Version: 2.2
Origin: Debian
Label: Debian-security
Architecture: i386

I believe this causes problems with apt-get 0.5.0, because it does not
realize that they are the same distribution.

(hmmm... perhaps that version 2.2 should be updated to 2.2r2 for the
same reason?)

So I can have:

Package: *
Pin: release a=stable
Pin-Priority: 1001

but now, it apt-get will try to downgrade bind from the secure version
to the insecure version:

snoopy:~# apt-get -s  install bind          
Reading Package Lists... Done
Building Dependency Tree... Done
The following packages will be DOWNGRADED
  bind 
0 packages upgraded, 0 newly installed, 1 downgraded, 0 to remove and 182  not upgraded.
Inst bind (1:8.2.2p7-1 Debian:2.2r2/stable)
Conf bind (1:8.2.2p7-1 Debian:2.2r2/stable)

So, if instead I have

Package: *
Pin: release a=potato
Pin-Priority: 1001

instead, this problem is fixed.

snoopy:~# apt-get -s  install bind 
Reading Package Lists... Done
Building Dependency Tree... Done
Sorry, bind is already the newest version.
0 packages upgraded, 0 newly installed, 0 to remove and 422  not upgraded.

so, while a good work around is to have entries for both potato and
stable, I think that all Release files should be changed to either
have stable or potato.

Comments?

(have I correctly understood the situation?)
-- 
Brian May <bam@debian.org>