Your message dated Thu, 24 Jan 2019 10:02:04 +0100
with message-id <[email protected]>
and subject line Re: proposed-updates is not part of "release a=stable"
has caused the Debian Bug report #428381,
regarding proposed-updates is not part of "release a=stable"
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
428381: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=428381
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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)
--- End Message ---
--- Begin Message ---
apt pinning isn't really the domain of dak; I'm not sure what could be
improved on the apt side here.
Making p-u a component (such as main) of stable doesn't work (as that
would for example require stable's Release to be updated); also
components are not nice to use on the dak side.
Ansgar
--- End Message ---
