Bug#489857: using a debtorrent proxy makes apt-cache policy far less useful
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. [EMAIL PROTECTED]:~$ 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) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#489857: using a debtorrent proxy makes apt-cache policy far less useful
reassign 489857 apt retitle 489857 apt output makes it hard to identify mirrors behind proxies thanks On Tue, Jul 8, 2008 at 1:57 AM, Sam Penny [EMAIL PROTECTED] wrote: 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. [EMAIL PROTECTED]:~$ 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. I've had to do that myself, both for debtorrent and other programs, and it's not fun. 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. This problem also exists with other programs that proxy access to mirrors. For example, apt-cacher, approx, apt-proxy. 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! I have reassigned it to apt, which is where the apt-cache program comes from. I think other apt programs have similar behavior though, but I don't have any examples right now. I think I recall seeing an error message (maybe the gpg key not found error) from apt-get for a proxied mirror and having some trouble figuring out which one it was. Thanks, Cameron -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
