Debian Bug report logs - #511181
bittorrent: bad data from tracker - error without details from btdownloadcurses

version graph

Package: bittorrent; Maintainer for bittorrent is Michael Janssen <jamuraa@debian.org>; Source for bittorrent is src:bittorrent.

Reported by: Russell Coker <russell@coker.com.au>

Date: Thu, 8 Jan 2009 07:12:01 UTC

Severity: normal

Found in version bittorrent/3.4.2-11.1

Reply or subscribe to this bug.

Toggle useless messages

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to debian-bugs-dist@lists.debian.org, Michael Janssen <jamuraa@debian.org>:
Bug#511181; Package bittorrent. (Thu, 08 Jan 2009 07:12:03 GMT) Full text and rfc822 format available.

Acknowledgement sent to Russell Coker <russell@coker.com.au>:
New Bug report received and forwarded. Copy sent to Michael Janssen <jamuraa@debian.org>. (Thu, 08 Jan 2009 07:12:03 GMT) Full text and rfc822 format available.

Message #5 received at submit@bugs.debian.org (full text, mbox):

From: Russell Coker <russell@coker.com.au>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: bittorrent: bad data from tracker - error without details from btdownloadcurses
Date: Thu, 08 Jan 2009 18:09:52 +1100
Package: bittorrent
Version: 3.4.2-11.1
Severity: normal

I am trying to set up my own torrent.  For some reason bttrack and
btdownloadcurses don't like talking to each other.

btdownloadcurses gives the error "bad data from tracker -" which doesn't
help much.  It seems that line 135 of
/usr/share/python-support/bittorrent/BitTorrent/Rerequester.py doesn't
do what is necessary to prepare a visible error message.

I am probably doing something wrong, but unless I can get a useful error
message from btdownloadcurses it seems unlikely that I will be able to
solve it.




Information forwarded to debian-bugs-dist@lists.debian.org, Michael Janssen <jamuraa@debian.org>:
Bug#511181; Package bittorrent. (Sun, 26 Jul 2009 10:09:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to russell@coker.com.au:
Extra info received and forwarded to list. Copy sent to Michael Janssen <jamuraa@debian.org>. (Sun, 26 Jul 2009 10:09:05 GMT) Full text and rfc822 format available.

Message #10 received at 511181@bugs.debian.org (full text, mbox):

From: Russell Coker <russell@coker.com.au>
To: 511181@bugs.debian.org
Subject: found the problem
Date: Sun, 26 Jul 2009 19:55:44 +1000
btmakemetafile.bittorrent test http://www.example.com:8000

It turns out that my mistake was to use the above command instead of the below 
command to create the metafile.

btmakemetafile.bittorrent test http://www.example.com:8000/announce

I suggest that the btmakemetafile program give a warning when "/announce" is 
not at the end of the URL.  This won't be adequate to solve the problem but 
will be a good step towards alleviating it.

What we really need is to have the tracker logs indicate the URL that was used 
for accessing itself.  If something obviously wrong like missing "/announce" 
is done then it would be good to have that logged directly.




Send a report that this bug log contains spam.


Debian bug tracking system administrator <owner@bugs.debian.org>. Last modified: Fri Apr 25 09:35:31 2014; Machine Name: buxtehude.debian.org

Debian Bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.