-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
rutorrent: Update v4.3.7 to v5.1.12 and migrate to Python 3.12 #6404
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
Conversation
* Bump PHP requirement to 8.2
|
@smaarn I already have a local update to rutorrent 4.3.9 including updates for
and work on spk/rutorrent in progress to:
If you don't mind I could add the updated dependencies soon and help with the spk definitions later... |
@hgy59 by all means, do ! This PR was just to kick off the upgrade work in a "minimal" effort mode (e.g. have the build passing, play with things to see if there needs to be more advanced config changes...). |
- update cross/libtorrent-rakshasa from v0.13.8 to v0.14.0 (drop specific commit by hash) - update cross/rtorrent from v0.9.8 to v0.10.0 (drop specific commit by hash) - update cross/xmlrpc-c from v1.51.06 to v1.59.03 - spk/rutorrent: - drop rutorrent.sc (same as default, generated by spksrc.spk.mk) - adjust changelog
- add cross/screen5 (requires DSM 7, i.e. std c17)
… rutorrent/upgrade-5.1
|
@smaarn dependencies updated (and master merged into this) Thanks to #6255 the github prepare action takes now less than one minute including the source download. For spk/rutorrent files, further investigation is required. @mreid-tt shall we try to update this package for DSM 7.1 with PHP 8.0 and DSM 7.2 with PHP 8.2? |
@hgy59, we can try both yes. I am a bit unsure why we are bumping the PHP version however since the release notes for ruTorrent don't seem to make any special mention of a minimum PHP 8 requirement. If this is in fact needed then a build for different versions of PHP will show errors when run with incompatible versions (similar to #6229). |
@mreid-tt actually I was under the impression that I couldn't install PHP 7.4 on my DSM (7.2). Turns out I was wrong. We can definitely avoid upgrading then. I'm not sure, though, about a "build" for different versions of PHP causing incompatibilities (it's only runtime dependencies from what I recall), right ? I will revert the PHP upgrade anyway since it would minimize the "risk" of this upgrade. |
|
Status: installation successful but get the following warnings at startup: |
Fix installation directory for dumptorrent and scrapec
Fix configuration of dump plugin
PR Review: simplify installation of dumptorrent and scrapec binaries
Fix PLIST
This reverts commit 80a7014.
|
Summary of situation:
@hgy59 do you recall what were the reasoning behind the version upgrades and why you picked those specific versions (and not others) ? |
cross/libtorrent-rakshasa
cross/rtorrent
cross/xmlrpc-c
what else? |
This reverts commit 9b347c4.
Will be having a crack at reverting the upgrade of libtorrent and rtorrent to the "unstable" version and see how it goes. It turns out that 0.9.8 is the latest "stable" version and the recommended one for rutorrent so we may not even have a choice, but let's try with the 0.10.0 version. |
|
@smaarn, I've completed the change to the plugin restore function. I've also bumped to rutorrent to 5.1.12. Finally, I've migrated the package to Python 3.12. Will see how the build completes and then do some testing. |
|
Install and update are successful on DSM 7: Install LogUpgrade LogService Log |
th0ma7
left a comment
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.
I initially had it set to the 5.2.x branch, but I noticed there are other packages that might also need updates. I can handle updating the download references and version numbers, but several of them include patch files and explicit PLIST files, which would be difficult for me to update without a development environment. I'm happy to take care of the basic version updates, but I’d need assistance with the more detailed components. |
This reverts commit 51c9783.
|
Gotcha, maybe then just updating the few trivial dependencies (if any) and leaving the rest for a subsequent PR? As this is already a big update on its own for the rutorrent package. |
I've done some testing with the latest versions and these are the findings:
As such, I've rolled these back and left everything else updated and am running some final tests. |
|
@smaarn, I believe we have a working version now following my testing. I'm still getting one error in the log: But this does not seem to affect the app functionality. All plugins (including ratio) are loaded and enabled. EDIT: Correction to my previous message. After performing a clean uninstall and reinstall, the error no longer appears. It’s possible that some cached data in my browser from earlier tests may have contributed to the issue. For now, the startup is running clean.
|
th0ma7
left a comment
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.
LGTM - nice work :)

Description
Checklist
all-supportedcompleted successfullyType of change
Status
dumpplugin (adddumptorrent)ratioplugin loading/tmp/errors.log)