From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: client175
Date: Sun, 12 Sep 2021 23:05:10 +0200 [thread overview]
Message-ID: <526e08d0-11ec-54ca-7979-4291454cb188@ipfire.org> (raw)
In-Reply-To: <655be8fb-66ce-482d-1107-c56c27228068@ipfire.org>
[-- 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
next prev parent reply other threads:[~2021-09-12 21:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 ` Adolf Belka [this message]
[not found] <f7a6dc6e26314a0acbc998012dd8edf0@ipfire.org>
2021-09-13 13: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=526e08d0-11ec-54ca-7979-4291454cb188@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