From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Core Update 156
Date: Tue, 11 May 2021 12:29:01 +0100 [thread overview]
Message-ID: <37854022-BDDE-4A49-8200-048381CAAF83@ipfire.org> (raw)
In-Reply-To: <cfdb29d5-6303-3fa5-7c95-3a00bfe6671f@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2746 bytes --]
Hello,
> On 11 May 2021, at 12:16, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>
> Hi Michael,
>
> With the release of Core Update 156 out of the way is pmacct good to go for Core Update 157 or are further changes required.
I did not have any plans. The conversation around this has just died another time and I do not really remember where we left it.
I really do not want to carry around stuff that nobody cares about and that the conversation has died multiple times suggests just that. In fact we are trying to drop more dead stuff because if nobody updates it and nobody uses it, what is the point?
What is your view of the things around pmacct? Is it ready? What do users gain from having it in the distribution?
Apart from that, I wanted to close Core Update 157 pretty much this week because the big things have been merged so far. We have some Python 2 migration stuff on the list which can wait for 158, it is important but not urgent.
Did I miss anything?
-Michael
> Regards,
>
> Adolf.
>
> On 07/04/2021 18:43, Adolf Belka 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.
>>
>> 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
>>
next prev parent reply other threads:[~2021-05-11 11:29 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
2021-05-11 11:16 ` Adolf Belka
2021-05-11 11:29 ` Michael Tremer [this message]
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=37854022-BDDE-4A49-8200-048381CAAF83@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