From: Adolf Belka <ahb.ipfire@gmail.com>
To: development@lists.ipfire.org
Subject: Re: Pending package updates
Date: Tue, 01 Sep 2020 23:01:43 +0200 [thread overview]
Message-ID: <a4eceda9-16d6-5d84-07a1-3aa4b9b18e88@gmail.com> (raw)
In-Reply-To: <a37bfccb-90c8-6fa8-7e90-133e5c106b71@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1134 bytes --]
Hi Peter,
I am running Arch Linux based systems and it looks like I can build IPFire 2.x so I will have a go at those updates. As long as they are just version updates I should be able to manage that. If I come across any problems I will get back to the list.
All the best,
Adolf Belka
On 01/09/2020 20:22, Peter Müller wrote:
> Hello *,
>
> some rather important packages within IPFire 2.x are in need of being updated:
> - Strongswan 5.9.0
> - Postfix 3.5.7
> - libnetfilter_queue 1.0.5
> - iptables 1.8.5
> - libnetfilter_conntrack 1.0.8
> - conntrack-tools 1.4.6
>
> Since IPFire 2.x currently refuses to build on my workstation ("kernel too old", running
> OpenSuSE Leap 15.1), I cannot take care of those until I found some spare time to undergo
> a distribution upgrade, which probably does not happen before mid-September.
>
> Is somebody else currently in luxury of being capable to build IPFire 2.x? If yes,
> might I ask that person to have a look at those packages, so we can ship them in
> Core Update 150? :-)
>
> 1001 thanks in advance.
>
> Thanks, and best regards,
> Peter Müller
next prev parent reply other threads:[~2020-09-01 21:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-01 18:22 Peter Müller
2020-09-01 21:01 ` Adolf Belka [this message]
2020-09-02 13:26 ` Michael Tremer
2020-09-02 13:42 ` Adolf Belka
2020-09-02 14:24 ` Adolf Belka
2020-09-02 15:36 ` Michael Tremer
2020-09-02 16:02 ` Matthias Fischer
2020-09-02 18:27 ` Matthias Fischer
2020-09-03 8:14 ` Adolf Belka
2020-09-03 8:23 ` Adolf Belka
2020-09-04 15:46 ` Michael Tremer
2020-09-05 14:09 ` Adolf Belka
2020-09-07 11:33 ` Adolf Belka
2020-09-07 13:16 ` Adolf Belka
2020-09-02 13:25 ` 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=a4eceda9-16d6-5d84-07a1-3aa4b9b18e88@gmail.com \
--to=ahb.ipfire@gmail.com \
--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