Welcome!
Important information
-- Spectre and Meltdown vulnerabilities
-- Change in MX sources

News
-- MX Linux on social media: here
-- Mepis support still here

Current releases
-- MX-17.1 Final release info here
-- antiX-17 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

MEPIS 12 Community Repository: The Transmission Thread

News about updates on package status for CR packages compiled for MEPIS 12.0
Post Reply
Message
Author
User avatar
Stevo
Forum Veteran
Forum Veteran
Posts: 16568
Joined: Fri Dec 15, 2006 8:07 pm

MEPIS 12 Community Repository: The Transmission Thread

#1 Post by Stevo » Mon Dec 22, 2014 6:10 pm

Bittorrent application Transmission, version 2.84, is now in the testing CR.

Changelog is here: https://trac.transmissionbt.com/wiki/Ch ... rsion-2.84

Please let us know how it installs and performs is you try it, Thanksl

User avatar
Stevo
Forum Veteran
Forum Veteran
Posts: 16568
Joined: Fri Dec 15, 2006 8:07 pm

Re: MEPIS 12 Community Repository: The Transmission Thread

#2 Post by Stevo » Tue Dec 23, 2014 5:19 pm

I also disabled systemd for the transmission daemon, but don't know if this broke it or not. I think it's more for torrent servers. I did test the GTK front end and downloaded an ISO quite nicely, but that did not use the daemon.

User avatar
eugen-b
Forum Regular
Forum Regular
Posts: 572
Joined: Tue Aug 25, 2015 1:56 pm

Re: MEPIS 12 Community Repository: The Transmission Thread

#3 Post by eugen-b » Sun Dec 06, 2015 7:41 pm

I've been playing with my Transmission-gtk clients recently but then I got the idea that I could to test if the CLI version would run. I installed (on my new livarp install) transmission-cli, transmission-daemon an transmission-remote-cli (which is supposed to be the Ncurses UI). transmission-cli seems to be for downloading only, the daemon can run like the gtk client for seeding (at least I suppose it does, because I see some upload on my conky). The daemon creates a folder ~/.config/transmission-daemon which is very similar to the ~/.config/transmission folder, so I symlinked the three subfolders to the common config on my data btrfs subvolume.

But the transmission-remote-cli refuses to run:

Code: Select all

transmission-remote-cli                      < localhost:pts/0:~
Unsupported Transmission version: 2.84 (14307) -- RPC protocol version: 15
Please install Transmission version 2.52 or lower.
@Stevo, is it possible to get a newer version of transmission-remote-cli ?
https://packages.debian.org/jessie/transmission-cli
Or can I simply install the Jessie version?
MX-14 on a Via Eden 1GHz CPU thin client, 3GB RAM, Via VX800 chipset, Via Chrome9 HC GPU, 32GB M.2 SSD;
btrfs with @ and @home subvolumes for MX-14;
added @antiX and @antiXhome subvolumes and copied antix 13.1 base into them, adjusting Grub from MX-14.

User avatar
Stevo
Forum Veteran
Forum Veteran
Posts: 16568
Joined: Fri Dec 15, 2006 8:07 pm

Re: MEPIS 12 Community Repository: The Transmission Thread

#4 Post by Stevo » Sun Dec 06, 2015 8:41 pm

Those appear to be separately sourced than transmission, so I'll see if those can be backported.

Installing a Jessie package on a Wheezy base often turns into a pile of problems; let's try a backport first.

The gtk version appears to be the same in Jessie.
The optimist proclaims that we live in the best of all possible worlds, and the pessimist fears this is true.

James Branch Cabell

User avatar
eugen-b
Forum Regular
Forum Regular
Posts: 572
Joined: Tue Aug 25, 2015 1:56 pm

Re: MEPIS 12 Community Repository: The Transmission Thread

#5 Post by eugen-b » Sun Dec 06, 2015 8:55 pm

Stevo wrote:Those appear to be separately sourced than transmission, so I'll see if those can be backported.

Installing a Jessie package on a Wheezy base often turns into a pile of problems; let's try a backport first.

The gtk version appears to be the same in Jessie.
Thanks in advance! It would complete the transmission ecosystem. Especially users of old hardware would profit from a CLI torrent client, IMO.
When I'm testing such things like installing Jessie packages I always create a snapshot before, no worries!
MX-14 on a Via Eden 1GHz CPU thin client, 3GB RAM, Via VX800 chipset, Via Chrome9 HC GPU, 32GB M.2 SSD;
btrfs with @ and @home subvolumes for MX-14;
added @antiX and @antiXhome subvolumes and copied antix 13.1 base into them, adjusting Grub from MX-14.

User avatar
Stevo
Forum Veteran
Forum Veteran
Posts: 16568
Joined: Fri Dec 15, 2006 8:07 pm

Re: MEPIS 12 Community Repository: The Transmission Thread

#6 Post by Stevo » Sun Dec 06, 2015 10:41 pm

How does the backported deb in here work?

https://copy.com/qyNBGs6ElEsgR2Ol

User avatar
eugen-b
Forum Regular
Forum Regular
Posts: 572
Joined: Tue Aug 25, 2015 1:56 pm

Re: MEPIS 12 Community Repository: The Transmission Thread

#7 Post by eugen-b » Mon Dec 07, 2015 4:39 am

I was able to install the .deb file, but need more time to learn how to set it up so I can test its function. Thanks!
MX-14 on a Via Eden 1GHz CPU thin client, 3GB RAM, Via VX800 chipset, Via Chrome9 HC GPU, 32GB M.2 SSD;
btrfs with @ and @home subvolumes for MX-14;
added @antiX and @antiXhome subvolumes and copied antix 13.1 base into them, adjusting Grub from MX-14.

User avatar
eugen-b
Forum Regular
Forum Regular
Posts: 572
Joined: Tue Aug 25, 2015 1:56 pm

Re: MEPIS 12 Community Repository: The Transmission Thread

#8 Post by eugen-b » Mon Dec 07, 2015 5:18 am

To be able to start the Curses GUI it needs to create a confing first by running

Code: Select all

transmission-remote-cli --create-config
Then the transmission-daemon must be running.

Code: Select all

transmission-daemon
Then you launch theCurses UI

Code: Select all

transmission-remote-cli
and it looks like this then:
transmission-remote-cli.png
There are some more things to keep in mind, but I didn't understand them yet.
You do not have the required permissions to view the files attached to this post.
MX-14 on a Via Eden 1GHz CPU thin client, 3GB RAM, Via VX800 chipset, Via Chrome9 HC GPU, 32GB M.2 SSD;
btrfs with @ and @home subvolumes for MX-14;
added @antiX and @antiXhome subvolumes and copied antix 13.1 base into them, adjusting Grub from MX-14.

User avatar
eugen-b
Forum Regular
Forum Regular
Posts: 572
Joined: Tue Aug 25, 2015 1:56 pm

Re: MEPIS 12 Community Repository: The Transmission Thread

#9 Post by eugen-b » Mon Dec 07, 2015 10:37 am

Now I cannot start transmission-remote-cli anymore (using mate-terminal, therefore the strange output format)

Code: Select all

15:36 eugen > transmission-remote-cli                      < localhost:pts/0:~
401: Unauthorized
Unauthorized User
Update: Restarting the daemon made the start possible.
MX-14 on a Via Eden 1GHz CPU thin client, 3GB RAM, Via VX800 chipset, Via Chrome9 HC GPU, 32GB M.2 SSD;
btrfs with @ and @home subvolumes for MX-14;
added @antiX and @antiXhome subvolumes and copied antix 13.1 base into them, adjusting Grub from MX-14.

User avatar
eugen-b
Forum Regular
Forum Regular
Posts: 572
Joined: Tue Aug 25, 2015 1:56 pm

Re: MEPIS 12 Community Repository: The Transmission Thread

#10 Post by eugen-b » Wed Dec 09, 2015 6:03 am

It doesn't work again

Code: Select all

10:50 eugen > transmission-remote-cli                      < localhost:pts/0:~
Cannot connect to localhost:9091: Die Wartezeit für die Verbindung ist abgelaufen
Means "waiting time for the connction has expired".
Killing trnasmission-daemon doen't make any difference.
It looks like running a bittorrent client with default settings is a bit too naive. Need to learn more about this matter.
MX-14 on a Via Eden 1GHz CPU thin client, 3GB RAM, Via VX800 chipset, Via Chrome9 HC GPU, 32GB M.2 SSD;
btrfs with @ and @home subvolumes for MX-14;
added @antiX and @antiXhome subvolumes and copied antix 13.1 base into them, adjusting Grub from MX-14.

Post Reply

Return to “Package Status - 12.0 Beta”