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

Bug#489857: marked as done (apt output makes it hard to identify mirrors behind proxies)

Your message dated Fri, 5 Nov 2010 21:34:03 +0100
with message-id <AANLkTinOodazEunuffSzQLmDKfMO110gwQNvSfMbVa52@mail.gmail.com>
and subject line Close: apt-cache policy should not assume single directory
has caused the Debian Bug report #485520,
regarding apt output makes it hard to identify mirrors behind proxies
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.)


-- 
485520: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=485520
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: debtorrent
Severity: minor


I have debtorrent set up on my machine and I use it for both my etch/amd64
main machine and my lenny/i386 chroot. Because all my source lines in
apt.sources point to localhost, even though the debtorrent proxy then
forwards those requests to about a dozen different locations, when I use
apt-cache policy or the like, it doesn't tell me which of the forwarded-to
servers is implicated. e.g.

sammy@dakhpum:~$ apt-cache policy ia32-libs-xulrunner 
ia32-libs-xulrunner:
  Installed: (none)
  Candidate: 1.8.1.3-0.2
  Version table:
     1.8.1.3-0.2 0
        500 http://localhost etch/main Packages

which doesn't tell me whether it's a real debian package coming from
*.debian.org or if it's coming from backports.org, or some other repository
I might have used to install some particular package.

A quick grep through /var/lib/apt/lists/ shows me it's coming from
debian-multimedia.org, but it's suboptimal having to do that.

Ideally, apt-cache policy (and probalby other places) would include the path
part of the source line in the description, e.g.

        500 http://localhost:9988/www.debian-multimedia.org etch/main Packages

on my lenny/i386 chroot, that might be more like this:

        500 debtorrent://localhost/www.debian-multimedia.org etch/main Packages

because I use apt-method-debtorrent there (which incidentally is brilliant!)

I can think of other times this change might be useful, for example if there
are multiple separate repositories on the same server, perhaps a mirror
service or the like.



I expect the fix will have to be in apt rather than debtorrent, but as
debtorrent is the special case that exposes the problem, I figured this was
the place to report it. Apologies if this is the wrong place!

-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable'), (50, 'testing')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-5-amd64
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)

--- End Message ---
--- Begin Message --- 
Version: 0.7.26~exp1

These bugs were fixed with the following change:

  [ Robert Collins ]
  * Change the package index Info methods to allow apt-cache policy to be
    useful when using several different archives on the same host.
    (Closes: #329814, LP: #22354)

Seems that we missed the opportunity to close or at least
merge them back then, so i am doing that now (closing).

Thanks for reporting!


Best regards

David Kalnischkies

--- End Message ---
Reply to: