From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Patches to be merged to be capable of removing python2
Date: Mon, 13 Sep 2021 11:07:37 +0200 [thread overview]
Message-ID: <aedf1c97-5250-adcb-cc8c-2f8c455e66b3@ipfire.org> (raw)
In-Reply-To: <980510301a55e5a28acf1a23427fd5b2@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 3990 bytes --]
Hi Arne,
On 13/09/2021 10:57, Arne Fitzenreiter wrote:
> I had already merged freeradius yesterday.
My pull on next must have been before you did that merge because the freeradius lfs I have in my build is the earlier version.
>
> At the moment patchwork is not working so you should wait antil the server is up again.
The frr build is still ongoing. Before I submit the patch I will check that patchwork is back up and running.
I have the feeling that client175 will be the problem package. It doesn't work for you but I was able to get the gui page up when I tested my change on my vm testbed.
After frr is built and submitted, I will do a build of the current state of Core Update 160 and install that on my vm testbed and then install the client175 change via the .ipfire package and see if it still works for me or no longer.
Regards,
Adolf.
>
> Arne
>
>
>
> Am 2021-09-13 10:41, schrieb Adolf Belka:
>> Hi Arne,
>>
>> On 12/09/2021 21:36, Adolf Belka wrote:
>>> Hi Arne,
>>>
>>> On 12/09/2021 18:12, Arne Fitzenreiter wrote:
>>>> At the moment i have not merged all of this. (frr, alsa and freeradius are missing)
>>>> but core160 is already large...
>>>>
>>>> But at my test i merged the python2 remove by an accident and only frr has made problems.
>>>> So i think freeradus and alsa detect the missing python2 but of course the patches should merged
>>>> but not in core160 because alsa is large.
>>> That's interesting. When I ran without python2 on Core Update 159, alsa and freeradius definitely would not build on my system.
>>>
>>> I will go back and have another test on my build system but with Core Update 160 merged to current status to see what happens with python2 removed.
>>>
>> I ran the current updated next with python2 removed and alsa and
>> collectd both successfully built without any hiccups. That definitely
>> didn't happen when I did my original test which would have been back
>> when next was being put together for Core Update 158.
>>
>> Probably I made some mistake.
>>
>> Anyway with Core Update 160 as it currently is my patches for python
>> fixes for alsa and collectd are not needed and they should be dropped
>> from Patchwork.
>>
>> I will test with frr and freeradius this morning. I will do a new
>> patch for frr anyway as that package was a bit out of date anyway.
>>
>> Will report back later what I find.
>>
>> EDIT:-
>> There was some infrastructure problem with IPFire, couldn't access any
>> IPFire location or send email, so I am able to edit this mail before
>> sending.
>>
>> frr failed to build due to lack of python2, so it definitely needs to
>> be updated for the removal of python2 and because it is old.
>>
>> freeradius built without a problem, so that is a third of my patches
>> that is not required to be merged now. Please drop that patch in
>> Patchwork.
>>
>> Regards,
>>
>> Adolf.
>>
>>> Regards,
>>> Adolf.
>>>>
>>>> Arne
>>>>
>>>>
>>>>
>>>> Am 2021-09-10 08:57, schrieb Adolf Belka:
>>>>> Dear All,
>>>>>
>>>>>
>>>>> For clarification here is the list of the patches or patch series that
>>>>> need to be merged to get to the position where python2 is capable of
>>>>> being removed.
>>>>>
>>>>>
>>>>> alsa
>>>>> https://patchwork.ipfire.org/project/ipfire/patch/20210820200636.3535891-1-adolf.belka(a)ipfire.org/
>>>>> ca-certificates https://patchwork.ipfire.org/project/ipfire/list/?series=2282
>>>>> collectd
>>>>> https://patchwork.ipfire.org/project/ipfire/patch/20210820200551.3535831-1-adolf.belka(a)ipfire.org/
>>>>> crda https://patchwork.ipfire.org/project/ipfire/list/?series=2264
>>>>> freeradius
>>>>> https://patchwork.ipfire.org/project/ipfire/patch/20210820200613.3535863-1-adolf.belka(a)ipfire.org/
>>>>> frr https://patchwork.ipfire.org/project/ipfire/list/?series=2260
>>>>> spice https://patchwork.ipfire.org/project/ipfire/list/?series=2296
>>>>>
>>>>>
>>>>> Regards,
>>>>>
>>>>> Adolf.
next prev parent reply other threads:[~2021-09-13 9:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-10 6:57 Adolf Belka
2021-09-12 16:12 ` Arne Fitzenreiter
2021-09-12 16:18 ` Arne Fitzenreiter
2021-09-12 19:36 ` Adolf Belka
2021-09-13 8:41 ` Adolf Belka
2021-09-13 8:57 ` Arne Fitzenreiter
2021-09-13 9:07 ` Adolf Belka [this message]
2021-09-15 15:24 ` Michael Tremer
2021-09-15 16:32 ` Adolf Belka
2021-09-21 10:02 ` Michael Tremer
2021-09-21 10:23 ` Adolf Belka
2021-09-21 11:31 ` 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=aedf1c97-5250-adcb-cc8c-2f8c455e66b3@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