Your message dated Mon, 25 Feb 2008 08:41:25 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#460586: deluge 0.5.8.4-1
has caused the Debian Bug report #460586,
regarding share ratio resets if less than 1.000
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.)
--
460586: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=460586
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: deluge-torrent
Version: 0.5.8-1
Severity: normal
--- Please enter the report below this line. ---
I don't use duluge very often, in general I have only one torrent active.
Once the download of the torrent is finished the seeding starts and the share
ratio grows normally.
Than I close deluge and shutdown.
The next time I use deluge the share ratio of the torrent is resetted yo 0.000
if the previous time was less than 1.
In general I leave the torrens in seeding untill the ratio is about 1.5 ,but in
this way (and with many torrents) is difficult to remember when stop it.
--- System information. ---
Architecture: i386
Kernel: Linux 2.6.22-3-686
Debian Release: lenny/sid
500 unstable ftp.it.debian.org
500 testing security.debian.org
--- Package information. ---
Depends (Version) | Installed
=============================================-+-================
libboost-date-time1.34.1 (>= 1.34.1-2.1) | 1.34.1-4+b1
libboost-filesystem1.34.1 (>= 1.34.1-2.1) | 1.34.1-4+b1
libboost-thread1.34.1 (>= 1.34.1-2.1) | 1.34.1-4+b1
libc6 (>= 2.7-1) | 2.7-5
libgcc1 (>= 1:4.1.1-21) | 1:4.3-20080104-1
librsvg2-common | 2.18.2-1
libssl0.9.8 (>= 0.9.8f-1) | 0.9.8g-3
libstdc++6 (>= 4.2.1-4) | 4.3-20080104-1
notification-daemon | 0.3.7-1+b1
python (>= 2.4) | 2.4.4-6
python (<< 2.6) | 2.4.4-6
python-dbus | 0.82.4-1
python-glade2 | 2.12.1-1
python-gtk2 | 2.12.1-1
python-notify | 0.1.1-2
python-pyopenssl | 0.6-2.3
python-support (>= 0.7.1) | 0.7.6
python-xdg | 0.15-1.1
zlib1g (>= 1:1.1.4-1) | 1:1.2.3.3.dfsg-8
--- End Message ---
--- Begin Message ---
Federico Muciaccia a écrit :
I've tryed with Deluge o.5.8.4-1: the bug doesn't appear any more.
Maybe it has been fixed, as you say.
May I close this bug now (or let some other users test it)?
Regards
Federico
Let's close it for now. If something else can reproduce it, a new bugn
report will be opened.
For now, the bug is not reproducible anymore neither by submitter nor by
package's maintainer.
Best regards, Adam.
--- End Message ---
