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

Bug#634669: marked as done (apt: unable to determine failed source from update messages)

Your message dated Fri, 14 Aug 2015 00:12:50 +0200
with message-id <20150813221250.GA31996@crossbow>
and subject line Re: apt: unable to determine failed source from update messages
has caused the Debian Bug report #634669,
regarding apt: unable to determine failed source from update messages
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.)


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


apt-get update prints only the server and the release directory of the
downloaded package lists.

When multiple package sources are mirrored on the same server it is
impossible to tell what source failed to download.

debian security and debian backports work around this issue by placing
the package list in specially named release directory which can then be
recognized in the apt output but some other package authors that publish
debian repositories are less careful and name the release directory
after the Debian release, just like the Debian main repository does.

It is then impossible to tell apart these repositories and the Debian
main repository in the apt output when downloaded from the same mirror
server.


-- Package-specific info:

-- (/etc/apt/preferences present, but not submitted) --


-- (/etc/apt/sources.list present, but not submitted) --


-- System Information:
Debian Release: wheezy/sid
  APT prefers stable
  APT policy: (900, 'stable'), (500, 'testing'), (410, 'unstable'), (200, 'experimental'), (111, 'oldstable'), (107, 'natty-updates'), (107, 'natty')
Architecture: amd64 (x86_64)

Kernel: Linux 3.0.0-rc3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages apt depends on:
ii  debian-archive-keyring  2010.08.28       GnuPG archive keys of the Debian a
ii  gnupg                   1.4.10-4         GNU privacy guard - a free PGP rep
ii  libc6                   2.11.2-10        Embedded GNU C Library: Shared lib
ii  libgcc1                 1:4.6.1-1        GCC support library
ii  libstdc++6              4.6.1-1          GNU Standard C++ Library v3
ii  zlib1g                  1:1.2.3.4.dfsg-3 compression library - runtime

apt recommends no packages.

Versions of packages apt suggests:
ii  apt-doc                0.8.10.3+squeeze1 Documentation for APT
ii  aptitude               0.6.3-3.2         terminal-based package manager (te
ii  bzip2                  1.0.5-6           high-quality block-sorting file co
ii  dpkg-dev               1.15.8.11         Debian package development tools
ii  lzma                   4.43-14           Compression method of 7z format in
pn  python-apt             <none>            (no description available)

-- no debconf information

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

On Tue, Jul 19, 2011 at 01:08:38PM +0200, Michal Suchanek wrote:
> It is then impossible to tell apart these repositories and the Debian
> main repository in the apt output when downloaded from the same mirror
> server.

Nowadays the path is shown in the output, not only the host, so that
issue is resolved in the meantime. Hence closing.

Best regards

David Kalnischkies

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: