Your message dated Wed, 15 Jul 2026 18:26:16 +0100
with message-id <[email protected]>
and subject line No longer seen
has caused the Debian Bug report #704679,
regarding rtorrent: fails to recognize file sizes over 32GB
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
704679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704679
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: rtorrent
Version: 0.9.2-1
Severity: normal
Tags: lfs
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these lines ***
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Jonathan Lane <[email protected]>
To: Debian Bug Tracking System <[email protected]>
Subject: rtorrent: reports torrents sized over 32GB as <1MB
Message-ID: <20130404134319.27099.1189.reportbug@plug>
X-Mailer: reportbug 6.4.3
Date: Thu, 04 Apr 2013 09:43:19 -0400
X-Debbugs-Cc: [email protected]
Package: rtorrent
Version: 0.9.2-1
Severity: normal
Tags: lfs
Dear Maintainer,
I attempted to download a torrent of 33GB with rtorrent, the total size
of the download is listed as 0.1KB in rtorrent. It worked properly in
Deluge. A torrent of 46GB gets reported as 0.2MB in rtorrent, but
again works properly in Deluge. I suspect this has something to do with
the variable storing the download size not being large enough and
rolling over to zero.
-- System Information:
Debian Release: 7.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: armel (armv5tel)
Kernel: Linux 3.2.0-4-kirkwood
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages rtorrent depends on:
ii libc6 2.13-38
ii libcurl3 7.26.0-1+wheezy1
ii libgcc1 1:4.7.2-5
ii libncursesw5 5.9-10
ii libsigc++-2.0-0c2a 2.2.10-0.2
ii libstdc++6 4.7.2-5
ii libtinfo5 5.9-10
ii libtorrent14 0.13.2-1
ii libxmlrpc-core-c3 1.16.33-3.2
rtorrent recommends no packages.
Versions of packages rtorrent suggests:
ii dtach 0.8-2.1
ii screen 4.1.0~20120320gitdb59704-7
-- no debconf information
-- System Information:
Debian Release: 7.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: armel (armv5tel)
Kernel: Linux 3.2.0-4-kirkwood
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages rtorrent depends on:
ii libc6 2.13-38
ii libcurl3 7.26.0-1+wheezy1
ii libgcc1 1:4.7.2-5
ii libncursesw5 5.9-10
ii libsigc++-2.0-0c2a 2.2.10-0.2
ii libstdc++6 4.7.2-5
ii libtinfo5 5.9-10
ii libtorrent14 0.13.2-1
ii libxmlrpc-core-c3 1.16.33-3.2
rtorrent recommends no packages.
Versions of packages rtorrent suggests:
ii dtach 0.8-2.1
ii screen 4.1.0~20120320gitdb59704-7
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.15.7-1
I cannot reproduce this with recent versions of rtorrent (and possibly
older versions, but I didn't re-install to try there). Torrents > 32G
are correctly showing up their full size, so closing out.
J.
--
I wondered why I lost three stones last week.
--- End Message ---
