Transmission

Thanks, also see: https://trac.transmissionbt.com/ticket/4722

Thanks, I found the other location indeed.

I also downloaded the 2.42 package from experimental and was browsing through to see whether I could construct a 2.42 that can be installed on squeeze without updating 73 other packages to versions possibly not from squeeze.

Hmmm trackers still report me as 2.33, so somehow the 2.42+ is not running.
Maybe the service transmission-daemon is a different executable from the one I built and installed with make.

backed up some files and went for make install.
Looks to be working! transmission-daemon -V reports 2.42+
Thanks!

Thanks. When I do that I am still getting an error:


config.status: error: po/Makefile.in.in was not created by intltoolize


I can try the source tarball, but I'd rather build from trunk. Makes updating much easier.

yes i see the same config error, but in my case it is not fatal and i'm able ...

Result when building source tar ball (2.42):


tr-utp.c:65: error: conflicting types for âUTP_Writeâ
../third-party/libutp/utp.h:114: note: previous declaration of âUTP_Writeâ was here
make[1]: *** [tr-utp.o] Error 1
make[1]: Leaving directory `/root/.transmission/transmission-2.42/libtransmission ...

Thanks. When I do that I am still getting an error:
I can try the source tarball, but I'd rather build from trunk. Makes updating much easier.

Hello,

I am trying to build the trunk on debian squeeze.

I installed a couple of packages (curl, libevent, ...), but am getting an error I can't explain:


...
config.status: creating gtk/icons/Makefile
config.status: creating web/Makefile
config.status: creating web/images/Makefile
config.status ...

it turned out that other people were having some similar issues with the same tracker as well.
In the end I decided to restart transmission-daemon and after that everything was ok.

Hello,

Currently all my torrents from one tracker are reporting an error:

"Peer not found <hash>. Restart torrent."

For all torrents, the hash is the same.

I see this error using Remote Transmission (the desktop gui on win7 x64).

I wanted to get some information using the command line on my NAS ...

Hello,

I am running Transmission 2.32 on Debian Squeeze amd64.

Sometimes after rebooting I can't connect to the daemon from a remote client (Transmission Remote on Windows).
Also the web interface is unreacheable at port 9091.

Other times it works fine.

Looking through /var/log/syslog I notice ...

yes in settings.json you can disable UPnP (automatic port forwarding) :


"port-forwarding-enabled": false,


I already had that one disabled, I remember something like that. Maybe I disabled it earlier.

I uninstalled the minissdp package, and transmission is still running fine.

Thanks.

Hello,

I am running Debian squeeze and just upgrade my Transmission to the one from expiremental (2.32).

I noticed that a new deamon is installed, minissdpd. Something with UPnP.

Since I don't want anything todo with UPnP, I'd like to get rid of it.

Can I just uninstall minissdp(d)? Or at least ...

Well, then why does transmission rename the files after adding them?

And with my previous install (older, I believe 1.97) I had a cronjob that restarted transmission every night and never saw any torrents being reloaded.

Most pragmatic for now is to see whether the suggested


"trash-original ...

How to prevent this?
Use the daemon option to delete added files:
$ transmission-remote -si
VERSION
Daemon version: 2.32 (12526)
...
MISC
Autostart added torrents: Yes
Delete automatically added torrents: Yes <------------------

$ transmission-remote -h | grep -i delete
...
--trash-torrent ...