[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#394619: marked as done (apt-get: not favoring sources listed first in sources.list)

Your message dated Thu, 13 Aug 2015 14:55:16 +0200
with message-id <20150813125516.GA20180@crossbow>
and subject line Re: apt-get don't adhere the order from sources.list
has caused the Debian Bug report #355284,
regarding apt-get: not favoring sources listed first in sources.list
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.)


-- 
355284: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=355284
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: apt
Version: 0.6.46.2
Severity: normal


I have several Debian testing machines on my local network, so I keep a partial mirror of 
installed packages on one of them (the "clayton1" machine at the top of my sources.list). In 
the past, the machine this bug report is being filed on would take packages first from 
clayton1, and anything it didn't find there would it would pull down from ftp.kr.debian.org.

For the past several weeks, apt-get has been insisting on downloading everything from 
ftp.kr.debian.org, and ignoring packages already present on my clayton1 local mirror.

(apt-get has been observed recently taking packages from clayton1 that do not exist on 
"http://ftp.kr.debian.org/debian/ testing", so I know the clayton1 mirror still works.)

-- Package-specific info:

-- apt-config dump --

APT "";
APT::Architecture "i386";
APT::Build-Essential "";
APT::Build-Essential:: "build-essential";
APT::Authentication "";
APT::Authentication::TrustCDROM "true";
APT::Default-Release "testing";
Dir "/";
Dir::State "var/lib/apt/";
Dir::State::lists "lists/";
Dir::State::cdroms "cdroms.list";
Dir::State::userstatus "status.user";
Dir::State::status "/var/lib/dpkg/status";
Dir::Cache "var/cache/apt/";
Dir::Cache::archives "archives/";
Dir::Cache::srcpkgcache "srcpkgcache.bin";
Dir::Cache::pkgcache "pkgcache.bin";
Dir::Etc "etc/apt/";
Dir::Etc::sourcelist "sources.list";
Dir::Etc::sourceparts "sources.list.d";
Dir::Etc::vendorlist "vendors.list";
Dir::Etc::vendorparts "vendors.list.d";
Dir::Etc::main "apt.conf";
Dir::Etc::parts "apt.conf.d";
Dir::Etc::preferences "preferences";
Dir::Bin "";
Dir::Bin::methods "/usr/lib/apt/methods";
Dir::Bin::dpkg "/usr/bin/dpkg";
DPkg "";
DPkg::Pre-Install-Pkgs "";
DPkg::Pre-Install-Pkgs:: "/usr/sbin/dpkg-preconfigure --apt || true";

-- (no /etc/apt/preferences present) --


-- /etc/apt/sources.list --

deb http://clayton1/debian/ testing main
deb http://ftp.kr.debian.org/debian/ testing main contrib non-free

#deb cdrom:[Debian GNU/Linux testing _Etch_ - Official Snapshot i386 Binary-1 (20051111)]/ etch contrib main

deb http://security.debian.org/ testing/updates main contrib non-free

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (990, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-tp600e.2
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages apt depends on:
ii  debian-archive-keyring       2006.01.18  GnuPG archive keys of the Debian a
ii  libc6                        2.3.6.ds1-4 GNU C Library: Shared libraries
ii  libgcc1                      1:4.1.1-13  GCC support library
ii  libstdc++6                   4.1.1-13    The GNU Standard C++ Library v3

apt recommends no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
Hi,

On Mon, Mar 27, 2006 at 10:35:48PM +0200, General Stone wrote:
> It affects only if server1.example.org hasn't a Release.gpg
> So, it should be added for sources, too and should be documented.

In the meantime this is the case for sources, too.

There are multiple ways (some better documented than others) to sidestep
this behaviour, but the best one is trusted=yes in sources.list, see the
manpage. Anyway, as this is behaviour as designed, it isn't a bug and
hence the report can be closed.


Best regards

David Kalnischkies

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: