date:20191105

Re: [yocto] help with meta-java

2019-11-05 Thread Vincent Prince

Hi Tim,

There are some pending stuff on meta-java ML
openembedded-de...@lists.openembedded.org and layer is not zeus
compatible yet.
I'm trying to contact layer maintainers for several weeks, i don't
know if information is obsolete or if people are too busy/away?

Main layer maintainers:
  Henning Heinold 
  Maxin John 
  Otavio Salvador 
  Richard Leitner 

For now, I just use master-next, and I'm considering using
https://github.com/AdoptOpenJDK/ prebuilds, meta-java is quite hard to
understand I found :)

Best regards,
Vincent

Le lun. 4 nov. 2019 à 18:23, Shockley, Timothy
 a écrit :
>
> Helllo,
>
>
>
> I am looking for some help with meta-java, specifically upgrading to zeus 
> branch and also upgrading openjdk to a more recent release in order to 
> address CVEs. Wondering if there is anyone else working / needing this?
>
>
>
> Thanks,
>
> Tim Shockley
>
>
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] help with meta-java

2019-11-05 Thread Richard Leitner


Hi,
unfortunately, due to a different focus on my day job in the previous 
months I didn't had time for doing any work on meta-java.


This will change in the coming weeks and I will start to review and test 
patches again.


Nonetheless it would be great if one of the other listed maintainers (or 
somebody else) can support me as there will be significant refactoring, 
cleanup and update work to be done ;-)


regards;Richard.L

On 05/11/2019 09:18, Vincent Prince wrote:

Hi Tim,

There are some pending stuff on meta-java ML
openembedded-de...@lists.openembedded.org and layer is not zeus
compatible yet.
I'm trying to contact layer maintainers for several weeks, i don't
know if information is obsolete or if people are too busy/away?

Main layer maintainers:
   Henning Heinold 
   Maxin John 
   Otavio Salvador 
   Richard Leitner 

For now, I just use master-next, and I'm considering using
https://github.com/AdoptOpenJDK/ prebuilds, meta-java is quite hard to
understand I found :)

Best regards,
Vincent

Le lun. 4 nov. 2019 à 18:23, Shockley, Timothy
 a écrit :


Helllo,



I am looking for some help with meta-java, specifically upgrading to zeus 
branch and also upgrading openjdk to a more recent release in order to address 
CVEs. Wondering if there is anyone else working / needing this?



Thanks,

Tim Shockley



--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Reminder: Yocto Project Technical Team Meeting @ Monthly from 8am to 8:30am on Tuesday (PDT)

2019-11-05 Thread Stephen K Jolley

All,



Just a reminder we will hold the monthly Yocto Project Technical Meeting at
8am PST. (11/5)



Yocto Project Technical Team Meeting: We encourage people attending the
meeting to logon and announce themselves on the Yocto Project IRC chancel
during the meeting (optional):

Yocto IRC: http://webchat.freenode.net/?channels=#yocto



Wiki: https://www.yoctoproject.org/public-virtual-meetings/



WhenMonthly from 8am to 8:30am on Tuesday Pacific Time

Where   Zoom Meeting: https://zoom.us/j/990892712



I will be tracking the minutes at:
https://docs.google.com/document/d/1Y5IIuE-z0Ykdl-DwuzUJh52flOZuhN_TSAfw2tdU9pg/edit?ts=5c06b22d
Please request access if you want to assist in editing them.  The world
should have view access.

--

Thanks,



*Stephen K. Jolley*

*Yocto Project Program Manager*

*7867 SW Bayberry Dr., Beaverton, OR 97007*

(*Cell*:(208) 244-4460

* *Email*: *s
jolley.yp...@gmail.com *
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] help with meta-java

2019-11-05 Thread Ross Burton


On 05/11/2019 08:18, Vincent Prince wrote:

Main layer maintainers:
   Henning Heinold 
   Maxin John 
   Otavio Salvador 
   Richard Leitner 


Maxin no longer works at Intel and I believe doesn't work on Yocto 
anymore either.


Ross
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-security][PATCH] cryptsetup tpm incubator: fix installed vs shipped

2019-11-05 Thread Christophe PRIOUZEAU

Fix [installed-vs-shipped] by adding /usr/lib/tmpfiles.d
on FILES.

Signed-off-by: Christophe Priouzeau 
---
 .../cryptsetup-tpm-incubator/cryptsetup-tpm-incubator_0.9.9.bb   | 1 +
 1 file changed, 1 insertion(+)

diff --git 
a/meta-tpm/recipes-tpm2/cryptsetup-tpm-incubator/cryptsetup-tpm-incubator_0.9.9.bb
 
b/meta-tpm/recipes-tpm2/cryptsetup-tpm-incubator/cryptsetup-tpm-incubator_0.9.9.bb
index 8385c94..b706d15 100644
--- 
a/meta-tpm/recipes-tpm2/cryptsetup-tpm-incubator/cryptsetup-tpm-incubator_0.9.9.bb
+++ 
b/meta-tpm/recipes-tpm2/cryptsetup-tpm-incubator/cryptsetup-tpm-incubator_0.9.9.bb
@@ -32,6 +32,7 @@ RRECOMMENDS_${PN} = "kernel-module-aes-generic \
  kernel-module-xts \
 "
 
+FILES_${PN} += "${libdir}/tmpfiles.d"
 RDEPENDS_${PN} += "lvm2 libdevmapper"
 RRECOMMENDS_${PN} += "lvm2-udevrules"
 
-- 
2.17.1
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] bitbake SRC_URI fetch Azure DevOps repository Azure DevOps Services Basic

2019-11-05 Thread Mark Hatle

When cloning a repository using the builtin fetcher that is git based, the
default protocol is 'git'.

If you want to use an alternative protocol, such as http or ssh, you must
specify the protocol to use.

In your example below, you have specified http:

SRC_URI = "git://git.oe.handhelds.org/git/vip.git;protocol=http"

Change the http to 'ssh' to switch to that protocol.  Note, for the fetcher the
system MUST be able to automatically login without user interaction.  This means
that you must have authorized keys enabled.

Note, ssh is not suggested as a protocol -- except for internal private
development -- because you can't easily share you recipes with others.  Many
corporations block ssh, and will only allow http via a proxy.

--Mark

On 11/3/19 8:52 PM, Samuel Jiang (江騏先) wrote:
> Dear yocto developer,
> The below disscussed about azure devops clone issue including test result with
> Microsoft support team member.
> We wonder know how Bitbake access repository through SSH. Does it different
> between git and Azue DevOps?
> 
> Thanks,
> 
> Samuel Jiang
> -- Forwarded message --
> *From:* Alex Chong (Shanghai Wicresoft Co,.Ltd.) 
> *Date:* 2019年10月31日 PM5:39 [+0800]
> *To:* Samuel Jiang (江騏先) 
> *Cc:* support , Alex Chong (Shanghai
> Wicresoft Co,.Ltd.) 
> *Subject:* RE: 119102923000220 use yocto bitbake SRC_URI fetch Azure DevOps
> repository Azure DevOps Services Basic
> 
>> Hi Samuel,
>>
>>  
>>
>> Thank you for reply.
>>
>>  
>>
>> I test and read the BitBake doc, let me share with you my finding and 
>> analysis.
>>
>>  1. I have verified that our Azure DevOps Organization Repo could be clone
>> through SSH authentication successfully. 
>>
>>  1. I create a new SSH key and add it to Azure DevOps SSH public keys. 
>>
>>  2. Then I use git clone command and clone this repo successfully. The url is
>> 
>> “v-chucho-micros...@vs-ssh.visualstudio.com:v3/v-chucho-microsoft/testCodeCoverage/testCodeCoverage”
>>
>>
>> My testing verify that SSH Authentication is available, and the url given by
>> Azure DevOps is correct.
>>
>>  
>>
>>  2. Then I also test it in GitHub, and succeed. The only difference is the 
>> url
>> of GitHub is “g...@github.com:xx.git” 
>>
>>  
>>
>>  3. So let’s come back to BitBake. I read more of the BitBake doc.(
>> 
>> https://www.yoctoproject.org/docs/1.8/bitbake-user-manual/bitbake-user-manual.html#bb-fetchers)
>> . Your command SRC_URI =
>> 
>> "git://quant...@vs-ssh.visualstudio.com:v3/quanta01/OpenBMC/crashdump;protocol=ssh;nobranch=1".
>> The BitBake example is below. 
>>
>> We can see that the BitBake syntax is like git SSH but not Azure DevOps SSH.
>> Do you try to use this command clone a repo from GitHub?
>>
>>  
>>
>>  4. Then I read the doc you shared. The customer also met your issue when
>> trying to clone Azure DevOps repo with SSH url. In my understanding, 
>> seems
>> BitBake Git fetcher is good for Git SSH but not ready to access the Azure
>> DevOps SSH. 
>>
>>  
>>
>> *_Action Plan_*
>>
>> Could you involve BitBake support team? We can deliver this testing result 
>> and
>> consult them how BitBake access Azure DevOps through SSH.
>>
>>  
>>
>> If you have any conern or query, please feel free to let me know.
>>
>>  
>>
>> Best Regards,
>>
>>  
>>
>> Alex Chong
>>
>>  
>>
>> image001
>>
>> Support Engineer
>>
>> Microsoft APAC Developer Support Team
>>
>> Customer Service & Support (CSS)
>>
>> Email: v-chu...@microsoft.com 
>>
>> Office: +86 (21) 52638610
>>
>> Time zone: (UTC+08:00) Beijing, Chongqing, Hong Kong, Urumqi
>>
>> Working time: 9:00am-6:00pm, Mon-Tue-Wed-Thu-Fri
>>
>>  
>>
>> *From:* Samuel Jiang (江騏先) 
>> *Sent:* Thursday, October 31, 2019 12:16 PM
>> *To:* Alex Chong (Shanghai Wicresoft Co,.Ltd.) 
>> *Cc:* support 
>> *Subject:* RE: 119102923000220 use yocto bitbake SRC_URI fetch Azure DevOps
>> repository Azure DevOps Services Basic
>>
>>  
>>
>> Hi Alex,
>>
>> I catch same problem on the yocto mail list
>> link: https://lists.yoctoproject.org/pipermail/yocto/2018-October/042736.html
>> 
>>
>> when I use SRC_URI =
>> "git://quant...@vs-ssh.visualstudio.com:v3/quanta01/OpenBMC/crashdump;protocol=ssh;nobranch=1"
>>
>> the bitbake response below error message:
>> git -c core.fsyncobjectfiles=0 ls-remote
>> ssh://quant...@vs-ssh.visualstudio.com:v3/quanta01/OpenBMC/crashdump  failed
>> with exit code 128, output:
>>
>> ssh: Could not resolve hostname vs-ssh.visualstudio.com:v3: Name or service
>> not known
>>
>> fatal: Could not read from remote repository.
>>
>> I think the bitbake call “git ls-remote” command h

[yocto] [meta-selinux][PATCH] autorelabel: only selinux-autorelabel need autorelabel file

2019-11-05 Thread Christophe PRIOUZEAU

With previous implementation, several packages provided
 .autorelabel file while only selinux-autorelabel manage it.
If there is several packages which try to install .autorelabel
file, an issue occur during installation of packagegroup-core-selinux.

Signed-off-by: Christophe Priouzeau 
---
 recipes-security/selinux/selinux-autorelabel_0.1.bb | 9 +
 recipes-security/selinux/selinux-initsh.inc | 7 ---
 2 files changed, 9 insertions(+), 7 deletions(-)

diff --git a/recipes-security/selinux/selinux-autorelabel_0.1.bb 
b/recipes-security/selinux/selinux-autorelabel_0.1.bb
index 4eb2b4e..7e7d08c 100644
--- a/recipes-security/selinux/selinux-autorelabel_0.1.bb
+++ b/recipes-security/selinux/selinux-autorelabel_0.1.bb
@@ -18,3 +18,12 @@ SRC_URI = "file://${BPN}.sh \
 INITSCRIPT_PARAMS = "start 01 S ."
 
 require selinux-initsh.inc
+
+do_install_append() {
+   if ${@bb.utils.contains('DISTRO_FEATURES', 'systemd', 'true', 'false', 
d)}; then
+   install -d ${D}${bindir}
+   install -m 0755 ${WORKDIR}/${SELINUX_SCRIPT_SRC}.sh 
${D}${bindir}
+   sed -i -e '/.*HERE$/d' ${D}${bindir}/${SELINUX_SCRIPT_SRC}.sh
+   echo "# first boot relabelling" > ${D}/.autorelabel
+   fi
+}
diff --git a/recipes-security/selinux/selinux-initsh.inc 
b/recipes-security/selinux/selinux-initsh.inc
index 8e31cda..6084762 100644
--- a/recipes-security/selinux/selinux-initsh.inc
+++ b/recipes-security/selinux/selinux-initsh.inc
@@ -29,13 +29,6 @@ do_install () {
 
install -d ${D}${systemd_unitdir}/system
install -m 0644 ${WORKDIR}/${SELINUX_SCRIPT_SRC}.service 
${D}${systemd_unitdir}/system
-
-   if ${@bb.utils.contains('DISTRO_FEATURES', 'systemd', 'true', 'false', 
d)}; then
-   install -d ${D}${bindir}
-   install -m 0755 ${WORKDIR}/${SELINUX_SCRIPT_SRC}.sh 
${D}${bindir}
-   sed -i -e '/.*HERE$/d' ${D}${bindir}/${SELINUX_SCRIPT_SRC}.sh
-   echo "# first boot relabelling" > ${D}/.autorelabel
-   fi
 }
 
 sysroot_stage_all_append () {
-- 
2.17.1
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] bitbake SRC_URI fetch Azure DevOps repository Azure DevOps Services Basic

2019-11-05 Thread Richard Purdie

On Mon, 2019-11-04 at 02:52 +, Samuel Jiang (江騏先) wrote:
> Dear yocto developer,
> The below disscussed about azure devops clone issue including test
> result with Microsoft support team member.
> We wonder know how Bitbake access repository through SSH. Does it
> different between git and Azue DevOps?


Try:

SRC_URI = 
"git://quant...@vs-ssh.visualstudio.com/v3/quanta01/OpenBMC/crashdump;protocol=ssh;nobranch=1"

as I think you didn't convert the url to our syntax correctly.

Cheers,

Richard


> Thanks,
> 
> Samuel Jiang
> -- Forwarded message --
> From: Alex Chong (Shanghai Wicresoft Co,.Ltd.) <
> v-chu...@microsoft.com>
> Date: 2019年10月31日 PM5:39 [+0800]
> To: Samuel Jiang (江騏先) 
> Cc: support , Alex Chong
> (Shanghai Wicresoft Co,.Ltd.) 
> Subject: RE: 119102923000220 use yocto bitbake SRC_URI fetch Azure
> DevOps repository Azure DevOps Services Basic
> 
> > Hi Samuel,
> > 
> >  
> > 
> > Thank you for reply.
> > 
> >  
> > 
> > I test and read the BitBake doc, let me share with you my finding
> > and analysis.
> > 
> > I have verified that our Azure DevOps Organization Repo could be
> > clone through SSH authentication successfully.
> > I create a new SSH key and add it to Azure DevOps SSH public keys.
> >  
> > 
> > Then I use git clone command and clone this repo successfully. The
> > url is “v-chucho-micros...@vs-ssh.visualstudio.com:v3/v-chucho-
> > microsoft/testCodeCoverage/testCodeCoverage”
> > 
> > 
> > My testing verify that SSH Authentication is available, and the url
> > given by Azure DevOps is correct.
> > 
> >  
> > 
> > Then I also test it in GitHub, and succeed. The only difference is
> > the url of GitHub is “g...@github.com:xx.git”
> >  
> > 
> > So let’s come back to BitBake. I read more of the BitBake doc.( 
> > https://www.yoctoproject.org/docs/1.8/bitbake-user-manual/bitbake-user-manual.html#bb-fetchers
> > ) . Your command SRC_URI = "git://quanta01@vs-
> > ssh.visualstudio.com:v3/quanta01/OpenBMC/crashdump;protocol=ssh;nob
> > ranch=1". The BitBake example is below.
> > 
> > 
> > We can see that the BitBake syntax is like git SSH but not Azure
> > DevOps SSH. Do you try to use this command clone a repo from
> > GitHub?
> > 
> >  
> > 
> > Then I read the doc you shared. The customer also met your issue
> > when trying to clone Azure DevOps repo with SSH url. In my
> > understanding, seems BitBake Git fetcher is good for Git SSH but
> > not ready to access the Azure DevOps SSH.
> > 
> > 
> >  
> > 
> > Action Plan
> > 
> > Could you involve BitBake support team? We can deliver this testing
> > result and consult them how BitBake access Azure DevOps through
> > SSH.
> > 
> >  
> > 
> > If you have any conern or query, please feel free to let me know.
> > 
> >  
> > 
> > Best Regards,
> > 
> >  
> > 
> > Alex Chong
> > 
> >  
> > 
> > 
> > 
> > Support Engineer
> > 
> > Microsoft APAC Developer Support Team
> > 
> > Customer Service & Support (CSS)
> > 
> > Email: v-chu...@microsoft.com
> > 
> > Office: +86 (21) 52638610
> > 
> > Time zone: (UTC+08:00) Beijing, Chongqing, Hong Kong, Urumqi
> > 
> > Working time: 9:00am-6:00pm, Mon-Tue-Wed-Thu-Fri
> > 
> >  
> > 
> > From: Samuel Jiang (江騏先) 
> > Sent: Thursday, October 31, 2019 12:16 PM
> > To: Alex Chong (Shanghai Wicresoft Co,.Ltd.) <
> > v-chu...@microsoft.com>
> > Cc: support 
> > Subject: RE: 119102923000220 use yocto bitbake SRC_URI fetch Azure
> > DevOps repository Azure DevOps Services Basic
> > 
> >  
> > 
> > Hi Alex,
> > 
> > I catch same problem on the yocto mail list
> > link: 
> > https://lists.yoctoproject.org/pipermail/yocto/2018-October/042736.html
> > 
> > when I use SRC_URI = "git://quanta01@vs-
> > ssh.visualstudio.com:v3/quanta01/OpenBMC/crashdump;protocol=ssh;nob
> > ranch=1"
> > 
> > the bitbake response below error message:
> > git -c core.fsyncobjectfiles=0 ls-remote 
> > ssh://quant...@vs-ssh.visualstudio.com:v3/quanta01/OpenBMC/crashdump
> >   failed with exit code 128, output:
> > 
> > ssh: Could not resolve hostname vs-ssh.visualstudio.com:v3: Name or
> > service not known
> > 
> > fatal: Could not read from remote repository.
> > 
> > I think the bitbake call “git ls-remote” command however it could
> > not parser below host vs-ssh.visualstudio.com:v3
> > 
> > Could you help confirm the  “git ls-remote”command could work on
> > ssh method clone with ssh:// prefix?
> > 
> > BTW, the protocol will define the uri prefix, I didn’t find any way
> > removing this prefix.
> > 
> > Thanks,
> > Samuel Jiang
> > 
> >  
> > 
> > From: Alex Chong (Shanghai Wicresoft Co,.Ltd.) <
> > v-chu...@microsoft.com>
> > Sent: Thursday, October 31, 2019 10:32 AM
> > To: Samuel Jiang (江騏先) 
> > Cc: Alex Chong (Shanghai Wicresoft Co,.Ltd.) <
> > v-chu...@microsoft.com>; support <
> > supp...@mail.support.microsoft.com>
> > Subject: RE: 119102923000220 use yocto bitbake SRC_URI fetch Azure
> > DevOps repository Azure DevOps Services Basic
> > 
> >  
> > 
> > Hi Samuel,
> > 
> >  
> > 
> > H

[yocto] Yocto Project Status WW45’19

2019-11-05 Thread Stephen K Jolley

Current Dev Position: YP 3.1 M1

Next Deadline: YP 3.1 M1 build Dec. 2, 2019

SWAT Team Rotation:

   -

   SWAT lead is currently: Armin
   -

   SWAT team rotation: Armin-> Anuj on Nov. 8, 2019
   -

   SWAT team rotation: Anuj -> Chen on Nov. 15, 2019
   -

   https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team


Next Team Meetings:

   -

   Bug Triage meeting Thursday Nov. 7th at 7:30am PDT (
   https://zoom.us/j/454367603)
   -

   Monthly Project Meeting Tuesday Nov. 5th at 8am PDT (
   https://zoom.us/j/990892712) 
   -

   Weekly Engineering Sync Tuesday Nov. 12th at 8am PDT (
   https://zoom.us/j/990892712) 
   -

   Twitch - Next event is Tuesday Nov. 12th at 8am PDT (
   https://www.twitch.tv/yocto_project)


Key Status/Updates:

   -

   The project presence at ELC-E in Lyon was strong, thanks to everyone who
   contributed, be it through presentations, helping with the booth, visiting
   the booth or attending or assisting with the summit!
   -

   YP 2.6.4 was released
   -

   Patches have continued to merge and master is staying roughly current
   with the pending patch queue. The autobuilder is still suffering a number
   of intermittent failures which will start to hamper future development.
   We’re likely going to have to pause and address those before other
   development can continue.
   -

   In particular, issues with pseudo on fedora30 have become apparent due
   to its use of the new statx() syscall.
   -

   YP 2.7.2 has been built and is now in QA
   -

   The YP TSC worked on and shared a proposal on how an LTS release could
   work which is available at:
   
https://docs.google.com/document/d/1AwAFDf52f_FoXksbHEVUMlu4hpcI0JMGVG-Kj_sUkyc/
   -

   We are continuing to collect ideas for YP 3.1 in this document:
   
https://docs.google.com/document/d/1UKZIGe88-eq3-pOPtkAvFAegbQDzhy_f4ye64yjnABc/edit?usp=sharing
   -

   If anyone has any status items for the project they’d like to add to the
   weekly reports, please email Richard and Stephen.


Proposed YP 3.1 Milestone Dates:

   -

   YP 3.1 M1 Proposed build date 12/2/2019
   -

   YP 3.1 M1 Proposed release date 12/13/2019
   -

   YP 3.1 M2 Proposed build date 1/20/2020
   -

   YP 3.1 M2 Proposed release date 1/31/2020
   -

   YP 3.1 M3 Proposed build date 2/24/2020
   -

   YP 3.1 M3 Proposed release date 3/6/2020
   -

   YP 3.1 M4 Proposed build date  3/30/2020
   -

   YP 3.1 M4 Proposed release date  4/24/2020


Planned upcoming dot releases:

   -

   YP 3.0.1 has patches being queued in poky-contrib
   -

   YP 2.7.2 (Warrior) is in QA.
   -

   YP 2.6.4 (Thud) was released.


Tracking Metrics:

   -

   WDD 2518 (last week 2493) (
   https://wiki.yoctoproject.org/charts/combo.html)
   -

   Poky Patch Metrics
   -

  Total patches found: 1446 (last week 1441)
  -

  Patches in the Pending State: 579 (40%) [last week 579 (40%)]


The Yocto Project’s technical governance is through its Technical Steering
Committee, more information is available at:

https://wiki.yoctoproject.org/wiki/TSC

The Status reports are now stored on the wiki at:
https://wiki.yoctoproject.org/wiki/Weekly_Status

[If anyone has suggestions for other information you’d like to see on this
weekly status update, let us know!]

Thanks,



*Stephen K. Jolley*

*Yocto Project Program Manager*

*7867 SW Bayberry Dr., Beaverton, OR 97007*

(*Cell*:(208) 244-4460

* *Email*: *s
jolley.yp...@gmail.com *
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] help with meta-java

Re: [yocto] help with meta-java

[yocto] Reminder: Yocto Project Technical Team Meeting @ Monthly from 8am to 8:30am on Tuesday (PDT)

Re: [yocto] help with meta-java

[yocto] [meta-security][PATCH] cryptsetup tpm incubator: fix installed vs shipped

Re: [yocto] bitbake SRC_URI fetch Azure DevOps repository Azure DevOps Services Basic

[yocto] [meta-selinux][PATCH] autorelabel: only selinux-autorelabel need autorelabel file

Re: [yocto] bitbake SRC_URI fetch Azure DevOps repository Azure DevOps Services Basic

[yocto] Yocto Project Status WW45’19

9 matches

Site Navigation

Mail list logo

Footer information