From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Pending patches for upcoming Core Update 154
Date: Sat, 30 Jan 2021 13:08:36 +0000 [thread overview]
Message-ID: <7f0f5543-5839-c255-24c5-1403077f19bb@ipfire.org> (raw)
In-Reply-To: <295eec12-395b-ec69-c3ef-d6103f7d314f@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1380 bytes --]
Hello Matthias, hello *,
thanks for your reply.
Glad you mention and take care of libgcrypt, that one is important. :-)
Meanwhile, I am trying to get IPFire 2.x build working on my workstation [sic], working on
- binutils 2.36, which requires patching the kernel and hyperscan
- hyperscan 5.4.0
- libseccomp 2.5.1
- Postfix 3.5.9
for Core Update 154.
freetype unfortunately continues to break most recent ghostscript, and I have not yet found
out why. In addition, ghostscript-fonts-std seems to be heavily outdated (8.11 != 9.x), but
I have not found a suitable source for some more current RPMs flying around at OpenSuSE.
Thanks, and best regards,
Peter Müller
> On 27.01.2021 18:15, Peter Müller wrote:
>> Hello *,
>
> Hi,
>
>> to avoid redundancies: I am currently working on Postfix 3.5.9 and (more important) sudo
>> 1.9.5p2 for upcoming Core Update 154. Both fix some security issues; I am pretty sure you
>> have heard of CVE-2021-3156 affecting the latter by now.
>>
>> There might be some minor stuff (USB/PCI database files, etc.) to do as well, but I have
>> not checked that, yet. :-)
>
> My two cents - working ('Devel' does it, I'm only watching ;-) ) on:
>
> libgcrypt => 1.9.1
> libgpg-error => 1.41
> libassuan => 2.5.4
>
> Best,
> Matthias
>
>>
>> Thanks, and best regards,
>> Peter Müller
>>
>
next prev parent reply other threads:[~2021-01-30 13:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 17:15 Peter Müller
2021-01-27 19:04 ` Peter Müller
2021-01-27 19:13 ` Adolf Belka
2021-01-27 19:58 ` Peter Müller
2021-01-27 20:05 ` Adolf Belka
2021-01-28 20:20 ` Peter Müller
2021-01-30 16:29 ` Michael Tremer
2021-01-30 17:26 ` Peter Müller
2021-02-01 11:17 ` Michael Tremer
2021-01-30 13:00 ` Matthias Fischer
2021-01-30 13:08 ` Peter Müller [this message]
2021-01-30 13:51 ` Adolf Belka
2021-01-30 16:52 ` Adolf Belka
[not found] <AC2550F9-7FCE-4533-90BF-B8E46F825D8E@gmail.com>
2021-02-05 8:32 ` Adolf Belka
2021-02-05 11:10 ` Michael Tremer
[not found] <26ED65B8-154A-4476-B9E6-7DCD58078E0C@gmail.com>
2021-02-05 11:10 ` Michael Tremer
2021-02-05 11:38 ` Adolf Belka
2021-02-05 16:19 ` Michael Tremer
2021-02-05 17:31 ` Adolf Belka
2021-02-05 17:46 ` Michael Tremer
2021-02-05 17:59 ` 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=7f0f5543-5839-c255-24c5-1403077f19bb@ipfire.org \
--to=peter.mueller@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