Bug#644148: marked as done (pinning broken when using sources.list.d)
Your message dated Fri, 14 Oct 2011 17:10:50 +0200
with message-id <CAAZ6_fCd3jVgF1ZwDJkTSjeNt5f8RocqRRi8y8N7vXJ0t_PGNA@mail.gmail.com>
and subject line Re: Bug#644148: pinning broken when using sources.list.d
has caused the Debian Bug report #644148,
regarding pinning broken when using sources.list.d
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 owner@bugs.debian.org
immediately.)
--
644148: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644148
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: apt
Version: 0.8.10.3+squeeze1, 0.8.15.8
Hi,
if both /etc/apt/sources.list and /etc/apt/sources.list.d/foo.list are
used, where the foo.list repository is pinned to e.g. 999, apt *still*
prefers packages from sources.list.
if sources.list is moved to sources.list.d/bar.list, everything is fine
and the pinning is properly respected.
we're hit by this bug e.g. in live-build (#573054) and have workarounded
it there with temporarily moving the sources.list to sources.list.d, but
also on any other regular/normal system.
Regards,
Daniel
--
Address: Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern
Email: daniel.baumann@progress-technologies.net
Internet: http://people.progress-technologies.net/~daniel.baumann/
--- End Message ---
--- Begin Message ---
On Mon, Oct 3, 2011 at 20:58, Julian Andres Klode <jak@debian.org> wrote:
> On Mon, Oct 03, 2011 at 12:33:30PM +0200, Daniel Baumann wrote:
>> if both /etc/apt/sources.list and /etc/apt/sources.list.d/foo.list are
>> used, where the foo.list repository is pinned to e.g. 999, apt *still*
>> prefers packages from sources.list.
>
> You can't pin packages with the same version differently. One version
> has one single pin. The pin of the source is completely irrelevant, it
> is used only to calculate the pin-priority of the version. The order
> of sources for one version is affected only by the order of the
> sources.list{,d} entries.
And this behavior is expected and documented in both manpages in
one of the first paragraphs of the description sections, so i don't see
an other good option for this bug beside closing it.
Obviously: Please feel free to reopen it if i missed something or
if something is still unclear.
Best regards
David Kalnischkies
--- End Message ---
Reply to: