-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Conversation
great to see the work to bring this package to DSM7. looking forward to its release |
7b42468
to
b2e61e3
Compare
@hgy59 I've added the ability to have DSM version specific wizard files. (still needs French translation) |
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 |
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`
folders for DSM7
# 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}" |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.
thank you for your work |
@hgy59 , @publicarray So I would suggest to make all packages use the syncommunity group and not sc-packagename to keep things simple. |
Thanks for the work on this one. Just curious when the transmission update package actually be released via the synology apps section ? Thanks again. |
@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)
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.
You already convinced me see #4789 @spyrodragon1 tops 48h for the CDN to catch up |
was able to repair my transmission package successfully with this and it even retained all my previous torrents. great work folks! |
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! |
Thank you for your hard work! |
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. |
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. |
I have experienced that with more packages(also on DSM 6) and sometimes it just re-appears again and sometimes not. |
So far rebooting hasn't worked yet but I will see how it goes. Transmission is working great regardless, thank you for the help! |
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 |
Version 3.00-19 is available for both DSM 6 as well as DSM 7 as of yesterday You can always download it and do a manual install. |
@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 |
You need the geminilake version for a DS220+ |
@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. Apologies again if I'm missing something..... |
Most likely a mistake in a year field. |
|
Motivation: share worker supported since 6.0-5914
Linked issues: #4562 closes #4313
Checklist
all-supported
completed successfully