public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <peter.mueller@link38.eu>
To: development@lists.ipfire.org
Subject: Updating packages for IPFire 2.x
Date: Sun, 17 Jun 2018 10:44:34 +0200	[thread overview]
Message-ID: <362d761d-8f2d-04df-0fd9-fdbd880549c6@link38.eu> (raw)

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

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.
-- 
"We don't care.  We don't have to.  We're the Phone Company."


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2018-06-17  8:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-17  8:44 Peter Müller [this message]
2018-06-17  9:10 ` ummeegge
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=362d761d-8f2d-04df-0fd9-fdbd880549c6@link38.eu \
    --to=peter.mueller@link38.eu \
    --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