Date   

qtwayland compile issue 5.15 #dunfell

sateesh m
 

Hi Guys,

              I am getting qtwayland building issue using dunfell version. can  anybody help me to solve this issue.



Regards,
Sateesh


Re: Raspberry PI enabling MMC1

chuck kamas
 

Raj,


Thanks for taking the time to respond. I thought of that too. My custom Yocto build has the line to turn on the sdio in it:

dtoverlay=sdio,poll_once=off
I have attached the entire file: config.txt.yocto

However, the Rasbian image does not have any mention of the dtoverlay for the sdio.  Curious. See config.txt attached.


Thanks for the help!

Chuck


On 11/17/20 12:08 AM, Khem Raj wrote:
On Mon, Nov 16, 2020 at 11:43 PM chuck kamas via
lists.yoctoproject.org <chuckkamas=yahoo.com@...>
wrote:
Hi all,


I have been spinning my wheels for two days trying to discover how to
enable MMC1 on a CM3. This is the one on GPIO22-27. I can boot Rasbian
on the CM3 and it inits the MMC1 and its pins just fine. I can
read/write to my SD card from it etc. However, when I build yocto it
leaves the GPIOS22-27 in gpio mode and does not set them to MMC1 mode.
I have tried changing the device tree as described here:

https://stackoverflow.com/questions/44702426/how-to-setup-an-own-device-tree-for-a-raspberrypi-in-yocto

That compiles and add the .dtbo to my build, but still the GPIOS are not
set to MMC1 mode.

cat /sys/kernel/debug/pinctrl/*gpio*/pinmux-pins
Pinmux settings per pin
Format: pin (name): mux_owner gpio_owner hog?
....

pin 22 (gpio22): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 23 (gpio23): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 24 (gpio24): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 25 (gpio25): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 26 (gpio26): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 27 (gpio27): (MUX UNCLAIMED) (GPIO UNCLAIMED)

.....
I have looked at:

https://ralimtek.com/raspberry%20pi/electronics/software/raspberry_pi_secondary_sd_card/


Any ideas of where to look next to turn on the sdio would be appreciated!

what does /boot/config.txt look like on raspbian and yocto built images

Chuck




Re: [PATCH yocto-autobuilder-helper] auh-config: add non-default distro features

Alexander Kanavin
 

ping :)

Alex


On Tue, 10 Nov 2020 at 09:56, Alexander Kanavin via lists.yoctoproject.org <alex.kanavin=gmail.com@...> wrote:
This adds systemd and pam related recipes to upstream checks and devtool-driven updates.

Signed-off-by: Alexander Kanavin <alex.kanavin@...>
---
 scripts/auh-config/local.conf.append | 1 +
 1 file changed, 1 insertion(+)

diff --git a/scripts/auh-config/local.conf.append b/scripts/auh-config/local.conf.append
index 9628737..b18590f 100644
--- a/scripts/auh-config/local.conf.append
+++ b/scripts/auh-config/local.conf.append
@@ -1,3 +1,4 @@

 INHERIT += "buildhistory"
 LICENSE_FLAGS_WHITELIST = "commercial"
+DISTRO_FEATURES_append = ' systemd pam'
--
2.29.1





Re: KeyError: 'getpwuid(): uid not found: 1000' in do_package phase

Marek Belisko
 

On Tue, Nov 17, 2020 at 2:19 PM Nicolas Jeker <n.jeker@...> wrote:

On Mon, 2020-11-16 at 23:27 +0100, Martin Jansa wrote:
https://github.com/webOS-ports/meta-webos-ports/commit/9fd17a67cdbed92df13a14b002a189b4c6c2d442

is an example where it triggers this error, but doesn't trigger the
more common host-user-contaminated QA error (unless you happened to
use UID 1001 on host for the user running bitbake).

Similarly when the files are "installed" with e.g. "cp -a" for which
layers usually use "cp -R --no-dereference --preserve=mode,links -v".
On a related note, the do_install reference in the manual gives some
advice on how to use cp and tar without contaminating the build.

The relevant part:
Thanks all for valuable inputs. Issue solved +1

Safe methods for installing files include the following:
* The install utility. This utility is the preferred method.
* The cp command with the "--no-preserve=ownership" option.
* The tar command with the "--no-same-owner" option. See the
bin_package.bbclass file in the meta/classes directory of the
Source Directory for an example.

https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#ref-tasks-install

On Mon, Nov 16, 2020 at 10:10 PM Marek Belisko <
marek.belisko@...> wrote:
On Mon, Nov 16, 2020 at 9:52 PM Joshua Watt <jpewhacker@...>
wrote:


On 11/16/20 2:38 PM, Marek Belisko wrote:

Hi,

I'm bumping my project based on zeus to dunfell. I've update all
layers and in one of my recipes I'm seeing following issue (not
see on
zeus at all):
WARNING: cv-my-test-1.0-r0 do_package: KeyError in
./package/srv/10%.png
ERROR: cv-my-test-1.0-r0 do_package: Error executing a python
function
in exec_python_func() autogenerated:

The stack trace of python calls that resulted in this
exception/failure was:
File: 'exec_python_func() autogenerated', lineno: 2, function:
<module>
0001:
*** 0002:sstate_report_unihash(d)
0003:
File: '/home/ubuntu/projects/my-test-
/poky/meta/classes/sstate.bbclass',
lineno: 840, function: sstate_report_unihash
0836: report_unihash = getattr(bb.parse.siggen,
'report_unihash', None)
0837:
0838: if report_unihash:
0839: ss = sstate_state_fromvars(d)
*** 0840: report_unihash(os.getcwd(), ss['task'], d)
0841:}
0842:
0843:#
0844:# Shell function to decompress and prepare a package
for installation
File: '/home/ubuntu/projects/my-test-
/poky/bitbake/lib/bb/siggen.py',
lineno: 555, function: report_unihash
0551:
0552: if "." in self.method:
0553: (module, method) =
self.method.rsplit('.', 1)
0554: locs['method'] =
getattr(importlib.import_module(module), method)
*** 0555: outhash =
bb.utils.better_eval('method(path,
sigfile, task, d)', locs)
0556: else:
0557: outhash =
bb.utils.better_eval(self.method +
'(path, sigfile, task, d)', locs)
0558:
0559: try:
File: '/home/ubuntu/projects/my-test-
/poky/bitbake/lib/bb/utils.py',
lineno: 420, function: better_eval
0416: if extraglobals:
0417: ctx = copy.copy(ctx)
0418: for g in extraglobals:
0419: ctx[g] = extraglobals[g]
*** 0420: return eval(source, ctx, locals)
0421:
0422:@contextmanager
0423:def fileslocked(files):
0424: """Context manager for locking and unlocking file
locks."""
File: '<string>', lineno: 1, function: <module>
File "<string>", line 1, in <module>

File: '/home/ubuntu/projects/my-test-
/poky/meta/lib/oe/sstatesig.py',
lineno: 595, function: OEOuthashBasic
0591: process(root)
0592: for f in files:
0593: if f == 'fixmepath':
0594: continue
*** 0595: process(os.path.join(root, f))
0596: finally:
0597: os.chdir(prev_dir)
0598:
0599: return h.hexdigest()
File: '/home/ubuntu/projects/my-test-
/poky/meta/lib/oe/sstatesig.py',
lineno: 551, function: process
0547: add_perm(stat.S_IXOTH, 'x')
0548:
0549: if include_owners:
0550: try:
*** 0551: update_hash(" %10s" %
pwd.getpwuid(s.st_uid).pw_name)
0552: update_hash(" %10s" %
grp.getgrgid(s.st_gid).gr_name)
0553: except KeyError:
0554: bb.warn("KeyError in %s" %
path)
0555: raise
Exception: KeyError: 'getpwuid(): uid not found: 1000'

ERROR: Logfile of failure stored in:
/home/ubuntu/projects/my-test-/build/tmp/work/aarch64-poky-
linux/cv-my-test/1.0-r0/temp/log.do_package.27454

Is this known issue or something related to my host setup?

This means the recipe is having host contamination (where the UID
of the user doing the build is leaking into the file system).
Some ideas what can be the source of that. This recipe is basically
just copying files from archive to final rootfs without any special
processing or so.

Thanks and BR,

marek



BR,

marek






Re: #yocto zeus X11 keyboard #yocto

Monsees, Steven C (US)
 


Is there a way around this ?


Yocto Project Status WW46'20

Stephen Jolley
 

Current Dev Position: YP 3.3 M1 development

Next Deadline: 7th December 2020 YP 3.3 M1 build

 

Next Team Meetings:

 

Key Status/Updates:

  • YP 3.1.4 should build this week now the CVE work has reached a logical point for the build.
  • Master has now opened up for 3.3 development and patches are merging.
  • Dunfell has seen a number of CVE report improvements (count of 202 down to 71 in the past three months), either through patches/upgrades or in corrections to the CVE database information, thanks Steve and all those who’ve helped.
  • The dunfell CVE improvements have also drastically improved the situation with master.
  • Intermittent autobuilder issues continue to occur. You can see the list of failures we’re continuing to see by searching for the “AB-INT” tag in bugzilla: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT
  • The SWAT team has been re-established. A new mailing has been created as swat@... to support this and a number of member organizations have agreed to help staff this team. We are in the process of getting the process running again and in due course there will be the option of other community members being able to help too. The tools and processes are under review to allow us to optimise the process. Thanks to the members and everyone participating to make this happen!
  • There are big improvements underway to the autobuilder display of builds, for example, https://autobuilder.yoctoproject.org/typhoon/#/builders/44/builds/2744 which shows many more individual steps with more detailed information. There still needs to be improvements to the configuration markup to make best use of this (help welcome!) but this should significantly improve the autobuilder readability.
  • There are other ideas being discussed around autobuilder usability improvements such as remembering field history (patch submitted to upstream buildbot), better success/failure count reporting and potential replacement of the buildlog wiki page and autobuilder integration with a specific purpose django app.

 

Ways to contribute:

 

YP 3.3 Milestone Dates:

  • YP 3.3 M1 build date 2020/12/07
  • YP 3.3 M1 Release date 2020/12/18
  • YP 3.3 M2 build date 2021/01/18
  • YP 3.3 M2 Release date 2021/01/29
  • YP 3.3 M3 build date 2021/03/01
  • YP 3.3 M3 Release date 2021/03/12
  • YP 3.3 M4 build date 2021/04/05
  • YP 3.3 M4 Release date 2021/04/30

 

Planned upcoming dot releases:

  • YP 3.1.4 build date 2020/11/2
  • YP 3.1.4 release date 2020/11/13
  • YP 3.2.1 build date 2020/11/16
  • YP 3.2.1 release date 2020/12/4
  • YP 3.1.5 build date 2021/01/11
  • YP 3.1.5 release date 2021/01/22
  • YP 3.2.2 build date 2021/02/08
  • YP 3.2.2 release date 2021/02/19
  • YP 3.1.6 build date 2021/02/22
  • YP 3.1.6 release date 2021/03/05
  • YP 3.1.7 build date 2021/03/22
  • YP 3.1.7 release date 2021/04/02

 

Tracking Metrics:

 

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

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Re: KeyError: 'getpwuid(): uid not found: 1000' in do_package phase

Nicolas Jeker
 

On Mon, 2020-11-16 at 23:27 +0100, Martin Jansa wrote:
https://github.com/webOS-ports/meta-webos-ports/commit/9fd17a67cdbed92df13a14b002a189b4c6c2d442

is an example where it triggers this error, but doesn't trigger the
more common host-user-contaminated QA error (unless you happened to
use UID 1001 on host for the user running bitbake).

Similarly when the files are "installed" with e.g. "cp -a" for which
layers usually use "cp -R --no-dereference --preserve=mode,links -v".
On a related note, the do_install reference in the manual gives some
advice on how to use cp and tar without contaminating the build.

The relevant part:

Safe methods for installing files include the following:
* The install utility. This utility is the preferred method.
* The cp command with the "--no-preserve=ownership" option.
* The tar command with the "--no-same-owner" option. See the
bin_package.bbclass file in the meta/classes directory of the
Source Directory for an example.

https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#ref-tasks-install

On Mon, Nov 16, 2020 at 10:10 PM Marek Belisko <
marek.belisko@...> wrote:
On Mon, Nov 16, 2020 at 9:52 PM Joshua Watt <jpewhacker@...>
wrote:


On 11/16/20 2:38 PM, Marek Belisko wrote:

Hi,

I'm bumping my project based on zeus to dunfell. I've update all
layers and in one of my recipes I'm seeing following issue (not
see on
zeus at all):
WARNING: cv-my-test-1.0-r0 do_package: KeyError in
./package/srv/10%.png
ERROR: cv-my-test-1.0-r0 do_package: Error executing a python
function
in exec_python_func() autogenerated:

The stack trace of python calls that resulted in this
exception/failure was:
File: 'exec_python_func() autogenerated', lineno: 2, function:
<module>
      0001:
  *** 0002:sstate_report_unihash(d)
      0003:
File: '/home/ubuntu/projects/my-test-
/poky/meta/classes/sstate.bbclass',
lineno: 840, function: sstate_report_unihash
      0836:    report_unihash = getattr(bb.parse.siggen,
'report_unihash', None)
      0837:
      0838:    if report_unihash:
      0839:        ss = sstate_state_fromvars(d)
  *** 0840:        report_unihash(os.getcwd(), ss['task'], d)
      0841:}
      0842:
      0843:#
      0844:# Shell function to decompress and prepare a package
for installation
File: '/home/ubuntu/projects/my-test-
/poky/bitbake/lib/bb/siggen.py',
lineno: 555, function: report_unihash
      0551:
      0552:            if "." in self.method:
      0553:                (module, method) =
self.method.rsplit('.', 1)
      0554:                locs['method'] =
getattr(importlib.import_module(module), method)
  *** 0555:                outhash =
bb.utils.better_eval('method(path,
sigfile, task, d)', locs)
      0556:            else:
      0557:                outhash =
bb.utils.better_eval(self.method +
'(path, sigfile, task, d)', locs)
      0558:
      0559:            try:
File: '/home/ubuntu/projects/my-test-
/poky/bitbake/lib/bb/utils.py',
lineno: 420, function: better_eval
      0416:    if extraglobals:
      0417:        ctx = copy.copy(ctx)
      0418:        for g in extraglobals:
      0419:            ctx[g] = extraglobals[g]
  *** 0420:    return eval(source, ctx, locals)
      0421:
      0422:@contextmanager
      0423:def fileslocked(files):
      0424:    """Context manager for locking and unlocking file
locks."""
File: '<string>', lineno: 1, function: <module>
   File "<string>", line 1, in <module>

File: '/home/ubuntu/projects/my-test-
/poky/meta/lib/oe/sstatesig.py',
lineno: 595, function: OEOuthashBasic
      0591:            process(root)
      0592:            for f in files:
      0593:                if f == 'fixmepath':
      0594:                    continue
  *** 0595:                process(os.path.join(root, f))
      0596:    finally:
      0597:        os.chdir(prev_dir)
      0598:
      0599:    return h.hexdigest()
File: '/home/ubuntu/projects/my-test-
/poky/meta/lib/oe/sstatesig.py',
lineno: 551, function: process
      0547:                    add_perm(stat.S_IXOTH, 'x')
      0548:
      0549:                if include_owners:
      0550:                    try:
  *** 0551:                        update_hash(" %10s" %
pwd.getpwuid(s.st_uid).pw_name)
      0552:                        update_hash(" %10s" %
grp.getgrgid(s.st_gid).gr_name)
      0553:                    except KeyError:
      0554:                        bb.warn("KeyError in %s" %
path)
      0555:                        raise
Exception: KeyError: 'getpwuid(): uid not found: 1000'

ERROR: Logfile of failure stored in:
/home/ubuntu/projects/my-test-/build/tmp/work/aarch64-poky-
linux/cv-my-test/1.0-r0/temp/log.do_package.27454

Is this known issue or something related to my host setup?

This means the recipe is having host contamination (where the UID
of the user doing the build is leaking into the file system).
Some ideas what can be the source of that. This recipe is basically
just copying files from archive to final rootfs without any special
processing or so.

Thanks and BR,

marek



BR,

marek



How to generate the SDK for RPI3 #dunfell #raspberrypi #sdk

@prashant2314
 

Hi Team,

I've built OS for rpi3 using dunfell yocto. I've also generated SDK for the same, for that I've added these info in my local.conf file-

TOOLCHAIN_TARGET_TASK_append = " python3-dev kernel-dev kernel-devsrc"
TOOLCHAIN_HOST_TASK_append = " nativesdk-cmake"

and after this, it is generating kernel source also in SDK, but when I'm setting environment and utilizing kernel source to compile my kernel, then I'm getting following error-

make[2]: *** No rule to make target 'init/main.o', needed by 'init/built-in.a'.  Stop.
Makefile:1732: recipe for target 'init' failed
make[1]: *** [init] Error 2
make[1]: Leaving directory '/opt/poky/3.1.2/sysroots/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/lib/modules/5.4.64-v7/build'
Makefile:23: recipe for target 'default' failed
make: *** [default] Error 2


So please help me resolve this issue, and if I'm missing any thing to add in local.conf file, so help me in that to generate proper sdk.


Re: Raspberry PI enabling MMC1

Khem Raj
 

On Mon, Nov 16, 2020 at 11:43 PM chuck kamas via
lists.yoctoproject.org <chuckkamas=yahoo.com@...>
wrote:

Hi all,


I have been spinning my wheels for two days trying to discover how to
enable MMC1 on a CM3. This is the one on GPIO22-27. I can boot Rasbian
on the CM3 and it inits the MMC1 and its pins just fine. I can
read/write to my SD card from it etc. However, when I build yocto it
leaves the GPIOS22-27 in gpio mode and does not set them to MMC1 mode.
I have tried changing the device tree as described here:

https://stackoverflow.com/questions/44702426/how-to-setup-an-own-device-tree-for-a-raspberrypi-in-yocto

That compiles and add the .dtbo to my build, but still the GPIOS are not
set to MMC1 mode.

cat /sys/kernel/debug/pinctrl/*gpio*/pinmux-pins
Pinmux settings per pin
Format: pin (name): mux_owner gpio_owner hog?
....

pin 22 (gpio22): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 23 (gpio23): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 24 (gpio24): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 25 (gpio25): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 26 (gpio26): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 27 (gpio27): (MUX UNCLAIMED) (GPIO UNCLAIMED)

.....
I have looked at:

https://ralimtek.com/raspberry%20pi/electronics/software/raspberry_pi_secondary_sd_card/


Any ideas of where to look next to turn on the sdio would be appreciated!

what does /boot/config.txt look like on raspbian and yocto built images

Chuck





Raspberry PI enabling MMC1

chuck kamas
 

Hi all,


I have been spinning my wheels for two days trying to discover how to enable MMC1 on a CM3. This is the one on GPIO22-27. I can boot Rasbian on the CM3 and it inits the MMC1 and its pins just fine. I can read/write to my SD card from it etc. However, when I build yocto it leaves the GPIOS22-27 in gpio mode and does not set them to MMC1 mode.  I have tried changing the device tree as described here:

https://stackoverflow.com/questions/44702426/how-to-setup-an-own-device-tree-for-a-raspberrypi-in-yocto

That compiles and add the .dtbo to my build, but still the GPIOS are not set to MMC1 mode.

cat /sys/kernel/debug/pinctrl/*gpio*/pinmux-pins
Pinmux settings per pin
Format: pin (name): mux_owner gpio_owner hog?
....

pin 22 (gpio22): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 23 (gpio23): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 24 (gpio24): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 25 (gpio25): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 26 (gpio26): (MUX UNCLAIMED) (GPIO UNCLAIMED)
pin 27 (gpio27): (MUX UNCLAIMED) (GPIO UNCLAIMED)

.....
I have looked at:

https://ralimtek.com/raspberry%20pi/electronics/software/raspberry_pi_secondary_sd_card/


Any ideas of where to look next to turn on the sdio would be appreciated!


Chuck


Enhancements/Bugs closed WW46!

Stephen Jolley
 

All,

The below were the owners of enhancements or bugs closed during the last week!

Who

Count

steve@...

1

chee.yang.lee@...

1

randy.macleod@...

1

richard.purdie@...

1

Grand Total

4

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Current high bug count owners for Yocto Project 3.3

Stephen Jolley
 

All,

Below is the list as of top 50 bug owners as of the end of WW46 of who have open medium or higher bugs and enhancements against YP 3.3.   There are 111 possible work days left until the final release candidates for YP 3.3 needs to be released.

Who

Count

richard.purdie@...

35

ross@...

22

david.reyna@...

21

bluelightning@...

19

bruce.ashfield@...

19

timothy.t.orling@...

12

JPEWhacker@...

12

sakib.sajal@...

11

mark.morton@...

11

akuster808@...

9

trevor.gamblin@...

9

kai.kang@...

9

Qi.Chen@...

6

raj.khem@...

5

stacy.gaikovaia@...

5

rpjday@...

4

randy.macleod@...

4

yi.zhao@...

4

mostthingsweb@...

4

idadelm@...

4

mingli.yu@...

4

ydirson@...

3

alejandro@...

3

hongxu.jia@...

3

chee.yang.lee@...

3

matthewzmd@...

2

jpuhlman@...

2

saul.wold@...

2

jon.mason@...

2

jeanmarie.lemetayer@...

2

kergoth@...

2

jaewon@...

2

pokylinux@...

2

mark.hatle@...

2

nicolas.dechesne@...

2

maxime.roussinbelanger@...

1

liezhi.yang@...

1

aehs29@...

1

apoorvsangal@...

1

anuj.mittal@...

1

fede@...

1

matt.ranostay@...

1

mhalstead@...

1

jason.wessel@...

1

shachar@...

1

kai.ruhnau@...

1

liu.ming50@...

1

kexin.hao@...

1

ankur.tyagi85@...

1

jbb5044@...

1

dl9pf@...

1

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Yocto Project Newcomer & Unassigned Bugs - Help Needed

Stephen Jolley
 

All,

 

The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on the triage page under the appropriate heading:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs  Also please review: https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded and how to create a bugzilla account at: https://bugzilla.yoctoproject.org/createaccount.cgi

The idea is these bugs should be straight forward for a person to help work on who doesn't have deep experience with the project.  If anyone can help, please take ownership of the bug and send patches!  If anyone needs help/advice there are people on irc who can likely do so, or some of the more experienced contributors will likely be happy to help too.

 

Also, the triage team meets weekly and does its best to handle the bugs reported into the Bugzilla. The number of people attending that meeting has fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the triage team) are therefore going to start reporting out the currently 322 unassigned or newcomer bugs.

 

We're hoping people may be able to spare some time now and again to help out with these.  Bugs are split into two types, "true bugs" where things don't work as they should and "enhancements" which are features we'd want to add to the system.  There are also roughly four different "priority" classes right now, “3.2”, “3.3, "3.99" and "Future", the more pressing/urgent issues being in "3.2" and then “3.3”.

 

Please review this link and if a bug is something you would be able to help with either take ownership of the bug, or send me (sjolley.yp.pm@...) an e-mail with the bug number you would like and I will assign it to you (please make sure you have a Bugzilla account).  The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage_Archive#Unassigned_or_Newcomer_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Re: KeyError: 'getpwuid(): uid not found: 1000' in do_package phase

Martin Jansa
 

https://github.com/webOS-ports/meta-webos-ports/commit/9fd17a67cdbed92df13a14b002a189b4c6c2d442

is an example where it triggers this error, but doesn't trigger the more common host-user-contaminated QA error (unless you happened to use UID 1001 on host for the user running bitbake).

Similarly when the files are "installed" with e.g. "cp -a" for which layers usually use "cp -R --no-dereference --preserve=mode,links -v".

On Mon, Nov 16, 2020 at 10:10 PM Marek Belisko <marek.belisko@...> wrote:
On Mon, Nov 16, 2020 at 9:52 PM Joshua Watt <jpewhacker@...> wrote:
>
>
> On 11/16/20 2:38 PM, Marek Belisko wrote:
>
> Hi,
>
> I'm bumping my project based on zeus to dunfell. I've update all
> layers and in one of my recipes I'm seeing following issue (not see on
> zeus at all):
> WARNING: cv-my-test-1.0-r0 do_package: KeyError in ./package/srv/10%.png
> ERROR: cv-my-test-1.0-r0 do_package: Error executing a python function
> in exec_python_func() autogenerated:
>
> The stack trace of python calls that resulted in this exception/failure was:
> File: 'exec_python_func() autogenerated', lineno: 2, function: <module>
>      0001:
>  *** 0002:sstate_report_unihash(d)
>      0003:
> File: '/home/ubuntu/projects/my-test-/poky/meta/classes/sstate.bbclass',
> lineno: 840, function: sstate_report_unihash
>      0836:    report_unihash = getattr(bb.parse.siggen, 'report_unihash', None)
>      0837:
>      0838:    if report_unihash:
>      0839:        ss = sstate_state_fromvars(d)
>  *** 0840:        report_unihash(os.getcwd(), ss['task'], d)
>      0841:}
>      0842:
>      0843:#
>      0844:# Shell function to decompress and prepare a package for installation
> File: '/home/ubuntu/projects/my-test-/poky/bitbake/lib/bb/siggen.py',
> lineno: 555, function: report_unihash
>      0551:
>      0552:            if "." in self.method:
>      0553:                (module, method) = self.method.rsplit('.', 1)
>      0554:                locs['method'] =
> getattr(importlib.import_module(module), method)
>  *** 0555:                outhash = bb.utils.better_eval('method(path,
> sigfile, task, d)', locs)
>      0556:            else:
>      0557:                outhash = bb.utils.better_eval(self.method +
> '(path, sigfile, task, d)', locs)
>      0558:
>      0559:            try:
> File: '/home/ubuntu/projects/my-test-/poky/bitbake/lib/bb/utils.py',
> lineno: 420, function: better_eval
>      0416:    if extraglobals:
>      0417:        ctx = copy.copy(ctx)
>      0418:        for g in extraglobals:
>      0419:            ctx[g] = extraglobals[g]
>  *** 0420:    return eval(source, ctx, locals)
>      0421:
>      0422:@contextmanager
>      0423:def fileslocked(files):
>      0424:    """Context manager for locking and unlocking file locks."""
> File: '<string>', lineno: 1, function: <module>
>   File "<string>", line 1, in <module>
>
> File: '/home/ubuntu/projects/my-test-/poky/meta/lib/oe/sstatesig.py',
> lineno: 595, function: OEOuthashBasic
>      0591:            process(root)
>      0592:            for f in files:
>      0593:                if f == 'fixmepath':
>      0594:                    continue
>  *** 0595:                process(os.path.join(root, f))
>      0596:    finally:
>      0597:        os.chdir(prev_dir)
>      0598:
>      0599:    return h.hexdigest()
> File: '/home/ubuntu/projects/my-test-/poky/meta/lib/oe/sstatesig.py',
> lineno: 551, function: process
>      0547:                    add_perm(stat.S_IXOTH, 'x')
>      0548:
>      0549:                if include_owners:
>      0550:                    try:
>  *** 0551:                        update_hash(" %10s" %
> pwd.getpwuid(s.st_uid).pw_name)
>      0552:                        update_hash(" %10s" %
> grp.getgrgid(s.st_gid).gr_name)
>      0553:                    except KeyError:
>      0554:                        bb.warn("KeyError in %s" % path)
>      0555:                        raise
> Exception: KeyError: 'getpwuid(): uid not found: 1000'
>
> ERROR: Logfile of failure stored in:
> /home/ubuntu/projects/my-test-/build/tmp/work/aarch64-poky-linux/cv-my-test/1.0-r0/temp/log.do_package.27454
>
> Is this known issue or something related to my host setup?
>
> This means the recipe is having host contamination (where the UID of the user doing the build is leaking into the file system).
Some ideas what can be the source of that. This recipe is basically
just copying files from archive to final rootfs without any special
processing or so.
>
> Thanks and BR,
>
> marek
>
>
>
>

BR,

marek




Re: Missing vardeps in meta/classes/roofs_rpm.bbclass?

Loic Domaigne
 

On 11/10/2020 7:18 PM Alexander Kanavin <alex.kanavin@...> wrote:


This seems like you need to make a patch (for master branch) and send it to
oe-core list? :)

Alex

On Tue, 10 Nov 2020 at 19:04, Loic Domaigne <tech@...> wrote:

Salut,

We were playing with rpm package management lately.

To configure the yum repos in the image, we're setting the following
variables in conf/local.conf:
FEED_PACKAGE_URIS
FEED_PACKAGE_BASE_PATHS

We made a typo, and forgot the S at the end of FEED_PACKAGE_BASE_PATHS
Not surprising, the repo file generated didn't have the right url:

$ cat oe-remote-repo-user1.repo
[oe-remote-repo-user1]
name=OE Remote Repo: user1
baseurl=http://192.168.7.1/user1
gpgcheck=0


After fixing the typo and bitbaking the image again, still no avail.
The repo file remains unchanged.

In fact, changing FEED_PACKAGE_BASE_PATHS did not re-trigger a new image
build. We found this behavior surprising.

AFAICS:
1) As per oe/lib/meta/lib/oe/rootfs.py and lib/oe/package_manager.py, the
URL is defined as the join paths of FEED_PACKAGE_URIS and
FEED_PACKAGE_BASE_PATHS.
2) However, in meta/classes/rootfs_rpm.bbclass, do_rootfs only specifies a
build dependency to FEED_PACKAGE_URIS:
do_rootfs[vardeps] += "PACKAGE_FEED_URIS"

Shouldn't the rootfs task depend on both PACKAGE_FEEDS_URIS and
PACKAGE_FEED_BASE_PATHS, ie.
do_rootfs[vardeps] += "PACKAGE_FEED_URIS PACKAGE_FEED_BASE_PATHS"

After fixing this dependency, the repo file got updated as expected:
cat oe-remote-repo-user1-rpm.repo
[oe-remote-repo-user1-rpm]
name=OE Remote Repo: user1 rpm
baseurl=http://192.168.7.1/user1/rpm
gpgcheck=0

Does that make sense?

I have conducted this analysis on Zeus. The problem isn't fixed with
Dunfell AFAICS. Also, the other package classes (deb,ipk) are impacted as
well.

Hope this helps!
Loic




Re: KeyError: 'getpwuid(): uid not found: 1000' in do_package phase

Marek Belisko
 

On Mon, Nov 16, 2020 at 9:52 PM Joshua Watt <jpewhacker@...> wrote:


On 11/16/20 2:38 PM, Marek Belisko wrote:

Hi,

I'm bumping my project based on zeus to dunfell. I've update all
layers and in one of my recipes I'm seeing following issue (not see on
zeus at all):
WARNING: cv-my-test-1.0-r0 do_package: KeyError in ./package/srv/10%.png
ERROR: cv-my-test-1.0-r0 do_package: Error executing a python function
in exec_python_func() autogenerated:

The stack trace of python calls that resulted in this exception/failure was:
File: 'exec_python_func() autogenerated', lineno: 2, function: <module>
0001:
*** 0002:sstate_report_unihash(d)
0003:
File: '/home/ubuntu/projects/my-test-/poky/meta/classes/sstate.bbclass',
lineno: 840, function: sstate_report_unihash
0836: report_unihash = getattr(bb.parse.siggen, 'report_unihash', None)
0837:
0838: if report_unihash:
0839: ss = sstate_state_fromvars(d)
*** 0840: report_unihash(os.getcwd(), ss['task'], d)
0841:}
0842:
0843:#
0844:# Shell function to decompress and prepare a package for installation
File: '/home/ubuntu/projects/my-test-/poky/bitbake/lib/bb/siggen.py',
lineno: 555, function: report_unihash
0551:
0552: if "." in self.method:
0553: (module, method) = self.method.rsplit('.', 1)
0554: locs['method'] =
getattr(importlib.import_module(module), method)
*** 0555: outhash = bb.utils.better_eval('method(path,
sigfile, task, d)', locs)
0556: else:
0557: outhash = bb.utils.better_eval(self.method +
'(path, sigfile, task, d)', locs)
0558:
0559: try:
File: '/home/ubuntu/projects/my-test-/poky/bitbake/lib/bb/utils.py',
lineno: 420, function: better_eval
0416: if extraglobals:
0417: ctx = copy.copy(ctx)
0418: for g in extraglobals:
0419: ctx[g] = extraglobals[g]
*** 0420: return eval(source, ctx, locals)
0421:
0422:@contextmanager
0423:def fileslocked(files):
0424: """Context manager for locking and unlocking file locks."""
File: '<string>', lineno: 1, function: <module>
File "<string>", line 1, in <module>

File: '/home/ubuntu/projects/my-test-/poky/meta/lib/oe/sstatesig.py',
lineno: 595, function: OEOuthashBasic
0591: process(root)
0592: for f in files:
0593: if f == 'fixmepath':
0594: continue
*** 0595: process(os.path.join(root, f))
0596: finally:
0597: os.chdir(prev_dir)
0598:
0599: return h.hexdigest()
File: '/home/ubuntu/projects/my-test-/poky/meta/lib/oe/sstatesig.py',
lineno: 551, function: process
0547: add_perm(stat.S_IXOTH, 'x')
0548:
0549: if include_owners:
0550: try:
*** 0551: update_hash(" %10s" %
pwd.getpwuid(s.st_uid).pw_name)
0552: update_hash(" %10s" %
grp.getgrgid(s.st_gid).gr_name)
0553: except KeyError:
0554: bb.warn("KeyError in %s" % path)
0555: raise
Exception: KeyError: 'getpwuid(): uid not found: 1000'

ERROR: Logfile of failure stored in:
/home/ubuntu/projects/my-test-/build/tmp/work/aarch64-poky-linux/cv-my-test/1.0-r0/temp/log.do_package.27454

Is this known issue or something related to my host setup?

This means the recipe is having host contamination (where the UID of the user doing the build is leaking into the file system).
Some ideas what can be the source of that. This recipe is basically
just copying files from archive to final rootfs without any special
processing or so.

Thanks and BR,

marek



BR,

marek


Re: KeyError: 'getpwuid(): uid not found: 1000' in do_package phase

Joshua Watt
 


On 11/16/20 2:38 PM, Marek Belisko wrote:
Hi,

I'm bumping my project based on zeus to dunfell. I've update all
layers and in one of my recipes I'm seeing following issue (not see on
zeus at all):
WARNING: cv-my-test-1.0-r0 do_package: KeyError in ./package/srv/10%.png
ERROR: cv-my-test-1.0-r0 do_package: Error executing a python function
in exec_python_func() autogenerated:

The stack trace of python calls that resulted in this exception/failure was:
File: 'exec_python_func() autogenerated', lineno: 2, function: <module>
     0001:
 *** 0002:sstate_report_unihash(d)
     0003:
File: '/home/ubuntu/projects/my-test-/poky/meta/classes/sstate.bbclass',
lineno: 840, function: sstate_report_unihash
     0836:    report_unihash = getattr(bb.parse.siggen, 'report_unihash', None)
     0837:
     0838:    if report_unihash:
     0839:        ss = sstate_state_fromvars(d)
 *** 0840:        report_unihash(os.getcwd(), ss['task'], d)
     0841:}
     0842:
     0843:#
     0844:# Shell function to decompress and prepare a package for installation
File: '/home/ubuntu/projects/my-test-/poky/bitbake/lib/bb/siggen.py',
lineno: 555, function: report_unihash
     0551:
     0552:            if "." in self.method:
     0553:                (module, method) = self.method.rsplit('.', 1)
     0554:                locs['method'] =
getattr(importlib.import_module(module), method)
 *** 0555:                outhash = bb.utils.better_eval('method(path,
sigfile, task, d)', locs)
     0556:            else:
     0557:                outhash = bb.utils.better_eval(self.method +
'(path, sigfile, task, d)', locs)
     0558:
     0559:            try:
File: '/home/ubuntu/projects/my-test-/poky/bitbake/lib/bb/utils.py',
lineno: 420, function: better_eval
     0416:    if extraglobals:
     0417:        ctx = copy.copy(ctx)
     0418:        for g in extraglobals:
     0419:            ctx[g] = extraglobals[g]
 *** 0420:    return eval(source, ctx, locals)
     0421:
     0422:@contextmanager
     0423:def fileslocked(files):
     0424:    """Context manager for locking and unlocking file locks."""
File: '<string>', lineno: 1, function: <module>
  File "<string>", line 1, in <module>

File: '/home/ubuntu/projects/my-test-/poky/meta/lib/oe/sstatesig.py',
lineno: 595, function: OEOuthashBasic
     0591:            process(root)
     0592:            for f in files:
     0593:                if f == 'fixmepath':
     0594:                    continue
 *** 0595:                process(os.path.join(root, f))
     0596:    finally:
     0597:        os.chdir(prev_dir)
     0598:
     0599:    return h.hexdigest()
File: '/home/ubuntu/projects/my-test-/poky/meta/lib/oe/sstatesig.py',
lineno: 551, function: process
     0547:                    add_perm(stat.S_IXOTH, 'x')
     0548:
     0549:                if include_owners:
     0550:                    try:
 *** 0551:                        update_hash(" %10s" %
pwd.getpwuid(s.st_uid).pw_name)
     0552:                        update_hash(" %10s" %
grp.getgrgid(s.st_gid).gr_name)
     0553:                    except KeyError:
     0554:                        bb.warn("KeyError in %s" % path)
     0555:                        raise
Exception: KeyError: 'getpwuid(): uid not found: 1000'

ERROR: Logfile of failure stored in:
/home/ubuntu/projects/my-test-/build/tmp/work/aarch64-poky-linux/cv-my-test/1.0-r0/temp/log.do_package.27454

Is this known issue or something related to my host setup?

This means the recipe is having host contamination (where the UID of the user doing the build is leaking into the file system).


Thanks and BR,

marek





KeyError: 'getpwuid(): uid not found: 1000' in do_package phase

Marek Belisko
 

Hi,

I'm bumping my project based on zeus to dunfell. I've update all
layers and in one of my recipes I'm seeing following issue (not see on
zeus at all):
WARNING: cv-my-test-1.0-r0 do_package: KeyError in ./package/srv/10%.png
ERROR: cv-my-test-1.0-r0 do_package: Error executing a python function
in exec_python_func() autogenerated:

The stack trace of python calls that resulted in this exception/failure was:
File: 'exec_python_func() autogenerated', lineno: 2, function: <module>
0001:
*** 0002:sstate_report_unihash(d)
0003:
File: '/home/ubuntu/projects/my-test-/poky/meta/classes/sstate.bbclass',
lineno: 840, function: sstate_report_unihash
0836: report_unihash = getattr(bb.parse.siggen, 'report_unihash', None)
0837:
0838: if report_unihash:
0839: ss = sstate_state_fromvars(d)
*** 0840: report_unihash(os.getcwd(), ss['task'], d)
0841:}
0842:
0843:#
0844:# Shell function to decompress and prepare a package for installation
File: '/home/ubuntu/projects/my-test-/poky/bitbake/lib/bb/siggen.py',
lineno: 555, function: report_unihash
0551:
0552: if "." in self.method:
0553: (module, method) = self.method.rsplit('.', 1)
0554: locs['method'] =
getattr(importlib.import_module(module), method)
*** 0555: outhash = bb.utils.better_eval('method(path,
sigfile, task, d)', locs)
0556: else:
0557: outhash = bb.utils.better_eval(self.method +
'(path, sigfile, task, d)', locs)
0558:
0559: try:
File: '/home/ubuntu/projects/my-test-/poky/bitbake/lib/bb/utils.py',
lineno: 420, function: better_eval
0416: if extraglobals:
0417: ctx = copy.copy(ctx)
0418: for g in extraglobals:
0419: ctx[g] = extraglobals[g]
*** 0420: return eval(source, ctx, locals)
0421:
0422:@contextmanager
0423:def fileslocked(files):
0424: """Context manager for locking and unlocking file locks."""
File: '<string>', lineno: 1, function: <module>
File "<string>", line 1, in <module>

File: '/home/ubuntu/projects/my-test-/poky/meta/lib/oe/sstatesig.py',
lineno: 595, function: OEOuthashBasic
0591: process(root)
0592: for f in files:
0593: if f == 'fixmepath':
0594: continue
*** 0595: process(os.path.join(root, f))
0596: finally:
0597: os.chdir(prev_dir)
0598:
0599: return h.hexdigest()
File: '/home/ubuntu/projects/my-test-/poky/meta/lib/oe/sstatesig.py',
lineno: 551, function: process
0547: add_perm(stat.S_IXOTH, 'x')
0548:
0549: if include_owners:
0550: try:
*** 0551: update_hash(" %10s" %
pwd.getpwuid(s.st_uid).pw_name)
0552: update_hash(" %10s" %
grp.getgrgid(s.st_gid).gr_name)
0553: except KeyError:
0554: bb.warn("KeyError in %s" % path)
0555: raise
Exception: KeyError: 'getpwuid(): uid not found: 1000'

ERROR: Logfile of failure stored in:
/home/ubuntu/projects/my-test-/build/tmp/work/aarch64-poky-linux/cv-my-test/1.0-r0/temp/log.do_package.27454

Is this known issue or something related to my host setup?

Thanks and BR,

marek

--
as simple and primitive as possible
-------------------------------------------------
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
twitter: #opennandra
web: http://open-nandra.com


Re: Single page view of a particular manual

Nicolas Dechesne
 

hi Vasyl,

On Mon, Nov 16, 2020 at 12:55 PM Vasyl Vavrychuk <vvavrychuk@...> wrote:

Hi, Nicolas,

Thank you for your reply.

On Sun, Nov 15, 2020 at 8:06 PM Nicolas Dechesne
<nicolas.dechesne@...> wrote:

Can you please describe what you are doing in the webpage? It should
You need to select "All in one Mega manual" in the
dropdown menu on the top left corner of the page. When you do that, it
should bring you to this URL:
https://docs.yoctoproject.org/singleindex.html

Which contains the whole YP docs in a 'single' html page.
But as far as I remember, previously I could have a single page view
of a particular manual, for example "Development Tasks Manual", etc.
It is much more useful than complete single page view of all documents
at the same time (but this one is useful too in some cases).
Ah, you're right. It was possible with the previous docs, but not
anymore. With the Sphinx based docs the whole Yocto Project docs is
just "one set", not a collection of 'manuals'. So currently the single
html page includes the entire documentation set.

There is no 'easy' way to change that though. I am definitely
interested to gather more feedback about that. We made a conscious
choice to get this way, It's different, and if it's causing more pain,
we should know and discuss..

I heard complaints before that we had too 'many' manuals, and it was
hard to know which one to open, which is the opposite of what you are
asking ;)

let's see if we can gather more feedback.


[yocto-autobuilder2 PATCH] config.py: remove redundant meta-kernel references

Ross Burton <ross@...>
 

From: Ross Burton <ross.burton@...>

Signed-off-by: Ross Burton <ross.burton@...>
---
config.py | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/config.py b/config.py
index 035a2f8..271e6b0 100644
--- a/config.py
+++ b/config.py
@@ -6,14 +6,14 @@ buildertorepos = {
"a-quick": ["poky", "meta-intel", "oecore", "bitbake",
"meta-mingw", "meta-gplv2"],
"a-full": ["poky", "meta-intel", "oecore", "bitbake",
- "meta-mingw", "meta-gplv2", "meta-arm", "meta-kernel"],
+ "meta-mingw", "meta-gplv2", "meta-arm"],
"non-gpl3": ["poky", "meta-gplv2"],
"meta-mingw": ["poky", "meta-mingw"],
"qa-extras": ["poky", "meta-mingw"],
"meta-oe": ["poky", "meta-openembedded"],
"meta-virt": ["poky", "meta-openembedded", "meta-virtualization"],
"meta-intel": ["poky", "meta-intel"],
- "meta-arm": ["poky", "meta-arm", "meta-kernel"],
+ "meta-arm": ["poky", "meta-arm"],
"qemuarm-oecore": ["oecore", "bitbake"],
"checkuri": ["poky"],
"check-layer": ["poky", "meta-mingw", "meta-gplv2"],
@@ -43,7 +43,6 @@ repos = {
"meta-gplv2": ["git://git.yoctoproject.org/meta-gplv2", "master"],
"meta-openembedded": ["git://git.openembedded.org/meta-openembedded", "master"],
"meta-virtualization": ["git://git.yoctoproject.org/meta-virtualization", "master"],
- "meta-kernel": ["https://gitlab.com/openembedded/community/meta-kernel.git", "master"],
"yocto-docs": ["git://git.yoctoproject.org/yocto-docs", "master"]
}

--
2.24.3 (Apple Git-128)

6421 - 6440 of 57809