Bug#381282: apt-setup: stable -> testing
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
It would be great to see these bugs get some attention of the maintainers...
So I try to explain what I know about this issue:
The reason for this situation is, that apt-setup calls the system
database for the value of the key 'mirror/suite'. This key gets set on
installation.
So, if someone installed sarge back when it was in testing state, the
database got correctly set with that value 'testing'. After sarge
changed to stable state, the user changed 'testing' to 'stable' or
'sarge' in /etc/apt/sources.list but didn't set the respective key in
the internal system database.
So from that moment on the internal system database and sources.list
aren't synchronous anymore concerning the system state. I don't know of
a user viable way to set 'mirror/suite' to the actual state.
caspar
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFuKYGzpQ+GCsPNMERAllPAKC4EkjTFFAzCACQVniaMpP1wdiD7gCg2Sjb
IQop/H17Ts7qxwhTvyWdOW4=
=oJ1k
-----END PGP SIGNATURE-----
Reply to: