Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Transmission DSM7 support #4719

Merged
merged 26 commits into from
Aug 31, 2021
Merged

Transmission DSM7 support #4719

merged 26 commits into from
Aug 31, 2021

Conversation

publicarray
Copy link
Member

@publicarray publicarray commented Jul 8, 2021

Motivation: share worker supported since 6.0-5914
Linked issues: #4562 closes #4313

Checklist

  • Build rule all-supported completed successfully
  • Package upgrade completed successfully (dsm 6 & 7 individually) some users report a leftover firewall rule Can‘t start transmission on DSM7.0 #4313
  • New installation of package completed successfully (dsm6 & 7)

@publicarray publicarray changed the title Transmission DSM7 support Transmission DSM7 support [WIP] Jul 8, 2021
@publicarray publicarray changed the title Transmission DSM7 support [WIP] Transmission DSM7 support Jul 8, 2021
@mreid-tt
Copy link
Contributor

mreid-tt commented Aug 7, 2021

great to see the work to bring this package to DSM7. looking forward to its release

@publicarray
Copy link
Member Author

publicarray commented Aug 17, 2021

@hgy59 I've added the ability to have DSM version specific wizard files. (still needs French translation)
@BenjV already tested new installation procedure of the DSM7 package.

@Selenuix
Copy link

@hgy59 I've added the ability to have DSM version specific wizard files. (still needs French translation)
@BenjV already tested new installation procedure of the DSM7 package.

Are the translations still needed? Do you accept PRs? I got no real way to test but I could always try to help.

@publicarray
Copy link
Member Author

Bonjour @Selenuix, PRs are always welcome. The Wizards are in a JSON format you can see the old translation I removed here fb8640d and the new ones can be found here https://github.com/SynoCommunity/spksrc/pull/4719/files#diff-10ef7b0d6d3b7deeb475da37e2b322ab6bdbaa8807b1146be0a9e531351fedf9

You can copy the contents into a new file appending the _fre to the file name. Mostly only the description needs translation. Any help is appreciated.

publicarray and others added 14 commits August 28, 2021 13:21
set using SERVICE_WIZARD_SHARE

only disadvantage is that this does not support sub-folders currently

[Transmission] fix empty volume, consistency with naming
* Remove busybox dep

* transmission: remove unnecessary GROUP setting from service-setup.sh

* transmission: set GROUP for backwards compatibility

* Undo SPK_REV/CHANGELOG

* Adjust wizard text

* Remove now superfluous busybox configs
useful when using `synopkg install`
Comment on lines 2 to 4
# This gives tranmission the power to execute python scripts on completion (like TorrentToMedia).
PYTHON_DIR="/usr/local/python"
PATH="${SYNOPKG_PKGDEST}/bin:${PYTHON_DIR}/bin:${PATH}"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As there is no SPK_DEPENDS=python... in this package, it is not defined which python should be used.

For synocommunity packages the path /usr/local/{package} must not be used anymore, i.e. it must be defined as /var/packages/{package}/target.

I suppose that python2 should not be used anymore, so the package must be python3 or python38.

Proposal:
remove these lines and rely on python that is already installed and available in the path.

if no python is found in path, a lookup for synocommunity python3 and python38 could be used here to add it to the path for transmission.

Copy link
Member Author

@publicarray publicarray Aug 28, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks. Good catch! I didn't even notice that python can be used from transmission.

Copy link

@BenjV BenjV Aug 28, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As of DSM 7, Python 3 is standard available and can be found via the path.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if no python is found in path, a lookup for synocommunity python3 and python38 could be used here to add it to the path for transmission.

@hgy59 I didn't do any fancy detection because that is what $PATH is for anyway. Don't need to do it twice and this way it still works if a python package is added or removed. Agreed, for DSM7 the build in Python should be good enough.

@publicarray publicarray merged commit f5fc4a3 into master Aug 31, 2021
@publicarray publicarray added status/published Published and activated (may take up to 48h until visible in DSM package manager) and removed status/ready-to-merge labels Aug 31, 2021
@publicarray publicarray deleted the transmission7.0 branch August 31, 2021 02:36
@hgy59
Copy link
Contributor

hgy59 commented Aug 31, 2021

Can we now use spk/transmission as a template for wizard files with shared folders compatible with DSM 7?
This would help to finalize #4683, #4627 and all the download related packages like #4743 and others.

@Zigwan06
Copy link

thank you for your work

@BenjV
Copy link

BenjV commented Aug 31, 2021

@hgy59 , @publicarray
I would suggest to use it for all packages, but at least not only for packages that create shared folders but also the ones who must read them.
Like Sonarr, Radarr and Sick(beard/chill) that reads files from the shares created by Nzbget and/or Transmission.
Their user should also be member of the syncommunity group.

So I would suggest to make all packages use the syncommunity group and not sc-packagename to keep things simple.

@spyrodragon1
Copy link

Thanks for the work on this one. Just curious when the transmission update package actually be released via the synology apps section ? Thanks again.

@publicarray
Copy link
Member Author

publicarray commented Sep 1, 2021

@hgy59 Yes we can. #4748 is interesting because I want to know what happens when multiple packages use the same shared folder. For DSM6 It also uses the old behaviour of creating shared folders. So existing DSM6 packages should continue to work. (sorry about the reverts I'm a bit indecisive)

@BenjV

shared folders but also the ones who must read them.

I'm not sure on that. Everyone has a different way to organise their media. e.g. filebot for instance. Setting up the permissions for the packages that you use is easy enough already. I prefer users to be educated rather than forcing a specific way of doing things. IMHO we should be phasing out wizards not add more.

all packages use the syncommunity group

You already convinced me see #4789

@spyrodragon1 tops 48h for the CDN to catch up

@mreid-tt
Copy link
Contributor

mreid-tt commented Sep 1, 2021

was able to repair my transmission package successfully with this and it even retained all my previous torrents. great work folks!

@gemmmo
Copy link

gemmmo commented Sep 1, 2021

Just updated DS218 (rtd1296) to DSM7. Repair didn't work in Package Manager but manual install of the package from the synocommunity website completed without errors and everything works fine. Thank you!

@isr25
Copy link

isr25 commented Sep 1, 2021

Thank you for your hard work!

@gemmmo
Copy link

gemmmo commented Sep 1, 2021

Not sure if this is the right place to ask, after installing transmission on DSM7 it shows up in Package Center and works when launched using the URL but there is no app shortcut in the main menu. Is there a way to fix this? For example if I uninstall Transmission and reinstall transmission will my torrent data be automatically restored? Thank you.

@BenjV
Copy link

BenjV commented Sep 1, 2021

Yes if you uninstall Transmission and do not remove the data you can install Transmission again and all torrents will be restored.

@gemmmo
Copy link

gemmmo commented Sep 1, 2021

Yes if you uninstall Transmission and do not remove the data you can install Transmission again and all torrents will be restored.

Thanks for the help! Reinstalled smoothly but the Transmission logo still doesn't show up in the Main Menu. I'll leave it since it works fine launching from URL and the migration was perfect from DSM7.

@BenjV
Copy link

BenjV commented Sep 1, 2021

I have experienced that with more packages(also on DSM 6) and sometimes it just re-appears again and sometimes not.
Has noting to do with this package, maybe a reboot of your Nas will help.

@gemmmo
Copy link

gemmmo commented Sep 1, 2021

So far rebooting hasn't worked yet but I will see how it goes. Transmission is working great regardless, thank you for the help!

@spyrodragon1
Copy link

Apologies for the stupid question but do i need to update to v7 of the synology software to see the transmission update or should i see it while I'm on v6 ? The update hasn't appeared in the package center yet on my NAS and I'm just wondering if the update just hasn't appeared yet ( and I should be more patient ) or it hasn't appeared because it won't appear until i upgrade to v7. Hope that makes some semblance of sense. Thanks

@BenjV
Copy link

BenjV commented Sep 2, 2021

Version 3.00-19 is available for both DSM 6 as well as DSM 7 as of yesterday
What architecture is your Nas?

You can always download it and do a manual install.
Download can be found here.
https://synocommunity.com/package/transmission

@spyrodragon1
Copy link

spyrodragon1 commented Sep 2, 2021

@BenjV - It's a DS220+ (INTEL Celeron J4025) currently running DSM 6.2.4-25556. Happy to download it manually but not sure what package I would take from that list.....thanks

@BenjV
Copy link

BenjV commented Sep 2, 2021

You need the geminilake version for a DS220+
zie:
https://github.com/SynoCommunity/spksrc/wiki/Architecture-per-Synology-model

@spyrodragon1
Copy link

@BenjV - Sorry again for the stupid question but it says transmission 3.00-19 was the 1st November 2020 release on that page ?

Update openssl to 1.1.
Date
2020-11-01 17:01:28.615450

Apologies again if I'm missing something.....

@BenjV
Copy link

BenjV commented Sep 2, 2021

Most likely a mistake in a year field.
This version is currently the latest build.

@vjayer
Copy link

vjayer commented Aug 7, 2023

You need the geminilake version for a DS220+ zie: https://github.com/SynoCommunity/spksrc/wiki/Architecture-per-Synology-model
@spyrodragon1
sorry for the necroposting reply but just wanted to place this in case others have the same question.
Gemini Lake is the Intel codename for the family that includes the Celeron J4025
https://ark.intel.com/content/www/us/en/ark/products/197307/intel-celeron-processor-j4025-4m-cache-up-to-2-90-ghz.html
so your DS220+ should be supported

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status/published Published and activated (may take up to 48h until visible in DSM package manager)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Can‘t start transmission on DSM7.0