public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Core Update 156
Date: Wed, 07 Apr 2021 21:08:25 +0100	[thread overview]
Message-ID: <15C6428B-CB5B-400E-880F-418AF6016CC0@ipfire.org> (raw)
In-Reply-To: <d47a4141-7c81-16ce-cb0c-7c25e7279314@ipfire.org>

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

Hello,

> On 7 Apr 2021, at 17:43, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
> 
> Hi All,
> 
> I submitted the v2 version of pmacct about 10 days ago based on the input to the first version. Is this package good to go for CU156 or is further discussion still needed.
> 
> I am currently updating bash/readline and a patch will probably be submitted later today or tomorrow.  Looking at the changes in bash from 5.0 to 5.1 I don't see anything that says this update needs to go into CU156 so I would leave it for CU157.

Unless it is security-critical there is probably no difference.

It would be good if we could tag another toolchain soon so that we can merge everything that is still pending in that regard, but we will probably break add-ons if we do not bump the major version number.

Best,
-Michael

> Regards,
> Adolf.
> 
> 
> On 07/04/2021 17:04, Michael Tremer wrote:
>> Hello,
>> 
>> I would like to formally close Core Update 156 as soon as possible to merge it into “master” and release it to a wider audience for testing.
>> 
>> Does anyone have any changes that *must* be in this update?
>> 
>> I have the following things on my list:
>> 
>> * Dropping macvtap support: This is broken and I do not think that we would need this because we have bridges. Please review my proposed patch: https://lists.ipfire.org/pipermail/development/2021-April/009858.html
>> 
>> * Jonatan wanted to drop the other templates for the web UI
>> 
>> * Peter has some sysctl changes
>> 
>> Apart from that I would like to move our attention to testing this update and collecting patches for the next update. Core Update 156 is already quite large (15 MB compressed on x86_64) and so I would reject any larger changes unless really necessary.
>> 
>> Lots of thanks to Adolf for putting in so many hours to update all these packages that have received so little love in the past. Especially Perl is one of those which take ages and ages :)
>> 
>> Best,
>> -Michael
> 
> -- 
> Sent from my laptop
> 


  reply	other threads:[~2021-04-07 20:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-07 15:04 Michael Tremer
2021-04-07 15:39 ` Robin Roevens
2021-04-07 15:41   ` Michael Tremer
2021-04-07 16:43 ` Adolf Belka
2021-04-07 20:08   ` Michael Tremer [this message]
2021-05-11 11:16   ` Adolf Belka
2021-05-11 11:29     ` Michael Tremer
2021-05-11 12:42       ` pmacct (was Core Update 156) Adolf Belka
2021-05-11 13:17         ` Michael Tremer
2021-05-11 13:51           ` Adolf Belka
2021-05-11 16:44             ` Michael Tremer
2021-04-07 18:32 ` Core Update 156 Michael Tremer
2021-04-07 19:37   ` Matthias Fischer
2021-04-07 19:52   ` Matthias Fischer
2021-04-07 20:07     ` 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=15C6428B-CB5B-400E-880F-418AF6016CC0@ipfire.org \
    --to=michael.tremer@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