Package: ftp.debian.org Severity: normal Since "proposed-updates" contain only approved updates for the next stable release it make sense to add it to the sources.lists (at least for some users).
I have done so and I'm discovering a little quirk related to its use. Until now I had etch + proposed-updates only in my sources.list. Recently I have added sid in my sources.list and added APT::Default-Release "stable" to make sure to follow etch. All packages which already got updated via proposed-updates are now candidates for upgrade to sid... that's because proposed-updates is not labelled as being part of "release a=stable" and as such is not pinned accordingly. It has: release v=4.0-updates,o=Debian,a=proposed-updates,l=Debian,c=main Whereas etch has: release v=4.0r0,o=Debian,a=stable,l=Debian,c=main I don't know how dak works but IMO it would make more sense to have proposed-updates be: release v=4.0-updates,o=Debian,a=stable,l=Debian,c=proposed-updates/main Of course, for an experienced APT user the problem is minor. It can be solved by adding this snippet to /etc/apt/preferences: Package: * Pin: release a=proposed-updates Pin-Priority: 990 But I really believe that APT::Default-Release "stable" should be enough and do the right thing with proposed-updates as well. Cheers, -- System Information: Debian Release: 4.0 APT prefers proposed-updates APT policy: (990, 'proposed-updates'), (990, 'stable'), (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-686 Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]