From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: client175
Date: Mon, 13 Sep 2021 15:05:18 +0200 [thread overview]
Message-ID: <11b5d539-2bfd-6fcd-f3cb-69005305bbd9@ipfire.org> (raw)
In-Reply-To: <f7a6dc6e26314a0acbc998012dd8edf0@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 3425 bytes --]
Hi Arne,
On 13/09/2021 10:51, Arne Fitzenreiter wrote:
> I have installed it on updated testmachine via pakfire unstable tree (nightly build from next).
> The server will not startup so i was bot able to get the webgui at all
I installed the client175 .ipfire package onto a Core Update 159 VM machine on my testbed. I was able to get the webgui page shown but I also could not get the program to start. In the /var/log/client175 file there were error messages related to server.py and a couple of modules from cherrypy.
These are the error messages:-
Traceback (most recent call last):
File "/srv/client175/server.py", line 23, in <module>
import cherrypy, json, os, pwd, urllib.request, urllib.parse, urllib.error, urllib.request, urllib.error, urllib.parse, sys
File "/srv/client175/cherrypy/__init__.py", line 156, in <module>
from cherrypy._cperror import HTTPError, HTTPRedirect, InternalRedirect
File "/srv/client175/cherrypy/_cperror.py", line 3, in <module>
from cgi import escape as _escape
ImportError: cannot import name 'escape' from 'cgi' (/usr/lib/python3.8/cgi.py)
It wouldn't surprise me if even if these messages were solved there might be further erros in other modules. It looks to me like the client175 python modules are not easily converted by 2to3.
I suspect that if client175 is to stay in IPFire then python2 will need to stay to be able to run the existing python2 modules. python2 could be built as an addon dependency so that it is only installed if client175 is selected.
Regards,
Adolf.
>
> I will retest this after finishing core160
>
> Arne
>
>
> Am 2021-09-12 22:05, schrieb Adolf Belka:
>> Hi Arne,
>>
>> On 12/09/2021 21:41, Adolf Belka wrote:
>>> Hi Arne,
>>>
>>> On 12/09/2021 17:37, Arne Fitzenreiter wrote:
>>>> I have tested client175 today. Unfortunately not work at my testsystem.
>>>>
>>>> It give a lot of errors missing deps of cherrypy and beatifulsoup also some files in root are not converted.
>>
>> Did you get these errors when you tried to play some music or when the
>> client175 cgi page was rendered.
>>
>> I installed my client175 iso into my VM testbed and was able to see
>> the cgi page from client175. I could also get it to show music files
>> stored in directories.
>>
>> I just couldn't get it to test actually playing any music as my
>> VirtualBox VM had no audio capability. I am trying to see if I can
>> correct that situation now.
>>
>>
>> Regards,
>>
>> Adolf.
>>
>>> Interesting because those packages were not required for use before.
>>>> Looks like you have missed some files to put folder to create the patch because there are some not python3 syntax. (mpd.py and mpd-proxy.py has print without parenthesis)
>>>
>>> If you can send me the log messages you got from trying to run client175 I will look at what I need to do to fix this.
>>>
>>> I will also see if there is any way I can get a sound capability going on my VirtualBox VM testbed so that I can actually test out any following client 175 update before submitting it.
>>>
>>> Sorry for the problems.
>>>
>>> I think this confirms that we won't have all the python2 removals completed in Core Update 160. My various fixes will probably need to go into Core Update 161 meaning that the python2 removal will have to go into Core Update 162.
>>>
>>> Regards,
>>> Adolf.
>>>>
>>>> Arne
next parent reply other threads:[~2021-09-13 13:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f7a6dc6e26314a0acbc998012dd8edf0@ipfire.org>
2021-09-13 13:05 ` Adolf Belka [this message]
[not found] <08571798269f0ec4b4c0772c71f3511e@ipfire.org>
2021-09-12 19:41 ` client175 Adolf Belka
2021-09-12 20:05 ` client175 Adolf Belka
2021-09-12 21:05 ` client175 Adolf Belka
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=11b5d539-2bfd-6fcd-f3cb-69005305bbd9@ipfire.org \
--to=adolf.belka@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