From: Nick Leverton <nick@leverton.org>
To: yocto@yoctoproject.org
Subject: Re: Dropping Debian 7 as supported?
Date: Tue, 16 Feb 2016 10:18:12 +0000 [thread overview]
Message-ID: <3643440.C5VSuRxHDx@nickl> (raw)
In-Reply-To: <CAJTo0LY6r8od5c3rysNWFg=-3c0jWx4STaaPQD-pcEmUmqh2Dw@mail.gmail.com>
On Thursday 11 Feb 2016 14:32:50 Burton, Ross wrote:
> On 11 February 2016 at 14:21, Nick Leverton <nick@leverton.org> wrote:
> > Possibly a little early - Debian 7 will be going onto LTS security support
> > for
> > two years, starting some time this month. Quoting from
> > https://wiki.debian.org/LTS
>
> Ah yes, I'd forgotten about the LTS project and was looking at the security
> team.
>
> This does make it less clear, but it's still an old release and we can't
> support/test on everything.
I agree it appears old by the standards of fast moving bleeding edge distros.
But despite what I said last week it's not really that ancient. Debian 7 is
still an officially supported version, and as an LTS version you're perhaps now
more likely to find your own users still on it.
The LTS announcement was made just this weekend, by the way:
"There will be no further security support for Debian 6.0.
The LTS Team will prepare the transition to Debian 7 ("wheezy"), which
is the current oldstable release. The LTS team will take over support
from the Security Team on April 26, 2016.
Debian 7 will also receive Long Term Support for five years after its
initial release with support ending in May 2018"
I can't say what Yocto ought to do, but if it were possible to make the sparse
support into an option, would that be a compromise ? The patch linked from
#9099 suggests that only two places would need to use that option.
Nick
prev parent reply other threads:[~2016-02-16 10:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-11 14:11 Dropping Debian 7 as supported? Burton, Ross
2016-02-11 14:11 ` Burton, Ross
2016-02-11 14:21 ` Nick Leverton
2016-02-11 14:32 ` Burton, Ross
2016-02-12 13:43 ` Nick Leverton
2016-02-12 17:14 ` Fred Ollinger
2016-02-12 17:18 ` Burton, Ross
2016-02-12 17:19 ` Fred Ollinger
2016-02-13 14:30 ` Jens Rehsack
2016-02-13 17:28 ` Richard Purdie
2016-02-13 18:12 ` Khem Raj
2016-02-14 10:24 ` Richard Purdie
2016-02-14 15:17 ` Khem Raj
2016-02-15 6:54 ` Jens Rehsack
2016-02-16 10:18 ` Nick Leverton [this message]
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=3643440.C5VSuRxHDx@nickl \
--to=nick@leverton.org \
--cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.