From: richard.purdie@linuxfoundation.org
To: "Jain, Sangeeta" <sangeeta.jain@intel.com>,
"yocto@yoctoproject.org" <yocto@yoctoproject.org>,
"Tummalapalli, Vineela" <vineela.tummalapalli@intel.com>
Cc: "otavio@ossystems.com.br" <otavio@ossystems.com.br>,
"Chan, Aaron Chun Yew" <aaron.chun.yew.chan@intel.com>,
"akuster808@gmail.com" <akuster808@gmail.com>
Subject: Re: QA notification for completed autobuilder build (yocto-2.8_M3.rc1)
Date: Mon, 23 Sep 2019 08:45:36 +0100 [thread overview]
Message-ID: <726da48bae7285caade355afd47c57208dfd6742.camel@linuxfoundation.org> (raw)
In-Reply-To: <CY4PR11MB187994BFF9D0605ADCB50754E3850@CY4PR11MB1879.namprd11.prod.outlook.com>
On Mon, 2019-09-23 at 07:37 +0000, Jain, Sangeeta wrote:
> Hi Richard,
>
> LSB support was expected to be removed from build 'yocto-2.8_M3.rc1'
> onwards, but link on AB still points to LSB images.
> The images present inside
> https://autobuilder.yocto.io/pub/releases/yocto-2.8_M3.rc1/machines/genericx86-64-lsb/
> are built with systemd as init manager.
>
> Can you please confirm if these are altcfg images and the link name
> needs to updated?
Well spotted!
I can confirm these are altcfg images which have systemd as the init
manager.
For backwards compatibility the autobuilder target names didn't change
but the configuration they're built with did. I hadn't realised this
would be visible in the release so we may need to think about that for
M4 but they are altcfg images.
[Added Vineela to cc:]
Cheers,
Richard
next prev parent reply other threads:[~2019-09-23 7:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190920050052.0C767E00D8F@yocto-www.yoctoproject.org>
[not found] ` <9DDD2658D1FE414E99172D2DB1E4D0434823F10E@PGSMSX109.gar.corp.intel.com>
2019-09-23 3:08 ` QA notification for completed autobuilder build (yocto-2.8_M3.rc1) Jain, Sangeeta
2019-09-23 7:37 ` Jain, Sangeeta
2019-09-23 7:45 ` richard.purdie [this message]
2019-09-23 7:51 ` Jain, Sangeeta
2019-09-20 5:00 pokybuild
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=726da48bae7285caade355afd47c57208dfd6742.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=aaron.chun.yew.chan@intel.com \
--cc=akuster808@gmail.com \
--cc=otavio@ossystems.com.br \
--cc=sangeeta.jain@intel.com \
--cc=vineela.tummalapalli@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.