aybassiouny / pyroscope

Automatically exported from code.google.com/p/pyroscope
GNU General Public License v2.0
0 stars 0 forks source link

rtmv fails if download has been moved by rutorrent or automatically #41

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
To move completed downloads to another folder, I have the following in my 
.rtorrent.rc:

directory = /export/Incoming/rTorrent/

schedule = 
watch_directory_1,10,10,"load_start=/data/Torrent/Music/*.torrent,d.set_custom1=
Music,d.set_custom2=/export/Incoming/Complete/Music/"

system.method.set_key = 
event.download.finished,move_complete,"d.set_directory=$d.get_custom2=;d.set_cus
tom1=Complete;execute=mv,-u,$d.get_base_path=,$d.get_custom2="

Now when I try to move one of the downloads I get:

# rtmv Some\ Dir ../Music.Final/
INFO     Moving to "../Music.Final/Some Dir"...
INFO     Total time: 0.124 seconds.
Traceback (most recent call last):
  File "/home/media/bin/rtmv", line 8, in <module>
    load_entry_point('pyrocore==0.4.3dev-r2092', 'console_scripts', 'rtmv')()
  File "/home/media/lib/pyroscope/pyrocore/src/pyrocore/scripts/rtmv.py", line 231, in run
    RtorrentMove().run()
  File "/home/media/lib/pyroscope/pyrocore/src/pyrocore/scripts/base.py", line 234, in run
    self.mainloop()
  File "/home/media/lib/pyroscope/pyrocore/src/pyrocore/scripts/rtmv.py", line 213, in mainloop
    assert src1 == src2, 'Item path %r should match %r!' % (src1, src2)
AssertionError: Item path u'/export/Incoming/rTorrent/Some Dir' should match 
u'/export/Incoming/Complete/Music/Some Dir'!

Same result for Torrents I moved with rutorrent.  I'm going to remove the 
assert from rtmv.py and see were it takes me.

Original issue reported on code.google.com by pschne...@gmail.com on 23 Apr 2013 at 6:15

GoogleCodeExporter commented 8 years ago
Removing the assert from rtmv.py fixed it for me.

Original comment by pschne...@gmail.com on 23 Apr 2013 at 6:18

GoogleCodeExporter commented 8 years ago
See https://github.com/pyroscope/pyroscope/issues

Original comment by pyroscope.project on 14 Mar 2015 at 6:57