Package: debtorrent
Version: 0.1.8
Severity: minor

Thanks for the fix in 0.1.8, but now I'm back to bug you again.  The
upload/download statistics seem to get mixed up between the
architecture-specific torrent and the corresponding architecture-independent
torrent.

I'd downloaded some packages, and the local status page correctly showed
very different stats for the unstable_main_binary-amd64 and
unstable_main_binary-all torrents. [1]

In aptitude I update, and new packages are listed.  Before downloading any
more, I refresh the local status page.

The download and upload stats for u_m_b-all have been copied to the
u_m_b-amd64 stats, although the size statistics differ.

The download and upload stats for the unstable_non-free_binary pair also
look suspiciously similar to each other.

The stats for the unstable_contrib_binary pair are ok (one's had nothing
downloaded, the other has 97kB).

Steve


[1] The difference is about 300MB, I installed nexuiz with its massive data
package.


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (990, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.25 (PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages debtorrent depends on:
ii  adduser                       3.108      add and remove users and groups
ii  python                        2.5.2-1    An interactive high-level object-o
ii  python-apt                    0.7.6      Python interface to libapt-pkg
ii  python-debian                 0.1.10     Python modules to work with Debian
ii  python-support                0.8.3      automated rebuilding support for P

Versions of packages debtorrent recommends:
ii  apt-transport-debtorrent 0.2.1           an APT transport for communicating
ii  python-crypto            2.0.1+dfsg1-2.1 cryptographic algorithms and proto

-- no debconf information



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

Reply via email to