From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Core Update 157
Date: Mon, 17 May 2021 23:52:54 +0200 [thread overview]
Message-ID: <36ab2dee-02e8-6cad-ff97-b4f1a6e9ffd6@ipfire.org> (raw)
In-Reply-To: <B0CDF18F-6E0F-4B34-BB1D-4137E04BAEB2@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2174 bytes --]
Hi Michael,
I don't have anything new that I am working on that needs to go into 157. I just keep finding things that can be updated and so I update them. I am quite happy for you to decide which Core Update they should go in.
In terms of python2 the big barrier to removing python2 at some point is crda. From my investigation it requires the python2 version of M2Crypto. The python2 version of M2crypto requires the python2 versions of typing and setuptools. All the other python2 to python3 migrations seemed to go okay.
Regards,
Adolf.
On 17/05/2021 23:23, Michael Tremer wrote:
> Hello,
>
> Because there are so many things going on at the same time, I would like to start a brief main thread about the upcoming Core Update(s).
>
> The original plan was to have this closed a while ago because Core Update 156 has already gone out. But then I decided to wait for a couple of smaller things until we had a security vulnerability reported which I wanted to investigate more (#12616 and #12619). It is not too bad, but I would like to ship at least a fix that is good enough to mitigate it. We might need some more time to figure out the details around the other half of the solution for this problem.
>
> Now this update has become *very* large. It is the largest update we have ever had and that might break things. Therefore I do not want to merge anything more that has to go into the core system, but add-on packages are fine.
>
> In fact, the build that I just pushed should be the final one, unless we find any other problems. Does anyone have anything urgent and small left? Otherwise Core Update 158 will be open as soon as 157 has hit the master branch.
>
> In order to coordinate that a little bit more and have a good and hopefully brief merge window, what should be in it?
>
> * Fixes for #12616
> * Can we finish the migration away from Python 2?
> * Drop the packages discussed at the last conference call (https://wiki.ipfire.org/devel/telco/2021-05-03)?
> * VPNs for iOS (https://patchwork.ipfire.org/project/ipfire/list/?series=1323)?
>
> What else are you guys working on that is ready for prime-time?
>
> -Michael
next prev parent reply other threads:[~2021-05-17 21:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 21:23 Michael Tremer
2021-05-17 21:28 ` Peter Müller
2021-05-17 21:29 ` Michael Tremer
2021-05-17 22:02 ` Peter Müller
2021-05-18 8:53 ` Michael Tremer
2021-05-17 21:52 ` Adolf Belka [this message]
2021-05-17 21:53 ` Michael Tremer
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=36ab2dee-02e8-6cad-ff97-b4f1a6e9ffd6@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