public inbox for ipfire-announce@lists.ipfire.org
 help / color / mirror / Atom feed
From: The IPFire Project <ipfire-announce@lists.ipfire.org>
To: ipfire-announce@lists.ipfire.org
Subject: IPFire 2.19 - Core Update 118 is almost there
Date: Tue, 06 Feb 2018 16:01:13 +0000	[thread overview]
Message-ID: <mailman.278.1517932902.839.ipfire-announce@lists.ipfire.org> (raw)

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

https://planet.ipfire.org/post/ipfire-2-19-core-update-118-is-almost-there
Hello Community,

the next Core Update 118 is almost there. We have no major new bugs left any
more and it is good to go. But before our release engineering team pulls the
trigger and is releasing this for everyone of you, we would like to make you
aware again that a number of add-on packages has been discontinued and will
automatically be uninstalled when Core Update 118 is installed. Those are:

  * nagios & nagiosql, because we have Icinga, which is a fork of the famous
    monitoring tool
  * mediatomb & openmailadmin which are both not maintained upstream any more
  * cacti, phpsane & owncloud which require PHP which has also been dropped
    in this release

PHP is being removed for security reasons and for more and more of the software
that we ship becoming independent from it. If you have installed any custom
applications that use PHP, please move them to another machine.

We are sending you this deprecation announcement to give you some extra time to
prepare for the upcoming changes in case you have missed them from the pre-
announcement of this Core Update.

                 reply	other threads:[~2018-02-06 16:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=mailman.278.1517932902.839.ipfire-announce@lists.ipfire.org \
    --to=ipfire-announce@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