Date   

Re: Mirroring meta-kernel on git.yoctoproject.org

 

On Wed, 5 Aug 2020 at 14:09, Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:

On Mon, 2020-08-03 at 09:56 +0100, Paul Barker wrote:
I'd like to get the meta-kernel layer mirrored on
git.yoctoproject.org
so that we've got a backup available in case of any issues with
GitLab. This has been requested by one of our users
(https://gitlab.com/openembedded/community/meta-kernel/-/issues/11).
I
also think it's important now that meta-arm-bsp and a few other
layers
depend on meta-kernel.

I can enable an automatic push from GitLab whenever the repository is
updated so all we would need on git.yoctoproject.org is a meta-kernel
repository and push access from the relevant SSH keys.
I've had to think carefully about this and I think we can only say no.

The reason is the namespacing. This is taking a special namespace and
its doing it by stealth, not a conscious decision. If we do this, its
going to create confusion for users and also create friction with other
Yocto Project components.

This was warned about when "meta-kernel" was started and now its coming
back to bite us :(.

I suspect this is something which will you'll want to appeal against
and I should therefore refer it to the YP TSC?
If there was any comment about the layer naming I don't think it got
to me. The only feedback I saw was that yocto-announce could not be
used to announce releases as it's not the product of a Yocto Project
member organisation.

I don't think appealing and trying to force the decision is the way to
go. We should look for some consensus on how to fit this into the
Yocto ecosystem going forward even if that involves renaming things or
doing something else. I'll raise this on the next weekly call.

Thanks,

--
Paul Barker
Konsulko Group


Re: Mirroring meta-kernel on git.yoctoproject.org

Richard Purdie
 

On Mon, 2020-08-03 at 09:56 +0100, Paul Barker wrote:
I'd like to get the meta-kernel layer mirrored on
git.yoctoproject.org
so that we've got a backup available in case of any issues with
GitLab. This has been requested by one of our users
(https://gitlab.com/openembedded/community/meta-kernel/-/issues/11).
I
also think it's important now that meta-arm-bsp and a few other
layers
depend on meta-kernel.

I can enable an automatic push from GitLab whenever the repository is
updated so all we would need on git.yoctoproject.org is a meta-kernel
repository and push access from the relevant SSH keys.
I've had to think carefully about this and I think we can only say no.

The reason is the namespacing. This is taking a special namespace and
its doing it by stealth, not a conscious decision. If we do this, its
going to create confusion for users and also create friction with other
Yocto Project components.

This was warned about when "meta-kernel" was started and now its coming
back to bite us :(.

I suspect this is something which will you'll want to appeal against
and I should therefore refer it to the YP TSC?

Cheers,

Richard


[PATCH] yocto-bsps: update reference BSPs to 5.4.54

Bruce Ashfield
 

From: Bruce Ashfield <bruce.ashfield@gmail.com>

Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
---

This also picks up the binutils fix.

Bruce

.../linux/linux-yocto_5.4.bbappend | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.4.bbappend b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.4.bbappend
index 626748541a..2c73eb2f67 100644
--- a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.4.bbappend
+++ b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_5.4.bbappend
@@ -7,17 +7,17 @@ KMACHINE_genericx86 ?= "common-pc"
KMACHINE_genericx86-64 ?= "common-pc-64"
KMACHINE_beaglebone-yocto ?= "beaglebone"

-SRCREV_machine_genericx86 ?= "ec485bd4afef57715eb45ba331b04b3f941e43bb"
-SRCREV_machine_genericx86-64 ?= "ec485bd4afef57715eb45ba331b04b3f941e43bb"
-SRCREV_machine_edgerouter ?= "ec485bd4afef57715eb45ba331b04b3f941e43bb"
-SRCREV_machine_beaglebone-yocto ?= "ec485bd4afef57715eb45ba331b04b3f941e43bb"
+SRCREV_machine_genericx86 ?= "9fc2fb2e73466a520ee9a3c48b3ca2f5b21415dc"
+SRCREV_machine_genericx86-64 ?= "9fc2fb2e73466a520ee9a3c48b3ca2f5b21415dc"
+SRCREV_machine_edgerouter ?= "9fc2fb2e73466a520ee9a3c48b3ca2f5b21415dc"
+SRCREV_machine_beaglebone-yocto ?= "9fc2fb2e73466a520ee9a3c48b3ca2f5b21415dc"

COMPATIBLE_MACHINE_genericx86 = "genericx86"
COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64"
COMPATIBLE_MACHINE_edgerouter = "edgerouter"
COMPATIBLE_MACHINE_beaglebone-yocto = "beaglebone-yocto"

-LINUX_VERSION_genericx86 = "5.4.49"
-LINUX_VERSION_genericx86-64 = "5.4.49"
-LINUX_VERSION_edgerouter = "5.4.49"
-LINUX_VERSION_beaglebone-yocto = "5.4.49"
+LINUX_VERSION_genericx86 = "5.4.54"
+LINUX_VERSION_genericx86-64 = "5.4.54"
+LINUX_VERSION_edgerouter = "5.4.54"
+LINUX_VERSION_beaglebone-yocto = "5.4.54"
--
2.19.1


Re: when is it appropriate to push recipe enhancements (eg., class-nativesdk) upstream?

Ross Burton
 

For simple things like adding native/nativesdk then pushing them
upstream is easy and simple. I'm trying to avoid commenting on that
specific bbappend...

Ross

On Wed, 5 Aug 2020 at 12:14, Robert P. J. Day <rpjday@crashcourse.ca> wrote:

based on recipe from an existing (zeus-based) project, colleague asks
about a bbappend file, and whether it's appropriate that it be submitted
upstream as a patch -- this example involves "pciutils" recipe from
oe-core, but the question more generally covers any number of recipes.

this particular code base has the following pciutils_%.bbappend file:

=== start ===
PACKAGECONFIG_class-nativesdk = ""

DISABLE_STATIC_pn-nativesdk-pciutils = ""

# Need nativesdk-specific do_install due to ${sbindir} being set to usr/bin
do_install_class-nativesdk () {
oe_runmake DESTDIR=${D} install install-lib

oe_multilib_header pci/config.h
}

BBCLASSEXTEND += "nativesdk"
=== end ===

i'm looking at this for the first time and, sure, it appears to
extend the pciutils recipe for nativesdk. but if that's true, then
would it not make sense to submit that as a patch?

the current zeus "pciutils_3.6.2.bb" recipe doesn't extend the
recipe for nativesdk, so if this bbappend file actually correctly
does that, would it not make sense to contribute that enhancement
back?

in general, there appear to be numerous recipes in this code base
that do little more than extend the recipe for native and nativesdk
because the oe-core (or meta-oe) recipes don't do that.

am i thinking about this correctly? it seems that, if local bbappend
content fixes or enhances a recipe, it would make sense to push that
fix so as to not have to carry around the bbappend files.

thoughts? i'm not passing any judgment on the correctness of this
particular bbappend file, i'm more interested in the general
philosophy of pushing improvements to not have to keep carrying
them around in the local code base.

rday



when is it appropriate to push recipe enhancements (eg., class-nativesdk) upstream?

Robert P. J. Day
 

based on recipe from an existing (zeus-based) project, colleague asks
about a bbappend file, and whether it's appropriate that it be submitted
upstream as a patch -- this example involves "pciutils" recipe from
oe-core, but the question more generally covers any number of recipes.

this particular code base has the following pciutils_%.bbappend file:

=== start ===
PACKAGECONFIG_class-nativesdk = ""

DISABLE_STATIC_pn-nativesdk-pciutils = ""

# Need nativesdk-specific do_install due to ${sbindir} being set to usr/bin
do_install_class-nativesdk () {
oe_runmake DESTDIR=${D} install install-lib

oe_multilib_header pci/config.h
}

BBCLASSEXTEND += "nativesdk"
=== end ===

i'm looking at this for the first time and, sure, it appears to
extend the pciutils recipe for nativesdk. but if that's true, then
would it not make sense to submit that as a patch?

the current zeus "pciutils_3.6.2.bb" recipe doesn't extend the
recipe for nativesdk, so if this bbappend file actually correctly
does that, would it not make sense to contribute that enhancement
back?

in general, there appear to be numerous recipes in this code base
that do little more than extend the recipe for native and nativesdk
because the oe-core (or meta-oe) recipes don't do that.

am i thinking about this correctly? it seems that, if local bbappend
content fixes or enhances a recipe, it would make sense to push that
fix so as to not have to carry around the bbappend files.

thoughts? i'm not passing any judgment on the correctness of this
particular bbappend file, i'm more interested in the general
philosophy of pushing improvements to not have to keep carrying
them around in the local code base.

rday


Re: Yocto host not found

Richard Purdie
 

On Tue, 2020-08-04 at 14:10 -0700, Rick Liu via lists.yoctoproject.org
wrote:
Does http://downloads.yoctoproject.org/ have HA or hot-backup
machine?
Is there an instruction on how to create a
http://downloads.yoctoproject.org/ local mirror and sync?
The standard DL_DIR should be enough for normal builds to work, based
on Scott's questions, it sounds like there is some issue somewhere
which would be worth looking into. I don't see that issue locally or on
the autobuilder infrastructure so its hard for me to say what is wrong.

Regarding HA or hot-backup, our resilience places are supposed to be
that:

a) DL_DIR should allow existing builds to work
b) kernel.org has a partial mirror of the key components
c) we just have to accept the autobuilder would be unavailable in the
case of NAS failure until its repaired

It sounds like something isn't working quite right for a) to be having
an issue.

We'd love to have more server infrastructure and have things like hot
backup machines. Our budgets and infrastructure allow us to have what
we have. I'd note that broadcom were once a silver member but dropped
project membership, sadly :(. We do the best we can with what we have.

Cheers,

Richard


Re: Is http://downloads.yoctoproject.org/ down?

Richard Purdie
 

On Tue, 2020-08-04 at 14:36 -0700, Scott Branden via
lists.yoctoproject.org wrote:
With downloads.yoctoproject.org down again this begs the question:

Why does uninative tarball get fetched by default from the internet
every time?
Why is it in not cached like every other tarball that is downloaded
by recipes?
The default behaviour for the yocto project should be to have the
tarball stored in the yocto cache such that it is not fetched every
time?
Those are good questions.

As far as I know on my own local builds, the uninative tarball *is*
cached locally in DL_DIR. We don't see repeated downloads on the
autobuilder either so it appears to work there too.

If you're not seeing that it would definitely be something to
investigate.

Cheers,

Richard


psplash and mountpoint -q

Mauro Ziliani
 

Hi all.

I'm working woth Zeus on intel platform

When the script is run in shutdown I get the error at line 28

26: export TMPDIR=/mnt/.psplash
27: [ -d $TMPDIR ] || mkdir -p $TMPDIR
28: if [ ! mountpoint -q $TMPDIR ]; then
29:     mount tmpfs -t tmpfs $TMPDIR -o,size=40k
30: fi

So I change the line so

28: if [ ! `mountpoint -q $TMPDIR` ]; then


Is this ok?


MZ


Re: #yocto #sdk running esdk as crops with local esdk-installer #yocto #sdk

valentin.duee@...
 

No ideas?


Re: Yocto host not found

Michael Halstead
 


On Tue, Aug 4, 2020 at 2:10 PM Rick Liu <rick.liu@...> wrote:
Does http://downloads.yoctoproject.org/ have HA or hot-backup machine?

No. Many important files are mirrored at http://mirrors.kernel.org/yocto/ though.
 
Is there an instruction on how to create a  http://downloads.yoctoproject.org/  local mirror and sync?

Some larger users keep local mirrors. The full archive is almost 20TB so they usually only mirror parts of it. Please email me directly if you are interested.
 

Rick

On Tue, Aug 4, 2020 at 11:16 AM FLoraVLogs <eripflo@...> wrote:
Ok, thanks for the update. Kindly keep me posted. 

On Tue., Aug. 4, 2020, 2:05 p.m. Michael Halstead, <mhalstead@...> wrote:
Remote troubleshooting has stalled. I'm headed to the data center to continue. No ETA yet.

On Tue, Aug 4, 2020 at 9:02 AM FLoraVLogs <eripflo@...> wrote:
Is there any ETA on this?

Regards,

Ripu

On Tue, Aug 4, 2020 at 11:30 AM Josef Holzmayr-Khosh Amoz <jester@...> wrote:
https://twitter.com/TheYoctoJester/status/1290569609100308480

Am Di., 4. Aug. 2020 um 15:17 Uhr schrieb FLoraVLogs <eripflo@...>:
>
> I am seeing the following error:
>
> Gateway Timeout
>
> Server error - server 198.145.29.63 is unreachable at this moment.
>
> Please retry the request or contact your administrator.
>
>
> Kindly help.
>
>
> Regards,
>
>
> Ripu
>
>
> On Tue, Aug 4, 2020 at 9:14 AM FLoraVLogs <eripflo@...> wrote:
>>
>> Hi,
>>
>> It seems like Yocto is down again.
>>
>> http://downloads.yoctoproject.org/
>>
>> Could you please help solve this?
>>
>> Regards,
>>
>> Ripu
>>
>> On Thu, Jan 9, 2020 at 4:50 PM FLoraVLogs <eripflo@...> wrote:
>>>
>>> It is working now.
>>>
>>> Thank you
>>>
>>> Regards,
>>>
>>> Ripu
>>>
>>> On Thu., Jan. 9, 2020, 4:44 p.m. Michael Halstead, <mhalstead@...> wrote:
>>>>
>>>> There was a brief outage while rebooting a storage device. The error should have been resolved several minutes ago. If you are still seeing this error please let me know.
>>>>
>>>> Michael Halstead
>>>>
>>>> On Thu, Jan 9, 2020 at 1:38 PM FLoraVLogs <eripflo@...> wrote:
>>>>>
>>>>> Also, I do see:
>>>>>
>>>>> Connecting to downloads.yoctoproject.org (downloads.yoctoproject.org)|198.145.29.63|:80... failed: Connection refused.
>>>>>
>>>>>
>>>>> On Thu, Jan 9, 2020 at 3:37 PM FLoraVLogs <eripflo@...> wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I tried to go into the following:
>>>>>> http://downloads.yoctoproject.org/
>>>>>>
>>>>>> I get the following error:
>>>>>>
>>>>>>
>>>>>> Host Not Found
>>>>>>
>>>>>> DNS error (the host name of the page you are looking for does not exist) or Server did not accept the connection.
>>>>>>
>>>>>> Please check that the host name has been spelled correctly.
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Ripu
>>>>>
>>>>>
>



--
Michael Halstead
Linux Foundation / Yocto Project
Systems Operations Engineer



--
Michael Halstead
Linux Foundation / Yocto Project
Systems Operations Engineer


Re: Yocto host not found

Rick Liu
 

Does http://downloads.yoctoproject.org/ have HA or hot-backup machine?
Is there an instruction on how to create a  http://downloads.yoctoproject.org/  local mirror and sync?

Rick

On Tue, Aug 4, 2020 at 11:16 AM FLoraVLogs <eripflo@...> wrote:
Ok, thanks for the update. Kindly keep me posted. 

On Tue., Aug. 4, 2020, 2:05 p.m. Michael Halstead, <mhalstead@...> wrote:
Remote troubleshooting has stalled. I'm headed to the data center to continue. No ETA yet.

On Tue, Aug 4, 2020 at 9:02 AM FLoraVLogs <eripflo@...> wrote:
Is there any ETA on this?

Regards,

Ripu

On Tue, Aug 4, 2020 at 11:30 AM Josef Holzmayr-Khosh Amoz <jester@...> wrote:
https://twitter.com/TheYoctoJester/status/1290569609100308480

Am Di., 4. Aug. 2020 um 15:17 Uhr schrieb FLoraVLogs <eripflo@...>:
>
> I am seeing the following error:
>
> Gateway Timeout
>
> Server error - server 198.145.29.63 is unreachable at this moment.
>
> Please retry the request or contact your administrator.
>
>
> Kindly help.
>
>
> Regards,
>
>
> Ripu
>
>
> On Tue, Aug 4, 2020 at 9:14 AM FLoraVLogs <eripflo@...> wrote:
>>
>> Hi,
>>
>> It seems like Yocto is down again.
>>
>> http://downloads.yoctoproject.org/
>>
>> Could you please help solve this?
>>
>> Regards,
>>
>> Ripu
>>
>> On Thu, Jan 9, 2020 at 4:50 PM FLoraVLogs <eripflo@...> wrote:
>>>
>>> It is working now.
>>>
>>> Thank you
>>>
>>> Regards,
>>>
>>> Ripu
>>>
>>> On Thu., Jan. 9, 2020, 4:44 p.m. Michael Halstead, <mhalstead@...> wrote:
>>>>
>>>> There was a brief outage while rebooting a storage device. The error should have been resolved several minutes ago. If you are still seeing this error please let me know.
>>>>
>>>> Michael Halstead
>>>>
>>>> On Thu, Jan 9, 2020 at 1:38 PM FLoraVLogs <eripflo@...> wrote:
>>>>>
>>>>> Also, I do see:
>>>>>
>>>>> Connecting to downloads.yoctoproject.org (downloads.yoctoproject.org)|198.145.29.63|:80... failed: Connection refused.
>>>>>
>>>>>
>>>>> On Thu, Jan 9, 2020 at 3:37 PM FLoraVLogs <eripflo@...> wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I tried to go into the following:
>>>>>> http://downloads.yoctoproject.org/
>>>>>>
>>>>>> I get the following error:
>>>>>>
>>>>>>
>>>>>> Host Not Found
>>>>>>
>>>>>> DNS error (the host name of the page you are looking for does not exist) or Server did not accept the connection.
>>>>>>
>>>>>> Please check that the host name has been spelled correctly.
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Ripu
>>>>>
>>>>>
>



--
Michael Halstead
Linux Foundation / Yocto Project
Systems Operations Engineer


Re: Is http://downloads.yoctoproject.org/ down?

Scott Branden <scott.branden@...>
 

With downloads.yoctoproject.org down again this begs the question:

Why does uninative tarball get fetched by default from the internet every time?
Why is it in not cached like every other tarball that is downloaded by recipes?
The default behaviour for the yocto project should be to have the tarball stored in the yocto cache such that it is not fetched every time?


Re: Yocto build failure -- supposedly due to opkg-4.2 download

Armin Kuster
 



On 8/4/20 12:00 PM, Alex G. wrote:
Hi,

I'm trying to get started with yocto builds. My builds keep failing trying to build the qemu-x86 image.

If I am not mistaken, many of the servers are down including downloads.yoctoproject.org.

-armin

Here's what I did:

1. I got poky from git://git.yoctoproject.org/poky.git -b dunfell
2. $ source path/to/poky/oe-init-build-env
3. $ time bitbake core-image-minimal

I keep getting the following error:

ERROR: opkg-1_0.4.2-r0 do_fetch: Fetcher failure for URL: 'http://downloads.yoctoproject.org/releases/opkg/opkg-0.4.2.tar.gz'. Unable to fetch URL from any source.

The file doesn't seem to be present on the server. I'm stuck. How do I fix this?

Alex


    


Yocto build failure -- supposedly due to opkg-4.2 download

Alex G.
 

Hi,

I'm trying to get started with yocto builds. My builds keep failing trying to build the qemu-x86 image.

Here's what I did:

1. I got poky from git://git.yoctoproject.org/poky.git -b dunfell
2. $ source path/to/poky/oe-init-build-env
3. $ time bitbake core-image-minimal

I keep getting the following error:

ERROR: opkg-1_0.4.2-r0 do_fetch: Fetcher failure for URL: 'http://downloads.yoctoproject.org/releases/opkg/opkg-0.4.2.tar.gz'. Unable to fetch URL from any source.

The file doesn't seem to be present on the server. I'm stuck. How do I fix this?

Alex


Re: Yocto host not found

FLoraVLogs <eripflo@...>
 

Ok, thanks for the update. Kindly keep me posted. 


On Tue., Aug. 4, 2020, 2:05 p.m. Michael Halstead, <mhalstead@...> wrote:
Remote troubleshooting has stalled. I'm headed to the data center to continue. No ETA yet.

On Tue, Aug 4, 2020 at 9:02 AM FLoraVLogs <eripflo@...> wrote:
Is there any ETA on this?

Regards,

Ripu

On Tue, Aug 4, 2020 at 11:30 AM Josef Holzmayr-Khosh Amoz <jester@...> wrote:
https://twitter.com/TheYoctoJester/status/1290569609100308480

Am Di., 4. Aug. 2020 um 15:17 Uhr schrieb FLoraVLogs <eripflo@...>:
>
> I am seeing the following error:
>
> Gateway Timeout
>
> Server error - server 198.145.29.63 is unreachable at this moment.
>
> Please retry the request or contact your administrator.
>
>
> Kindly help.
>
>
> Regards,
>
>
> Ripu
>
>
> On Tue, Aug 4, 2020 at 9:14 AM FLoraVLogs <eripflo@...> wrote:
>>
>> Hi,
>>
>> It seems like Yocto is down again.
>>
>> http://downloads.yoctoproject.org/
>>
>> Could you please help solve this?
>>
>> Regards,
>>
>> Ripu
>>
>> On Thu, Jan 9, 2020 at 4:50 PM FLoraVLogs <eripflo@...> wrote:
>>>
>>> It is working now.
>>>
>>> Thank you
>>>
>>> Regards,
>>>
>>> Ripu
>>>
>>> On Thu., Jan. 9, 2020, 4:44 p.m. Michael Halstead, <mhalstead@...> wrote:
>>>>
>>>> There was a brief outage while rebooting a storage device. The error should have been resolved several minutes ago. If you are still seeing this error please let me know.
>>>>
>>>> Michael Halstead
>>>>
>>>> On Thu, Jan 9, 2020 at 1:38 PM FLoraVLogs <eripflo@...> wrote:
>>>>>
>>>>> Also, I do see:
>>>>>
>>>>> Connecting to downloads.yoctoproject.org (downloads.yoctoproject.org)|198.145.29.63|:80... failed: Connection refused.
>>>>>
>>>>>
>>>>> On Thu, Jan 9, 2020 at 3:37 PM FLoraVLogs <eripflo@...> wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I tried to go into the following:
>>>>>> http://downloads.yoctoproject.org/
>>>>>>
>>>>>> I get the following error:
>>>>>>
>>>>>>
>>>>>> Host Not Found
>>>>>>
>>>>>> DNS error (the host name of the page you are looking for does not exist) or Server did not accept the connection.
>>>>>>
>>>>>> Please check that the host name has been spelled correctly.
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Ripu
>>>>>
>>>>>
>



--
Michael Halstead
Linux Foundation / Yocto Project
Systems Operations Engineer


Re: cannot bring global environment var into a recipe

Rob Prowel <rprowel@...>
 

On 2020-08-04 13:11, codusnocturnus via lists.yoctoproject.org wrote:
I think what you need to do is add the environment variable to BB_ENV_WHITELIST or BB_ENV_EXTRAWHITE:
https://www.yoctoproject.org/docs/1.6/bitbake-user-manual/bitbake-user-manual.html#var-BB_ENV_WHITELIST
Thanks,
Thanks, NightCoder! It worked, once I put it in the right place.

must be declared in global shell environment after running oe-init-build-environment

export BB_ENV_EXTRAWHITELIST="${BB_ENV_EXTRAWHITELIST} VAR_TO_BRING IN"

Unfortunately it's not always obvious to me where a variable is to be declared: some in global shell, sometimes in local.conf, sometimes in bb files...

Anyway, fixed! Thanks!


Re: Yocto host not found

Michael Halstead
 

Remote troubleshooting has stalled. I'm headed to the data center to continue. No ETA yet.


On Tue, Aug 4, 2020 at 9:02 AM FLoraVLogs <eripflo@...> wrote:
Is there any ETA on this?

Regards,

Ripu

On Tue, Aug 4, 2020 at 11:30 AM Josef Holzmayr-Khosh Amoz <jester@...> wrote:
https://twitter.com/TheYoctoJester/status/1290569609100308480

Am Di., 4. Aug. 2020 um 15:17 Uhr schrieb FLoraVLogs <eripflo@...>:
>
> I am seeing the following error:
>
> Gateway Timeout
>
> Server error - server 198.145.29.63 is unreachable at this moment.
>
> Please retry the request or contact your administrator.
>
>
> Kindly help.
>
>
> Regards,
>
>
> Ripu
>
>
> On Tue, Aug 4, 2020 at 9:14 AM FLoraVLogs <eripflo@...> wrote:
>>
>> Hi,
>>
>> It seems like Yocto is down again.
>>
>> http://downloads.yoctoproject.org/
>>
>> Could you please help solve this?
>>
>> Regards,
>>
>> Ripu
>>
>> On Thu, Jan 9, 2020 at 4:50 PM FLoraVLogs <eripflo@...> wrote:
>>>
>>> It is working now.
>>>
>>> Thank you
>>>
>>> Regards,
>>>
>>> Ripu
>>>
>>> On Thu., Jan. 9, 2020, 4:44 p.m. Michael Halstead, <mhalstead@...> wrote:
>>>>
>>>> There was a brief outage while rebooting a storage device. The error should have been resolved several minutes ago. If you are still seeing this error please let me know.
>>>>
>>>> Michael Halstead
>>>>
>>>> On Thu, Jan 9, 2020 at 1:38 PM FLoraVLogs <eripflo@...> wrote:
>>>>>
>>>>> Also, I do see:
>>>>>
>>>>> Connecting to downloads.yoctoproject.org (downloads.yoctoproject.org)|198.145.29.63|:80... failed: Connection refused.
>>>>>
>>>>>
>>>>> On Thu, Jan 9, 2020 at 3:37 PM FLoraVLogs <eripflo@...> wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I tried to go into the following:
>>>>>> http://downloads.yoctoproject.org/
>>>>>>
>>>>>> I get the following error:
>>>>>>
>>>>>>
>>>>>> Host Not Found
>>>>>>
>>>>>> DNS error (the host name of the page you are looking for does not exist) or Server did not accept the connection.
>>>>>>
>>>>>> Please check that the host name has been spelled correctly.
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Ripu
>>>>>
>>>>>
>



--
Michael Halstead
Linux Foundation / Yocto Project
Systems Operations Engineer


Re: cannot bring global environment var into a recipe

codusnocturnus
 

I think what you need to do is add the environment variable to BB_ENV_WHITELIST or BB_ENV_EXTRAWHITE:

https://www.yoctoproject.org/docs/1.6/bitbake-user-manual/bitbake-user-manual.html#var-BB_ENV_WHITELIST

Thanks,

Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

On Tuesday, August 4, 2020 9:54 AM, Rob Prowel <rprowel@comcast.net> wrote:

I don't want to get into a discussion about why it is a good or bad
idea, but I need to use a global shell variable as follows:

using "sumo"...that's all I can use.

$ export PM1_DEVEL_IMAGE=1

or

$ PM1_DEVEL_IMAGE=1 bitbake my-image

and reference that global var in a kernel bbappend such as

SRC_URI += "${@ 'file://rootnfs.cfg' if d.getVar('PM1_DEVEL_IMAGE') else
' '}"

to include the required fragment that supports rootnfs.

If I define the var right in the bbappend then it works as expected:
undefined skips the SRC_URI append, and if defined then it adds my
fragment. I need this to work for a var that is defined (or not) in the
global work shell, not depend upon the definition being IN a recipe file.

I tried using

export PM1_DEVEL_IMAGE

right in the bbappend, but then as far as the recipe is concerned it's
defined and the conditional always succeeds.

is d.getVar not the right function? What function behaves the same but
uses real shell variables?

Suggestions?


cannot bring global environment var into a recipe

Rob Prowel <rprowel@...>
 

I don't want to get into a discussion about why it is a good or bad idea, but I need to use a global shell variable as follows:

using "sumo"...that's all I can use.

$ export PM1_DEVEL_IMAGE=1

or

$ PM1_DEVEL_IMAGE=1 bitbake my-image


and reference that global var in a kernel bbappend such as


SRC_URI += "${@ 'file://rootnfs.cfg' if d.getVar('PM1_DEVEL_IMAGE') else ' '}"

to include the required fragment that supports rootnfs.

If I define the var right in the bbappend then it works as expected: undefined skips the SRC_URI append, and if defined then it adds my fragment. I need this to work for a var that is defined (or not) in the global work shell, not depend upon the definition being IN a recipe file.

I tried using

export PM1_DEVEL_IMAGE

right in the bbappend, but then as far as the recipe is concerned it's defined and the conditional always succeeds.


is d.getVar not the right function? What function behaves the same but uses real shell variables?


Suggestions?


Yocto Technical Team Minutes, Engineering Sync, for August 4 2020

Trevor Woerner
 

Yocto Technical Team Minutes, Engineering Sync, for August 4 2020
archive: https://docs.google.com/document/d/1ly8nyhO14kDNnFcW2QskANXW3ZT7QwKC5wWVDg9dDH4/edit

== disclaimer ==
Best efforts are made to ensure the below is accurate and valid. However,
errors sometimes happen. If any errors or omissions are found, please feel
free to reply to this email with any corrections.

== attendees ==
Trevor Woerner, Stephen Jolley, Armin Kuster, Richard Purdie, Josef
Holzmayr, Joshua Watt, Alejandro H, Steve Sakoman, Bruce Ashfield,
(phone-in), Jon Mason, Scott Murray, Denys Dmytriyenko, Matthew Zeng,
Philip Balister, Peter Kjellerstedt, Saul Wold, Tim Orling, Ross Burton

== notes ==
- 3.1.2 released
- 3.1-m2 in QA
- qemumips issues continue on AB
- published doc on inclusive language
- published doc on future directions
- intermittent AB failures, but seems to be going down
- lots of unassigned bugs, please pitch in
- 3.0.4 (last build of 3.0 series, zeus) probably built sometime next week (if
everything stays good)
- project tracking metrics are good, probably the best in roughly 18 months
- overall project appears healthy and growing

== general ==
RP: relatively quiet week
RP: binutils update caused perf issues, Bruce already submitted a patch
RP: infrastructure has issues today (some parts are down) Michael is aware

RP: inclusive language: agreed on by various groups in the project. please
join in.

RP: future directions is something we’ve been working on for a while, please
take a look

RP: i’ve been looking at the sphynx doc update (hi Nico!)
RP: Nico has been making great progress. i’d like to make improvements to
how doc versions are selected, looking into what sphynx can do for us. i
think Nico is about to publish a list of ways to contribute(?)

Timo: bug triage: we decided to create a new mailing list for AB failures. any
name suggestions?
RP: i think it wasn’t AB failures, but QA reports
SS: yes
RP: with AB1 we realised that what was being emailed out was wrong, with AB2
we never re-enabled/re-implemented it. the problem with an AB failures
list was that people started reporting general failures not happening on
AB. the idea was to shut down the build failures list and create a QA list
RP: we could create it, if there is demand, but i don’t think the demand is
there
Timo: i’d rather get an email than staring at the AB2 UI
RP: having that email sounds great, but we don’t have the code in place or
anyone to create/maintain it
Timo: fedora project has some stuff that maybe we could use
RP: resource issue, patch-test and patchwork are limping along already
Timo: fyi, Intel is hoping to take a look (shortly) at patch-test and
patchwork (it’s in the queue)
RP: thankfully some tools are getting tested since they have test suites,
hopefully more tools will get test suites

TW: we had a nice OEHH last Wednesday, thanks to all for the opportunity, nice
to see people attending
Timo: i appreciate it too
Crofton: i’ve created an OE calendar with the dates going forward, let me
know how that works
http://www.openembedded.org/wiki/Calendar

TW: time to start planning for next YPDD?
Armin: yes, David was on yesterday’s advocacy meeting and said he was taking
a lead on it

SS: getting ready for next LTS release, please take a look at the current CVE
list (we’re getting it down)
Armin: what’s different between having Steve send it out rather than the AB?
RP: i think generating it automatically causes it to end up in a black hole
that nobody looks at. i prefer to have it be more personal
SS: it is automatically generated
Timo: we also have tool (from WR)
RP: that is a good tool (the WR one). i’d like to see SS’s tool released
too so we can say “this is what we’re using”
Crofton: is YP security list still a thing?
(varous): yes, there is a mailing list
Crofton: it appears dead, bad for people to sign up then not see any activity
Armin: i thought there were hooks
Scott: the hooks stopped working a while back, there hasn’t been an email to
that list in months. talks to get it working again (MarkH)
RP: there was a datacentre move a while back, maybe that’s what happened
TW: oecommits emails stopped at end of March, maybe same thing?
Scott: or maybe the groups.io move?

Scott: yesterday, announcement of the new open software security foundation
(which appears to be an LF project) did OE/YP get invited?
https://openssf.org/
Crofton: i posted that on twitter, i’ll get back with the replies. chances
are we could use their help and they could use ours
RP: it’s the first i’ve heard of this, i’ve discussed with LF to have
better communication between LF members, especially for new foundations,
we weren’t notified but we should try to reach out
Timo: is there any regular LF-wide meeting within LF?
RP: no
Crofton: closest would be the Leadership Conference
RP: coordination between all the LF projects is hard and doesn’t exist (yet,
at least not to the degree that maybe it could)

Timo: fop is a “you should have this installed if you want to generate the
docs”
Timo: do we know how some of our diagrams were generated? do we have the
“sources”?
RP: i’m guessing not. i looked at some of them recently and noticed some
tweaking was needed and was wondering how we’d do that

Timo: last week Thea had some ideas for solving some of our resourcing issues.
e.g. looking at stats of past contributors can help find resources
Armin: i was at yesterday’s advocacy meeting, and this wasn’t a big topic
of discussion
Scott: is foundries.io a member now?
RP: yes
Scott: needs to be added to website
RP: odd, they are a silver member now

Bruce: hoping to go with 5.8 kernel (and related libc headers) for gatesgarth.
things are looking good, lots of pain (strace!) but coming along well

4081 - 4100 of 54277