Re: [yocto] [meta-raspberry]rpi-config

[Modjo]

Thanks for your answer. I will try tomorrow and let you known the result.

Regards,


Le 11/09/2018 à 18:43, Khem Raj a écrit :


On 9/11/18 8:17 AM, idealsim wrote:

Hi i'm trying to build an image for a raspberry-pi 3 on branch sumo but
i have an error when i try to include rpi-config. See the issue under :

ERROR: Task do_populate_sdk in
/media/xxx/data/raspberry/yocto/yocto_official/poky-sumo/meta-xxx/recipes-/images/console-image-.bb
rdepends upon non-existent task do_package_write_rpm in
/media/xxx/data/raspberry/yocto/yocto_official/poky-sumo/meta-raspberrypi/recipes-bsp/bootfiles/rpi-config_git.bb

ERROR: Command execution failed: 1

Do you have an idea how i can resolve this please ?


can you try this patch and report back if it helps or not

https://github.com/kraj/meta-raspberrypi/commit/095f642e7c064b44d12854966468cc5a2699d8fd


Regards,

Mickaël


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

Re: [yocto] [meta-raspberry]rpi-config

[Khem Raj]

On 9/11/18 8:17 AM, idealsim wrote:
> Hi i'm trying to build an image for a raspberry-pi 3 on branch sumo but
> i have an error when i try to include rpi-config. See the issue under :
> 
> ERROR: Task do_populate_sdk in
> /media/xxx/data/raspberry/yocto/yocto_official/poky-sumo/meta-xxx/recipes-/images/console-image-.bb
> rdepends upon non-existent task do_package_write_rpm in
> /media/xxx/data/raspberry/yocto/yocto_official/poky-sumo/meta-raspberrypi/recipes-bsp/bootfiles/rpi-config_git.bb
> 
> ERROR: Command execution failed: 1
> 
> Do you have an idea how i can resolve this please ?
> 

can you try this patch and report back if it helps or not

https://github.com/kraj/meta-raspberrypi/commit/095f642e7c064b44d12854966468cc5a2699d8fd

> Regards,
> 
> Mickaël



signature.asc
Description: OpenPGP digital signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Postinstall scriptlets of ['coreutils'] have failed

[Jens Rehsack]

> Am 10.09.2018 um 21:09 schrieb Martin Jansa :
> 
> pn-buildlist isn't really useful in this case, building both coreutils and 
> busybox doesn't imply that both will be actually included in the image..
> 
> If you compare installed-package-names.txt in buildhistory you'll see that 
> only the core-image-minimal-dev has coreutils installed.
> 
> docker-shr qemux86-64@ ~/build/oe-core/buildhistory/images/qemux86_64/glibc $ 
> grep busybox core-image-minimal*/installed-package-names.txt
> core-image-minimal-dev/installed-package-names.txt:busybox
> core-image-minimal-dev/installed-package-names.txt:busybox-dev
> core-image-minimal-dev/installed-package-names.txt:busybox-syslog
> core-image-minimal-dev/installed-package-names.txt:busybox-udhcpc
> core-image-minimal/installed-package-names.txt:busybox
> core-image-minimal/installed-package-names.txt:busybox-syslog
> core-image-minimal/installed-package-names.txt:busybox-udhcpc
> docker-shr qemux86-64@ ~/build/oe-core/buildhistory/images/qemux86_64/glibc $ 
> grep coreutils core-image-minimal*/installed-package-names.txt
> core-image-minimal-dev/installed-package-names.txt:coreutils
> core-image-minimal-dev/installed-package-names.txt:coreutils-dev
> 
> That's why the issue is shown only in core-image-minimal-dev.

The files "installed-package-names.txt" are not available in my setup (IIRC one 
has to enable that explicitly).

> Do you have custom busybox defconfig which enables nice applet? It's not 
> enabled in default config:
> meta/recipes-core/busybox/busybox/defconfig:# CONFIG_NICE is not set

You're right. Ages ago - in April 2015 - I added that to my busybox 
configuration, since I need a
nice for some scripts on target. And since you figured out, coreutils is 
(likely with reason) not
available in general for some images, others might have that, too.

So I created a small patch for corutils ;)

Thanks for figuring that out.

Cheers,
Jens

> On Mon, Sep 10, 2018 at 8:15 PM Jens Rehsack  > wrote:
> 
> 
>> Am 09.09.2018 um 20:56 schrieb Martin Jansa > >:
>> 
>> Does core-image-minimal include both busybox and coreutils? Maybe only -dev 
>> include both.
> 
> Unfortunately both include coreutils, see attached pn-buildlist (I can send 
> you the recipe-depends and the task-depends, either if you need them).
> 
>> I'll send fix for attr soon, waiting for some builds to finish testing it.
> 
> Seems similar to my kind of soon :-)
> 
>> On Sun, Sep 9, 2018 at 8:47 PM Jens Rehsack > > wrote:
>> So far, so good.
>> 
>> They way to fix that seems either to check why busybox uses ${base_bindir} 
>> nowadays in favor of ${bindir} and fix either busybox or coreutils or attr.
>> 
>> What drives me nuts is not only the failure after the busybox update - why 
>> does core-image-minimal builds successful while core-image-minimal-dev fails?
>> 
>> Cheers,
>> Jens
>> 
>>> Am 09.09.2018 um 19:27 schrieb Martin Jansa >> >:
>>> 
>>> busybox is most likely the one providing it in ${base_bindir}
>>> 
>>> Recent busybox upgrade probably moved this file.
>>> 
>>> There is also conflict on /usr/bin/setfattr between busybox and attr now.
>>> 
>>> On Sun, Sep 9, 2018 at 7:22 PM Martin Jansa >> > wrote:
>>> There are 2 packages using u-a for nice, but one is using {bindir} and 2nd 
>>> one is using {base_bindir}
>>> 
>>> coreutils is using bindir, find what's using ${base_bindir} and change one 
>>> of them to use the same u-a link as the other one.
>>> 
>>> On Sun, Sep 9, 2018 at 5:59 PM Jens Rehsack >> > wrote:
>>> 
>>> 
 Am 09.09.2018 um 13:15 schrieb Alexander Kanavin >>> >:
 
 It's right in the message?
 
 ERROR: Logfile of failure stored in:
 /home/sno/gpw-community-bsp/mops-yocto-platform/tmp/work/fischer-poky-linux/core-image-minimal-dev/1.0-r0/temp/log.do_rootfs.27709
 
 Alex
>>> 
>>> 
>>> It's not much what stands there:
>>> 
>>> Downloading 
>>> file:/home/sno/gpw-community-bsp/mops-yocto-platform/tmp/work/fischer-poky-linux/core-image-minimal-dev/1.0-r0/oe-rootfs-repo/core2-64/libcap-dev_2.25-r0_core2-64.ipk.
>>> Installing coreutils-dev (8.30) on root
>>> [...]
>>> Configuring update-rc.d-deupdate-alternatives: Linking 
>>> /home/sno/gpw-community-bsp/mops-yocto-platform/tmp/work/fischer-poky-linux/core-image-minimal-dev/1.0-r0/rootfs/usr/bin/diff
>>>  to /usr/bin/diff.diffutils
>>> update-alternatives: Linking 
>>> /home/sno/gpw-community-bsp/mops-yocto-platform/tmp/work/fischer-poky-linux/core-image-minimal-dev/1.0-r0/rootfs/usr/bin/cmp
>>>  to /usr/bin/cmp.diffutils
>>> update-alternatives: Linking 
>>> /home/sno/gpw-community-bsp/mops-yocto-platform/tmp/work/fischer-poky-linux/core-image-minimal-dev/1.0-r0/rootfs/bin/umount
>>>  to /bin/umount.util-linux
>>> update-alternatives: Linking 
>>> 

Re: [yocto] [meta-raspberry]rpi-config

[Andrei Gherzan]

On Tue, Sep 11, 2018 at 4:41 PM idealsim  wrote:

> Hi i'm trying to build an image for a raspberry-pi 3 on branch sumo but i
> have an error when i try to include rpi-config. See the issue under :
>
> ERROR: Task do_populate_sdk in
>
> /media/xxx/data/raspberry/yocto/yocto_official/poky-sumo/meta-xxx/recipes-/images/
> console-image-.bb
> rdepends upon non-existent task do_package_write_rpm in
>
> /media/xxx/data/raspberry/yocto/yocto_official/poky-sumo/meta-raspberrypi/recipes-bsp/bootfiles/
> rpi-config_git.bb
> ERROR: Command execution failed: 1
>

Is your image installing rpi-config?
--
Andrei Gherzan
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-raspberry]rpi-config

[idealsim]

Hi i'm trying to build an image for a raspberry-pi 3 on branch sumo but i  
have an error when i try to include rpi-config. See the issue under :


ERROR: Task do_populate_sdk in  
/media/xxx/data/raspberry/yocto/yocto_official/poky-sumo/meta-xxx/recipes-/images/console-image-.bb  
rdepends upon non-existent task do_package_write_rpm in  
/media/xxx/data/raspberry/yocto/yocto_official/poky-sumo/meta-raspberrypi/recipes-bsp/bootfiles/rpi-config_git.bb

ERROR: Command execution failed: 1

Do you have an idea how i can resolve this please ?

Regards,

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

[yocto] Yocto Project Status WW37’18

[Jolley, Stephen K]

Current Dev Position: YP 2.6 M3. - This is feature freeze for YP 2.6!

Next Deadline: YP 2.6 M3 Build Target is Aug. 27, 2018


SWAT Team Rotation:

· SWAT lead is currently: Amanda

· SWAT team rotation: Amanda -> Tracy on Sept. 14, 2018

· SWAT team rotation: Tracy-> Armin on Sept. 21, 2018

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


Key Status/Updates:

· We’re now into M3 feature freeze so new feature patches, particularly 
for unplanned changes will be much less likely to be merged until 2.7 now.

· M3 has not been built yet. The main remaining missing feature is the 
multilib allarch change, most other things have now merged.

· We’re aware of problems with openssl 1.1 in python 3.5 and are 
looking into ways of addressing this problem.

· There were a number of recipe upgrades that merged slightly later 
than normal, the feeling being it was better to be up to date in this case, 
including some key components like busybox which contained security fixes.

· Fixes for various build warnings merged. This included kernel config 
warnings, universe build warnings and sstate manifest warnings. Bugs have been 
filed for the remaining build warnings the autobuilder is showing and aiming 
for warning free builds looks realistic for 2.6 final release.

· A bug was found in bitbake’s runqueue code which was leading to 
missing build artefacts in very rare circumstances (missing single sstate 
objects in complex dependency chains). The result was an sstate manifest 
warning and image postinstalls being deferred to on-target.

· Various improvements to python were made to mitigate the performance 
issues seen by the introduction of profile guided optimisation (thanks Ross!)

· There were problems found with busybox-syslog having installation 
order issues and changes were made to the packagegroups to mitigate the 
postinstall errors which were impacting automated testing.

· The sstate hash equivalency code is still pending review and 
resolution of the filehandle upon fork issues.

· We plan to build M3 on the new autobuilder codebase and 
infrastructure (based upon buildbot ‘nine’) and decommission the older buildbot 
‘eight’ codebase ASAP. There is a display issue on the autobuilder to do with 
build object properties not refreshing, its cosmetic only, is cleared by 
refreshing the browser and we’re working with upstream to track down the issue.


Planned Releases for YP 2.6:

· YP 2.6 M3 Build Target is Aug. 27, 2018

· YP 2.6 M3 Release Target is Sept. 7, 2018

· YP 2.6 M4 Build Target is Oct. 1, 2018

· YP 2.6 M4 Release Target is Oct. 26, 2018


Planned upcoming dot releases:

· YP 2.4.4 (Rocko) will be targeted after YP 2.6 M4 is done.

· YP 2.5.2 (Sumo) will be targeted after YP 2.4.4 is done.


Tracking Metrics:

· WDD 2580 (last week 2582) 
(https://wiki.yoctoproject.org/charts/combo.html)

· Poky Patch Metrics

oTotal patches found: 1646 (last week 1643)

oPercentage of patches in the Pending State: 736 (45%) [last week 736 (45%)]


Key Status Links for YP:

https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.6_Status

https://wiki.yoctoproject.org/wiki/Yocto_2.6_Schedule

https://wiki.yoctoproject.org/wiki/Yocto_2.6_Features


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
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
•Cell:(208) 244-4460
• Email: stephen.k.jol...@intel.com

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

[yocto] [sumo] systemd install problem when polkit enabled

[Belisko Marek]

Hi,

I'm building core image (with added systemd) for x86 but I hit an
issue when installing systemd
that it fails chown polkitd:root (looks like there was discussion
about this issue here:
https://patchwork.openembedded.org/patch/142904/ but no real
explanation why it sometimes fails). Any ideas what to check? Using
poky sumo. Thanks.

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
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [layerindex-web][V2 PATCH 1/1] import_layer.py: add -t option for layer_type

[Robert Yang]

Now the logic is:
Use options.layer_type if specified, and guess if not. Default to 'M'.

Note choices=['A', 'B', 'S', 'D', 'M', ''], the '' is for default='', we can't
use default='M' here, otherwise we don't know whether the 'M' is specified by
user or is the default value, we don't guess if it is specified by user,
otherwise, guess.

Signed-off-by: Robert Yang 
---
 layerindex/tools/import_layer.py | 38 --
 1 file changed, 32 insertions(+), 6 deletions(-)

diff --git a/layerindex/tools/import_layer.py b/layerindex/tools/import_layer.py
index 2413cff..60986e0 100755
--- a/layerindex/tools/import_layer.py
+++ b/layerindex/tools/import_layer.py
@@ -178,6 +178,22 @@ def get_github_layerinfo(layer_url, username = None, 
password = None):
 
 return (json_data, owner_json_data)
 
+def get_layer_type_choices():
+"""
+Return help string and choices for --type.
+"""
+from layerindex.models import LayerItem
+help_str = "Specify layer type."
+choices = []
+for i in LayerItem.LAYER_TYPE_CHOICES:
+key, description = i
+help_str += ' %s: %s,' % (key, description)
+choices.append(key)
+
+help_str = help_str.rstrip(',')
+choices.append('')
+
+return (help_str, choices)
 
 def main():
 valid_layer_name = re.compile('[-\w]+$')
@@ -186,9 +202,16 @@ def main():
 usage = """
 %prog [options]  [name]""")
 
+utils.setup_django()
+layer_type_help, layer_type_choices = get_layer_type_choices()
+
 parser.add_option("-s", "--subdir",
 help = "Specify subdirectory",
 action="store", dest="subdir")
+parser.add_option("-t", "--type",
+help = layer_type_help,
+choices = layer_type_choices,
+action="store", dest="layer_type", default='')
 parser.add_option("-n", "--dry-run",
 help = "Don't write any data back to the database",
 action="store_true", dest="dryrun")
@@ -238,7 +261,6 @@ def main():
 github_login = None
 github_password = None
 
-utils.setup_django()
 import settings
 from layerindex.models import LayerItem, LayerBranch, LayerDependency, 
LayerMaintainer
 from django.db import transaction
@@ -263,7 +285,6 @@ def main():
 layer = LayerItem()
 layer.name = layer_name
 layer.status = 'P'
-layer.layer_type = 'M'
 layer.summary = 'tempvalue'
 layer.description = layer.summary
 
@@ -349,11 +370,18 @@ def main():
 
 
 logger.info('Creating layer %s' % layer.name)
-# Guess layer type
-if glob.glob(os.path.join(layerdir, 'conf/distro/*.conf')):
+# Guess layer type if not specified
+if options.layer_type:
+layer.layer_type = options.layer_type
+elif layer.name in ['openembedded-core', 'meta-oe']:
+layer.layer_type = 'A'
+elif glob.glob(os.path.join(layerdir, 'conf/distro/*.conf')):
 layer.layer_type = 'D'
 elif glob.glob(os.path.join(layerdir, 'conf/machine/*.conf')):
 layer.layer_type = 'B'
+else:
+layer.layer_type = 'M'
+
 layer.save()
 layerbranch = LayerBranch()
 layerbranch.layer = layer
@@ -411,11 +439,9 @@ def main():
 
 if layer.name == 'openembedded-core':
 layer.summary = 'Core metadata'
-layer.layer_type = 'A'
 elif layer.name == 'meta-oe':
 layer.summary = 'Additional shared OE metadata'
 layer.description = layer.summary
-layer.layer_type = 'A'
 
 if maintainers:
 maint_re = re.compile(r'^"?([^"@$<>]+)"? *<([^<> ]+)>[ 
-]*(.+)?$')
-- 
2.7.4

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

[yocto] [layerindex-web][V2 PATCH 0/1] import_layer.py: add -t option for layer_type

[Robert Yang]

* V2:
  - Make -t option use LAYER_TYPE_CHOICES from models.py.

* V1:
  - Initial version

// Robert

The following changes since commit ac32edb5bdbdef30ccf3ef49af0977246571abaa:

  TODO: add some more items (2018-09-06 11:08:43 +1200)

are available in the git repository at:

  git://git.pokylinux.org/poky-contrib rbt/li
  http://git.pokylinux.org/cgit.cgi//log/?h=rbt/li

Robert Yang (1):
  import_layer.py: add -t option for layer_type

 layerindex/tools/import_layer.py | 38 --
 1 file changed, 32 insertions(+), 6 deletions(-)

-- 
2.7.4

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

Re: [yocto] I can't seem to include tc in my image

[Nicolas Dechesne]

hi,

On Tue, Sep 11, 2018 at 9:16 AM Adham ElSafty
 wrote:
>
> I am trying to use traffic control in my yocto image and I want to use tc. I 
> included the iproute2 package in my image and used the IMAGE_INSTALL_APPEND = 
> “ iproute2” in the local.conf file.

Please use _append instead of _APPEND.

>
> When I run the core-image-minimal I can’t seem to find any of the iproute 
> commands installed though.
>
> Am I doing anything wrong or is anything missing?
>
>
>
> Best Regards,
>
> Adham ElSafty
>
> R Embedded Software Engineer
>
> Idea In Motion
>
>
>
> --
> ___
> 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] I can't seem to include tc in my image

[Adham ElSafty]

I am trying to use traffic control in my yocto image and I want to use tc. I 
included the iproute2 package in my image and used the IMAGE_INSTALL_APPEND = " 
iproute2" in the local.conf file.
When I run the core-image-minimal I can't seem to find any of the iproute 
commands installed though.
Am I doing anything wrong or is anything missing?

Best Regards,
Adham ElSafty
R Embedded Software Engineer
Idea In Motion

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