Package: bittornado Version: 0.3.18-1 Severity: normal 1) Given 2 peers A & B (there are no other peers):
2) A runs btlaunchmany to share a directory which contains 1 torrent file and the complete downloaded file for that torrent. 3) Then B attempts to download the torrent (important: B starts btdownload *after* btlaunchmany is started on A) Then: 4) B will not see any peers. But if you restart btlaunchmany on A then B will suddenly detect peer A and start downloading from it. If you share the file on A with btdownload rather than btlaunchmany, then B will be able to start downloading right away. btlaunchmany from the 'bittorrent' package doens't have this problem. I've tested with various combinations of bttrack, btdownload and btlaunchmany from the 'bittornado' and 'bittorrent' packages. As far as I can tell, the problem is definitely with the seeding 'btlaunchmany' only registering as a peer when it starts up, but not later. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.18-4-686 (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages bittornado depends on: ii python 2.4.4-2 An interactive high-level object-o ii python-support 0.6.3 automated rebuilding support for p Versions of packages bittornado recommends: ii mime-support 3.39-1 MIME files 'mime.types' & 'mailcap -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
