From: Joshua Lock <joshua.g.lock@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>,
Bas Mevissen <abuse@basmevissen.nl>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Yocto 2.2 Morty supported Linux Distros
Date: Wed, 02 Nov 2016 10:05:25 +0000 [thread overview]
Message-ID: <1478081125.22552.6.camel@linux.intel.com> (raw)
In-Reply-To: <CAJTo0Lat2oz3dpRXC6tSve3drTMB+=93mfR=0-UjxYtfgqLrxw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1003 bytes --]
On Tue, 2016-11-01 at 17:11 +0000, Burton, Ross wrote:
>
> > > On 1 November 2016 at 17:05, Bas Mevissen <abuse@basmevissen.nl>
wrote:
> > What are the criteria to call a distro supported?
> >
>
> > > The short version is that it's a distro that doesn't change too much,
is still supported, and we have builders on
autobuilder.yoctoproject.org running that distro.
>
> The Centos mismatch is annoying, can you please file a bug?
>
We previously had CentOS-7.* which was changed to CentOSLinux-7 in
meta-yocto ce1fe45e9a18a82e2b95ea7e0b088ba595ceeee6.
What's going on here? Are CentOS really changing the value of their
Distributor ID for a released version?
Or is the issue here that they aren't using consistent values for
Distributor ID and its equivalent across /etc/lsb-release, /etc/redhat-
release, /etc/os-release and other potential sources?
Can someone with a CentOS 7 box pastebin their /etc/lsb-release,
/etc/redhat-release and /etc/os-release?
Joshua
>
[-- Attachment #2: Type: text/html, Size: 1567 bytes --]
next prev parent reply other threads:[~2016-11-02 10:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-01 15:19 Yocto 2.2 Morty supported Linux Distros Vuille, Martin (Martin)
2016-11-01 15:22 ` Herman van Hazendonk
2016-11-01 15:27 ` Burton, Ross
2016-11-01 15:30 ` Vuille, Martin (Martin)
2016-11-01 17:05 ` Bas Mevissen
2016-11-01 17:11 ` Burton, Ross
2016-11-01 20:39 ` Paul Eggleton
2016-11-01 21:36 ` Bas Mevissen
2016-11-01 22:20 ` Daniel.
2016-11-01 23:22 ` Burton, Ross
2016-11-01 23:35 ` Khem Raj
2016-11-02 14:21 ` Daniel.
2016-11-02 14:27 ` Burton, Ross
2016-11-07 22:22 ` Brian Avery
2016-11-02 10:05 ` Joshua Lock [this message]
2016-11-02 16:41 ` Bas Mevissen
2016-11-02 21:31 ` Joshua Lock
2016-11-03 10:34 ` Joshua Lock
2016-11-03 12:59 ` Bas Mevissen
2016-11-03 1:17 ` Trevor Woerner
[not found] <c183wyprgqw24wdj3xxijdsr.1478091740228@email.android.com>
[not found] ` <CAFNP8OvOhcd9tFTWS4NhS2GMfcHyFp0MOtDy5y4fYscMAdPvnA@mail.gmail.com>
2016-11-07 14:27 ` Burton, Ross
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=1478081125.22552.6.camel@linux.intel.com \
--to=joshua.g.lock@linux.intel.com \
--cc=abuse@basmevissen.nl \
--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.