Custom Query (2449 matches)

From an email:

You miss a "Replaces: libtorrent-rasterbar7" in the control file for building libtorrent-rasterbar8 in Trusty 14.04

In fact up till now the package for all versions of Ubuntu was libtorrent-rasterbar7. The new package libtorrent-rasterbar8 replaces the old 7 in Wily 15.10.

Failing this Replaces: statement your build won't install on any regular version except Wily 15.10.

I am getting closer to figuring this out, see below error report:

[ERROR   ] 19:51:40 core:323 Disabling 'Z:\abcd\Watch\abcd', error during update: [Failure instance: Traceback: <type 'exceptions.WindowsError'>: [Error 32] The process cannot access the file because it is being used by another process: u'Z:\\abcd\\Watch\\abcd\\abcd.torrent'
twisted/internet/base.py:1192:run
twisted/internet/base.py:1201:mainLoop
twisted/internet/base.py:824:runUntilCurrent
twisted/internet/task.py:218:__call__
--- <exception caught here> ---
twisted/internet/defer.py:139:maybeDeferred
c:\program files\deluge\deluge-1.3.11-py2.6.egg\deluge\plugins\autoadd-1.04-py2.6.egg\autoadd\core.py:318:update_watchdir

The above happens when I cut and paste a *.torrent file into any watched folder.

The file does import into Deluge but then the watch folder in question unchecks itself, so any future *.torrent files placed in the directory just sit there, until I forcefully check the relevant box again. If multiple files have built up in the directory, they all import without a hitch. This happens at least when I have the "Delete .torrent after adding" option checked.

It almost seems that Deluge is trying to delete the file before it has finished copying to the watch folder, or at least before Windows "unlocks" the file for other processes to modify.

Any ideas on what is happening?

N.B. - I am trying the "Append extension after adding" function to see if it fixes the issue. I assume I will get the same result though, as if the file is being used by another process and can't delete it then Deluge won't be able to rename it either. UPDATE: Yes, same issue as I suspected.

I'd like to suggest a plugin that allows Deluge to be limited to using particular Network adapter, in this case a VPN. This would operate like a kill switch, so that traffic would only travel across the VPN, and if this would be VPN would go offline, or stop, then so to would the traffic until the VPN was re-established. The Network Adapter could be defined by MAC address quite easily. Thanks!