From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Updating packages for IPFire 2.x
Date: Sun, 17 Jun 2018 11:10:41 +0200 [thread overview]
Message-ID: <1529226641.2484.7.camel@ipfire.org> (raw)
In-Reply-To: <362d761d-8f2d-04df-0fd9-fdbd880549c6@link38.eu>
[-- Attachment #1: Type: text/plain, Size: 1634 bytes --]
Hi Peter, Hi all,
i do have also some updates for packages in the PIPE which i do have
also positively tested. This packages are:
fping-4.0
mtr-0.92
libstatgrab-0.91
<-- May Glances https://forum.ipfire.org/viewtopic.phpt=16563 might
be a better substitution for this
tmux-2.7
ipset-6.38
<-- Needs to be checked with Core122 test install (may today)
Have also some OpenVPN bugfixes (one is delivered) but it is a little
quiet on the list, is the patch delivering cycle currently may off ?
@Peter
May you remember the Rsyslog thing ? We had there
https://lists.ipfire.org/pipermail/development/2018-April/004227.html
a conversation about ? Did you go for a checkout of this ?
Greetings,
Erik
Am Sonntag, den 17.06.2018, 10:44 +0200 schrieb Peter Müller:
> Hello Matthias, hello *,
>
> recently, I was struggled updating the NRPE package in IPFire. Since
> I learned a lot while doing so, and several packages are outdated
> (some of them seem to be security relevant), I thought to update some
> more.
>
> Reading the development list, it seems like this is more or less
> what you are doing - so it seems to be a good thing to coordinate
> here
> if you don't mind.
>
> Personally, I would like to go through every package in IPFire 2.x
> and check whether it can be removed or needs to be updated.
>
> What do you think of this?
>
> Best regards,
> Peter Müller
>
> P.S.: Updating bash to 4.4 did not work here (there were a bunch
> of poorly documented patches for 4.3 which won't apply, and some
> other
> manholes I fell in) - in case anybody has experience with updating
> bash, please drop me a line.
next prev parent reply other threads:[~2018-06-17 9:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-17 8:44 Peter Müller
2018-06-17 9:10 ` ummeegge [this message]
2018-06-20 15:22 ` Peter Müller
2018-06-21 10:20 ` ummeegge
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=1529226641.2484.7.camel@ipfire.org \
--to=ummeegge@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