From: Stefan Schantl <stefan.schantl@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: pyload
Date: Wed, 29 May 2013 21:53:19 +0200 [thread overview]
Message-ID: <51A65CAF.7010700@ipfire.org> (raw)
In-Reply-To: <1369725144.2201.12.camel@fedora18x64-lan-e82.lan.e82>
[-- Attachment #1: Type: text/plain, Size: 2397 bytes --]
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(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development
next prev parent reply other threads:[~2013-05-29 19:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-28 7:12 pyload Daniel Weismüller
2013-05-29 19:53 ` Stefan Schantl [this message]
[not found] <155834D1-2868-4CE4-9AE3-FD6107AFD2C1@ipfire.org>
2013-05-30 8:32 ` pyload Erik K.
2013-05-30 15:52 ` pyload Erik K.
[not found] <SNT136-W50484950C5A451C1A0E4DC5920@phx.gbl>
2013-06-04 15:07 ` pyload Michael Tremer
2013-06-17 9:04 ` pyload Daniel Weismüller
2013-07-02 12:57 ` pyload Daniel Weismüller
2013-07-02 18:12 ` pyload Thomas Ebert
2013-07-03 13:30 ` pyload Thomas Ebert
2013-07-04 10:51 ` pyload Michael Tremer
2013-07-24 13:14 ` pyload Daniel Weismüller
[not found] <51F012B9.4070005@gmx.de>
2013-07-25 6:27 ` pyload Daniel Weismüller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51A65CAF.7010700@ipfire.org \
--to=stefan.schantl@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox