public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Pending patches for upcoming Core Update(s)
Date: Fri, 19 Feb 2021 10:02:28 +0100	[thread overview]
Message-ID: <a83551bd-e430-e1e4-d664-1d68de3411b3@ipfire.org> (raw)

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

Hi,

FYI and to avoid redundancies, I got one of the 64bit-'Devels' working on:

tar => 1.34
bind => 9.11.28
nettle => 3.7.1
libgcrypt => 1.9.2
krb5 => 1.19.1

And, because it "just came my way":
rust => 1.50 (under x86-64, this is huge - about ~1.2GB sources)

Opinions for this update(s)?

I'm just not so sure with the latter - do we want this?
As I see it, 'suricata' must then also be at least shipped or even updated.

Besides, 'suricata 6.0.1' is still running here with the 'usleep
(5000)'-patch. So far, without - seen! - problems. Any news on this? If
wanted, I could provide a patchset so "someone" else could test this!?

Best,
Matthias

             reply	other threads:[~2021-02-19  9:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-19  9:02 Matthias Fischer [this message]
2021-02-19 10:59 ` Michael Tremer
2021-02-19 11:02   ` 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=a83551bd-e430-e1e4-d664-1d68de3411b3@ipfire.org \
    --to=matthias.fischer@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