Re: client175

Re: client175

[Adolf Belka]

[-- Attachment #1: Type: text/plain, Size: 1096 bytes --]

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.
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

Re: client175

[Adolf Belka]

[-- Attachment #1: Type: text/plain, Size: 1635 bytes --]

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

Re: client175

[Adolf Belka]

[-- Attachment #1: Type: text/plain, Size: 2027 bytes --]

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.
> Interesting because those packages were not required for use before.

Sorry, I misunderstood. I thought you meant that there were additional python modules required to be installed.

I ran 2to3 converter on all the python modules.  Those that were not changed were the ones where the result from 2to3 converter was that there was nothing to change.

cherrypy and BeautifulSoup.py were both converted by 2to3 converter and if they are not working then I will need some help in figuring out what additional changes are required beyond what the 2to3 converter modified. Who can help with figuring those changes out?

Or did I do something wrong with the patch that carries out the diffs between the original python modules and those changes defined by the 2to3 converter?


Regards,

Adolf.


In that case I will need some help on figuring out what changes need to be done on these modules in client175

>> 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

Re: client175

[Adolf Belka]

[-- 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