On 10/14/07, Julian Gilbey <[EMAIL PROTECTED]> wrote:
> Here's my sources.list:
>
> -----
> deb http://localhost:9988/ftp.uk.debian.org/debian/ testing main contrib 
> non-free
> deb-src http://localhost:9988/ftp.uk.debian.org/debian/ testing main contrib 
> non-free

It's not recommended to use DebTorrent to download source packages.
Though it should work, it will just be slower than a normal download,
and won't use peer-to-peer to download source packages as that isn't
currently possible. I recommend you change your deb-src lines to
remove the localhost:9988 from them.

> deb http://localhost:9988/security.debian.org lenny/updates main contrib 
> non-free
> deb-src http://localhost:9988/security.debian.org lenny/updates main contrib 
> non-free

DebTorrent currently only supports the main archive due to extra
requirements that are currently only met by the main archive
(specifically the sub-piece files available at
http://merkel.debian.org/~ajt/extrapieces/). Though it should work
without these files, it's difficult for me to test all possible
archives to make sure they do work, so I focus on only the largest and
most popular. For example, in this case the empty Packages files for
security's contrib and non-free are causing issues (which I'll look
into and try and fix).

> # volatile
> deb http://localhost:9988/volatile.debian.org/debian-volatile etch/volatile 
> main contrib non-free
> deb-src http://localhost:9988/volatile.debian.org/debian-volatile 
> etch/volatile main contrib non-free

Again, this archive is not yet supported, though it seems to be working for you.

> # libdvdcss
> deb http://localhost:9988/download.videolan.org/pub/videolan/debian sid main
> deb-src http://localhost:9988/download.videolan.org/pub/videolan/debian sid 
> main
>
> # Multimedia
> deb http://localhost:9988/www.debian-multimedia.org testing main
> deb-src http://localhost:9988/www.debian-multimedia.org testing main

Same with these 2 archives. Since you're having issues with
DebTorrent, I would recommend reverting these unsupported archives to
not use DebTorrent. Then you can test it using only the main archive,
and see if there are any issues (which should also be easier to
diagnose then, if there are any). If everything is working fine for a
while, then maybe try adding these back one at a time to see if there
are any problems (I'm thinking a time period of weeks here).

> -----
>
> Here's the output of dselect update:
>
> -----
> burnside:~ # dselect update
[snip]
> Failed to fetch 
> http://localhost:9988/security.debian.org/dists/lenny/updates/main/i18n/Translation-en_GB.bz2
>   Connection failed
> Failed to fetch 
> http://localhost:9988/security.debian.org/dists/lenny/updates/contrib/i18n/Translation-en_GB.bz2
>   Connection failed
> Failed to fetch 
> http://localhost:9988/security.debian.org/dists/lenny/updates/non-free/i18n/Translation-en_GB.bz2
>   Connection failed
> Failed to fetch 
> http://localhost:9988/security.debian.org/dists/lenny/updates/main/binary-i386/Packages.gz
>   Connection failed
> Failed to fetch 
> http://localhost:9988/security.debian.org/dists/lenny/updates/main/source/Sources.gz
>   Connection failed

These errors are all related to the security.debian.org archive. After
looking through the log file you sent (thanks!), it seems that the
HTTP cache downloader for security.debian.org got hung up at some
point before this update. So, all new requests are being queued,
waiting for the old one to finish. This is obviously a bug, and I'll
be looking into a way to implement timeouts for this, but I'm curious
how this downloader got hung up. So, I was wondering if you could
search in the log file for the last time the downloader was working.
You should be able to find it easily using this command:

grep 'CacheRequest(security.debian.org)' debtorrent-client.log

and looking for the last line(s) that occurred in time before the
update (i.e. before 2007-10-14 09:30:01). If you could send me some of
the relevant log lines around that time I would be very grateful.

Thanks for all the extra info,
Cameron



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to