From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Jens Rehsack <rehsack@gmail.com>, "Burton, Ross" <ross.burton@intel.com>
Cc: Nick Leverton <nick@leverton.org>,
"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Dropping Debian 7 as supported?
Date: Sat, 13 Feb 2016 17:28:21 +0000 [thread overview]
Message-ID: <1455384501.16142.372.camel@linuxfoundation.org> (raw)
In-Reply-To: <2ABA8704-6F76-49C0-8DD4-8C74295CF4EB@gmail.com>
On Sat, 2016-02-13 at 15:30 +0100, Jens Rehsack wrote:
> > Am 11.02.2016 um 15:32 schrieb Burton, Ross <ross.burton@intel.com>
> > :
> >
> >
> > 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.
>
> Sure, but are there some serious/expensive maintaining efforts
> continuing support Debian 7?
> Or is it an approach to kick Debian from list of supported
> distributions for (above?) reasons?
>
> Since I run some build instances on a Debian 7 machine which is not
> going to be upgraded that
> soon (don't want Debian 8, but don't want to reinstall from scratch
> and migrate my Xen VM's ...),
> dropping support for "it's just time to move on" is more a Desktop
> philosophy, not for embedded/datacenter
> approaches ...
For example, we'd like to use the sparse option when building rootfs:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=9099
This support isn't available in the version of dd in debian 7. Our
options are:
* Build a dd -native
* Check the version of dd and error if too old
* Don't bother with sparse support
We're seeing a few issues like this with debian 7 and the general
feeling is we're better off concentrating on newer distros. We simply
don't have the time/resources to fix/support things like "dd-native" or
more paths through the sanity code.
This doesn't mean you won't be able to make debian 7 work with
something like the buildtools tarball or through other means, it does
mean we're not going to make sure it works out the box though.
So no, its not just "its time to move on".
Cheers,
Richard
next prev parent reply other threads:[~2016-02-13 17:28 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 [this message]
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
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=1455384501.16142.372.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=nick@leverton.org \
--cc=rehsack@gmail.com \
--cc=ross.burton@intel.com \
--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.