Oh ok. So we need someone other who may do the necessary changes.
Is here a volunteer who could made this for us? ;)
- Daniel
Am Mittwoch, den 24.07.2013, 19:45 +0200 schrieb Thomas Ebert:
Hi Daniel,
sorry i don't think so.
Regards Thomas
Am 24.07.2013 15:14, schrieb Daniel Weismüller:
Hi Thomas do you think you're able to implement the new suggestions from Michael?
- Daniel
Am Donnerstag, den 04.07.2013, 12:51 +0200 schrieb Michael Tremer:
Hi Thomas,
two things about this:
a) The rootfile is (again) completely messed up. The build system will complain at the end that it could not compare it to what has been generated in the build.
b) The initscript does not seem very well done. Despite that some information has not been properly filled out in the header and in the lines that will be prompted on the terminal at boot up, the start and stop process of pyload does not look very good.
If there is no such daemon, then please write a helper daemon that can be properly killed.
-Michael
On Wed, 2013-07-03 at 15:30 +0200, Thomas Ebert wrote:
Hi Daniel,
i've updated the init.d script and changed the default download folder to /var/pyload/Downloads. I've deleted the old branch pyload in my reposistory and created a new one with the same name.
Regards Thomas
Am 2013-07-02 20:12, schrieb Thomas Ebert:
Hi Daniel,
i don't think that it's a big case to implement that things.
I'll add these suggestions and make a new upload to my repository.
Regards Thomas
Am 2013-07-02 14:57, schrieb Daniel Weismüller:
Thomas,
do you think you're able to implement the suggestions from Michael?
- Daniel
Am Montag, den 17.06.2013, 11:04 +0200 schrieb Daniel Weismüller: > Hi > > Are there some news about pyload? > What about the suggestions? Did someone try to implement them? > > - Daniel > > > Am Dienstag, den 04.06.2013, 17:07 +0200 schrieb Michael Tremer: >> Hi, >> >> yeah, I would also suggest that the data directories are moved to > some >> subdirectory of /var, because a full root device will kill the > firewall >> box eventually. >> >> I also checkout out the source and that looks pretty much okay. > Some >> files which don't necessarily need to be in the packages like all > the >> *.so links, but still. >> >> Please replace the initscript by something proper. You will find > a >> template at src/initscripts/init.d/template. Except that, things > look >> good. >> >> -Michael >> >> On Fri, 2013-05-31 at 09:14 +0800, Fajar Ramadhan wrote: >>> Hi there, >>> >>> I have same problem just like ummeegge - /srv is too small > (which is >>> only 2 Gb here) to properly hold all downloaded files. So I > change its >>> download directory to /var/pyload and everything just works > fine for >>> me. >>> >>> One thing to remember : after you change pyload configurations, > you >>> should do manual pyload restart from web interface Administrate > -> >>> Restart pyLoad. pyLoad configurations wont change if you do > restart >>> using init script. >>> >>> I've tested some plugins such as download scheduler and youtube > (I >>> love youtube plugin since its able to download HD videos >>> automagically) and its work like a charm. Now I have > transmission and >>> pyLoad running in my box, great! :) >>> >>> Regards, >>> >>> - Fajar R. >>> >>>> Subject: Re: pyload >>>> From: ummeegge@ipfire.org >>>> Date: Thu, 30 May 2013 17:52:19 +0200 >>>> To: development@lists.ipfire.org >>>> >>>> Hi Stefan, >>>> so for the first the compiled binary (unrar) can be found in > here >>> http://people.ipfire.org/~ummeegge/unrarsrc/ >>>> i have installed now pyload and all the dependencies and for > the >>> first it looks very good. I could access the pyload > webinterface with >>> http://<IP-IPFire>:8086 and all menues are available. The start > of >>> different downloads over the "Add" button gives me also the >>> possibility to create new folders in the Download section (have > tested >>> it now only with "Queue" not with "Collector", under the tab > "Home" >>> the overview of active downloads are displayed, also the > "Queue" tab >>> with his small function icons worked good for me. >>>> The Logs section works also good and give a nice informative >>> overview. >>>> The administration tabs (Logout, Administrate, Info) on the > right >>> top of the WUI do their work. >>>> I have had some problems by changing the config´s, the > default >>> download directory is located under /srv which wasn´t the best > place >>> for me cause mostly disc space is under /var or /mnt/harddisk > so i >>> tried to change it over the WUI but the changes doesn´t take > affect, >>> also the WUI seems to work buggy after this changes. I need to > make >>> a /etc/init.d/pyload stop/start (the init script from pyload > seems not >>> to work with restart) after this all went good again and the > new >>> download folder was accepted. So it seems like configuration > changes >>> needs to have an pyload restart, that the changes takes affect > ? >>>> I think there is no reconnect.sh script available or may i > have >>> overseen it... >>>> The first impression of pyload is good but some further tests > might >>> be important i think. >>>> Thanks for your good work and greetings >>>> >>>> >>>> Erik >>>> >>>> Am 30.05.2013 um 10:32 schrieb Erik K.: >>>> >>>>>> Hi Stefan and Daniel, >>>>>> @Stefan i think unrar is not available in Pakfire, but i > compile >>> it at this time. If the build process is finished, i upload it > to my >>> home directory. I will go then also for some tests. >>>>>> Feedback will come soon. >>>>>> >>>>>> Greetings >>>>>> >>>>>> >>>>>> Erik >>>>>> >>>>>> Am 29.05.2013 um 21:53 schrieb Stefan Schantl: >>>>>> >>>>>>> Hello Daniel, >>>>>>> >>>>>>> thanks for testing the packages, are they also affected > by the >>> "/etc/init.d/" bug ? >>>>>>> All mailing list followers, please join the team and test > the >>> pyload package and it's dependencies. >>>>>>> The installation of the packages is pretty easy: >>>>>>> >>>>>>> * Install sqlite, pycurl and unrar by using pakfire. > "pakfire >>> install sqlite pycurl unrar" or do it over the WUI. >>>>>>> * Download pyload and the dependecies from here: >>> http://people.ipfire.org/~stevee/testing/ >>>>>>> * Put them on your IPFire into the "/opt/pakfire/tmp" > directory. >>>>>>> * Unextract the downloaded files with tar - "tar -xvf >>> file.ipfire" and install it with "./install.sh" >>>>>>> * Be sure to install the pyload package at the end - > pyload >>> automatically will be started. >>>>>>> The GUI, as Daniel already documented will be available > at >>> "http://<ip-of-your-ipfire>:8086", the default credentials are >>> "pyload" with the password "secret". >>>>>>> Please report any problems or errors, to get rid of them > and to >>> speed up the final merge into the main distribution. >>>>>>> A big thanks, >>>>>>> >>>>>>> - Stefan >>>>>>> >>>>>>>> Yesterday I've tested the pyload packages from Stevee. >>>>>>>> http://people.ipfire.org/~stevee/testing/ >>>>>>>> >>>>>>>> Installationorder: leptonica, tesseract-ocr, > python-pyOpenSSL, >>>>>>>> python-Jinja2, python-Beaker, python-thrift, > python-simplejson, >>>>>>>> python-pycrypto, python-pytesser, python-PIL, >>> python-BeautifulSoup, >>>>>>>> spidermonkey, sqlite, pycurl, unrar, pyload >>>>>>>> >>>>>>>> sqlite and pycurl you find in the pakfire. >>>>>>>> >>>>>>>> After I've installed everything the pyload webinterface > was >>> reachable on >>>>>>>> ipfire:8086. >>>>>>>> >>>>>>>> username: pyload >>>>>>>> password: secret >>>>>>>> >>>>>>>> At first pyload seems to work fine. Also automatic unrar > and >>> unzip of >>>>>>>> compressed files work fine. >>>>>>>> >>>>>>>> The only thing is that every one minute there is the > following >>> entry in >>>>>>>> the logfile. >>>>>>>> >>>>>>>> 149 28.05.2013 08:49:34 ERROR Error executing hooks: > 'NoneType' >>> object >>>>>>>> has no attribute '__getitem__' >>>>>>>> 150 28.05.2013 08:50:34 ERROR Error executing hooks: > 'NoneType' >>> object >>>>>>>> has no attribute '__getitem__' >>>>>>>> 151 28.05.2013 08:51:34 ERROR Error executing hooks: > 'NoneType' >>> object >>>>>>>> has no attribute '__getitem__' >>>>>>>> 152 28.05.2013 08:52:34 ERROR Error executing hooks: > 'NoneType' >>> object >>>>>>>> has no attribute '__getitem__' >>>>>>>> >>>>>>>> Maybe someone could verify it. >>>>>>>> >>>>>>>> - Daniel >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Development mailing list >>>>>>>> Development@lists.ipfire.org >>>>>>>> http://lists.ipfire.org/mailman/listinfo/development >>>>>>> _______________________________________________ >>>>>>> Development mailing list >>>>>>> Development@lists.ipfire.org >>>>>>> http://lists.ipfire.org/mailman/listinfo/development >>>>> _______________________________________________ >>>>> Development mailing list >>>>> Development@lists.ipfire.org >>>>> http://lists.ipfire.org/mailman/listinfo/development >>>> _______________________________________________ >>>> Development mailing list >>>> Development@lists.ipfire.org >>>> http://lists.ipfire.org/mailman/listinfo/development >>> _______________________________________________ >>> Development mailing list >>> Development@lists.ipfire.org >>> http://lists.ipfire.org/mailman/listinfo/development >> _______________________________________________ >> Development mailing list >> Development@lists.ipfire.org >> http://lists.ipfire.org/mailman/listinfo/development > > _______________________________________________ > Development mailing list > Development@lists.ipfire.org > http://lists.ipfire.org/mailman/listinfo/development
Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development
Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development
Development mailing list Development@lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development
-
Daniel Weismüller