Search Criteria
Package Details: pyload 0.4.9-17
| Package Base: | pyload |
|---|---|
| Description: | Downloadtool for One-Click-Hoster written in python. |
| Upstream URL: | http://www.pyload.org |
| Category: | network |
| Licenses: | GPL |
| Conflicts: | pyload-git, pyload-hg |
| Replaces: | pyload-git, pyload-hg |
| Submitter: | None |
| Maintainer: | dobo |
| Last Packager: | dobo |
| Votes: | 96 |
| First Submitted: | 2010-02-10 00:59 |
| Last Updated: | 2015-03-08 21:24 |
Latest Comments
Comment by dobo
2015-03-08 21:25
Ok, I've changed pyload.service but it's minor change so I haven't bumped package version. Sorry for waiting so long I've missed e-mail notification.
Comment by hawk07
2015-02-14 10:57
+1 for killermoehre
Comment by killermoehre
2014-06-18 16:55
Please, for the sake of systemd, use this service file
### FILE /usr/lib/systemd/system/pyload.service ###
[Unit]
Description=pyLoad Core
After=network.target
[Service]
ExecStart=/usr/bin/pyLoadCore
User=pyload
Group=pyload
[Install]
WantedBy=multi-user.target
### END ###
Comment by dobo
2014-06-12 16:50
I adopted this package. I forced pyload to use internal libraries bundled in its archive. That's why I removed python2-jinja and python2-beaker dependencies. I also included functionality to PKGBUILD which builds Python optimized byte-code files (*.pyo). Hope it works all fine!
Comment by HLFH
2014-04-10 17:02
Does not work. Because of jinja2 ? Please update
Comment by darude
2014-02-26 12:35
@Rusk: How did you do the downgrade für jinja2.6 since I'm having the same problem. :(
Comment by Rusk
2014-02-02 11:55
You will be unable to login to pyload's webinterface with jinja2.7. Only after using jinja2.6 I was able to login. Until then you'll be simply receiving error messages saying that your provided username and password didnt match.
Comment by willemw
2014-01-21 09:02
By following the wiki page, I ended up with two config dirs: /var/run/pyload/ and /var/run/pyload/.pyload/ (if I remember correctly), 'losing' my initial configuration settings. Let pyload determine the location of the config directory by removing the --configdir option.
PIDFile=/var/lib/pyload/.pyload/pyload.pid
This is just the default location. If /var/run/... is preferred, then maybe use that. Also note that the wiki page does not mention PIDFILE at all.
Downloading from a third source seems unnecessary (links may not always be available, firewall issues, etc.).
Comment by onny
2014-01-20 16:50
willemw: What do you mean with that? Shouldn't we put the pid-file into a /run-directory, e.g.: /var/run/pyload/?
Why remove --configdir from ExecStart?
And why not download *.desktop-files seperately?
Comment by willemw
2013-12-17 07:31
The paths used in file pyload.service are not standard/default paths. Please use default paths:
ExecStart=/usr/bin/pyLoadCore --daemon
PIDFile=/var/lib/pyload/.pyload/pyload.pid
The wiki also assumes default paths.
Why are the *.desktop files, etc downloaded separately?