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

rutorrent: fix volume customization in installation procedure and package dependencies #5669

Conversation

smaarn
Copy link
Contributor

@smaarn smaarn commented Mar 18, 2023

Description

This is fixing basically installation related concerns:

  • When customizing the volume an invalid value was defined for the full path of the download location
  • There were left over files from the previous PHP integration (5.6)
  • Apache 2.4 dependency wasn't explicitely declared
  • Watch dir configuration wasn't appropriately supported

Should fix #5668

Checklist

  • Build rule all-supported completed successfully
  • New installation of package completed successfully
  • Package upgrade completed successfully (Manually install the package again)
  • Package functionality was tested

Type of change

  • Bug fix

@smaarn smaarn requested a review from mreid-tt March 18, 2023 13:08
@smaarn smaarn marked this pull request as ready for review March 18, 2023 13:08
@mreid-tt
Copy link
Contributor

I tried doing a clean install in DSM 6 and setting a watch directory but got an error:

Screenshot 2023-03-18 at 11 39 25 AM

Screenshot 2023-03-18 at 11 40 25 AM

I don't know if this is a new error or something from before. Below are some of the logs:

/var/log/packages/rutorrent.log

2023/03/18 11:34:18	install rutorrent 3.10-14 Begin preinst
2023/03/18 11:34:18	Begin load_variables_from_file
2023/03/18 11:34:18	End load_variables_from_file
2023/03/18 11:34:18	Begin initialize_variables
2023/03/18 11:34:18	End initialize_variables
2023/03/18 11:34:18	===> Step preinst. STATUS=INSTALL USER=rutorrent GROUP=sc-download SHARE_PATH=/volume1/downloads
2023/03/18 11:34:18	Begin validate_preinst
2023/03/18 11:34:18	install rutorrent 3.10-14 End preinst ret=[1]
2023/03/18 11:34:18	install rutorrent 3.10-14 Begin /bin/rm -rf /volume1/@tmp/pkginstall
2023/03/18 11:34:18	install rutorrent 3.10-14 End /bin/rm -rf /volume1/@tmp/pkginstall ret=[0]

/var/log/synopkg.log

2023/03/18 11:34:18	install rutorrent 3.10-14 Begin preinst
2023/03/18 11:34:18	install rutorrent 3.10-14 End preinst ret=[1]
2023/03/18 11:34:18	install rutorrent 3.10-14 Begin /bin/rm -rf /volume1/@tmp/pkginstall
2023/03/18 11:34:18	install rutorrent 3.10-14 End /bin/rm -rf /volume1/@tmp/pkginstall ret=[0]
2023/03/18 11:34:18	install rutorrent 3.10-14 failed

@smaarn
Copy link
Contributor Author

smaarn commented Mar 18, 2023

I tried doing a clean install in DSM 6 and setting a watch directory but got an error:

Screenshot 2023-03-18 at 11 39 25 AM Screenshot 2023-03-18 at 11 40 25 AM

I don't know if this is a new error or something from before. Below are some of the logs:

/var/log/packages/rutorrent.log

2023/03/18 11:34:18	install rutorrent 3.10-14 Begin preinst
2023/03/18 11:34:18	Begin load_variables_from_file
2023/03/18 11:34:18	End load_variables_from_file
2023/03/18 11:34:18	Begin initialize_variables
2023/03/18 11:34:18	End initialize_variables
2023/03/18 11:34:18	===> Step preinst. STATUS=INSTALL USER=rutorrent GROUP=sc-download SHARE_PATH=/volume1/downloads
2023/03/18 11:34:18	Begin validate_preinst
2023/03/18 11:34:18	install rutorrent 3.10-14 End preinst ret=[1]
2023/03/18 11:34:18	install rutorrent 3.10-14 Begin /bin/rm -rf /volume1/@tmp/pkginstall
2023/03/18 11:34:18	install rutorrent 3.10-14 End /bin/rm -rf /volume1/@tmp/pkginstall ret=[0]

/var/log/synopkg.log

2023/03/18 11:34:18	install rutorrent 3.10-14 Begin preinst
2023/03/18 11:34:18	install rutorrent 3.10-14 End preinst ret=[1]
2023/03/18 11:34:18	install rutorrent 3.10-14 Begin /bin/rm -rf /volume1/@tmp/pkginstall
2023/03/18 11:34:18	install rutorrent 3.10-14 End /bin/rm -rf /volume1/@tmp/pkginstall ret=[0]
2023/03/18 11:34:18	install rutorrent 3.10-14 failed

@mreid-tt it's actually something which dates back from the previous versions which had gone through the cracks. Will push a fix in this MR in the coming minutes hours. Thanks for spotting.

EDIT: Updated the ETA (sorry but I realized that I needed to reset my dev environment)

@smaarn smaarn marked this pull request as draft March 18, 2023 16:07
@smaarn
Copy link
Contributor Author

smaarn commented Mar 18, 2023

Converting to draft until I confirm that I've fixed the watch directory issue reported above.

@smaarn smaarn marked this pull request as ready for review March 18, 2023 17:25
@smaarn smaarn marked this pull request as draft March 18, 2023 17:34
@smaarn
Copy link
Contributor Author

smaarn commented Mar 18, 2023

Flagged as draft as I spotted another bug with the watch directory (not actually configured appropriately)

@mreid-tt
Copy link
Contributor

I've done a reinstall and the watch folder gets created. I added a torrent into it however but nothing downloaded. I looked at the settings and saw this:
Screenshot 2023-03-18 at 1 33 00 PM

I don't know if this is correct and I changed it to this:
Screenshot 2023-03-18 at 1 35 55 PM

The torrent in the folder however still has not downloaded so perhaps I'm not understanding the app's configs.

@mreid-tt
Copy link
Contributor

Okay, it looks like we thought of the same thing... As an update the torrent in the watch folder eventually downloaded on its own so there was some delay but it should be good now.

@mreid-tt
Copy link
Contributor

mreid-tt commented Mar 18, 2023

Regarding my other #5617 (comment), where we discussed:

In the resource file, the webservice section can be expanded to include the specific service type. For example it currently has "backend": 8 which means "PHP7.4" but doesn't specify the front end as in apache_php or nginx_php

Hey @mreid-tt

  • I believe we do specify the type of the backend so I'm not sure what you meant by " doesn't specify the front end as in apache_php or nginx_php".

What I was trying to share was the recommended configuration for the Web Service in the DSM 7 developer guide. In it the following common keys are mandatory: service, display_name, type and php. Within the php profile, these keys are mandatory: profile_name, profile_desc, backend, user and group.

When I initially looked at your resource file I missed that the type was already present and set to "apache_php" so that was my mistake. All in all things are looking good to me.

spk/rutorrent/Makefile Outdated Show resolved Hide resolved
@mreid-tt
Copy link
Contributor

@smaarn, I can confirm that the last patch fixed the watch folder and torrent files added to it are automatically downloaded.

@smaarn smaarn marked this pull request as ready for review March 18, 2023 18:58
@smaarn smaarn requested a review from mreid-tt March 18, 2023 18:59
@smaarn smaarn merged commit ebab920 into SynoCommunity:master Mar 24, 2023
@hgy59 hgy59 added status/published Published and activated (may take up to 48h until visible in DSM package manager) and removed status/to-publish labels Mar 31, 2023
@voytec13
Copy link

voytec13 commented May 9, 2023

Are there any plans to support nginx as a backend or Apache will remain as hard dependency for rutorrent installation?

@smaarn smaarn deleted the rutorrent/fix/fix-installation-procedure-and-cleanup-resources branch May 17, 2023 19:43
@mreid-tt
Copy link
Contributor

Are there any plans to support nginx as a backend or Apache will remain as hard dependency for rutorrent installation?

As has been stated before in this #5617 (comment), there are no explicit plans for this. As you have asked this before, I would suggest you open a new issue specifically requesting that the backend support nginx. That way it can be tracked and responded to formally.

@smaarn, based on your previous comment there would likely have to be a hard switch from Apache to nginx as the package dependencies cannot allow for an either/or scenario. This document may assist with possible testing configurations: NGINX PHP FPM RTORRENT

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.

ruTorrent 3.10 fails to start after first time install on DSM 7
4 participants