On Mon, May 13, 2019 at 7:19 AM Edson Seabra <edson.sea...@zpesystems.com>
wrote:

> Hi,
>
>
> Thanks Khem Raj.
>
>
> As this package name is generate internally by poky/yocto I did this patch
> to make it build:
>
>
> *edson@ubuntu-16*:*oe*$ git diff package.py
>
> *diff --git a/meta/lib/oe/package.py b/meta/lib/oe/package.py*
>
> *index 6e83f01f14..3503313621 100644*
>
> *--- a/meta/lib/oe/package.py*
>
> *+++ b/meta/lib/oe/package.py*
>
> @@ -298,7 +298,7 @@ def npm_split_package_dirs(pkgdir):
>
>                  for pathitem in relpth.split('/'):
>
>                      if pathitem == 'node_modules':
>
>                          continue
>
> -                    pkgitems.append(pathitem)
>
> +                    pkgitems.append(pathitem.lower())
>
>                  pkgname = '-'.join(pkgitems).replace('_', '-')
>
>                  pkgname = pkgname.replace('@', '')
>
>                  pkgfile = os.path.join(root, dn, 'package.json')
>
>
> I do not feel confident to submit it. I would suggest a poky/yocto
> maintainer to step in.
>

Just change the concerned recipe name this patch is a bit too much

>
> Regards,
> Edson.
>
> ------------------------------
> *From:* Khem Raj <raj.k...@gmail.com>
> *Sent:* Sunday, May 12, 2019 4:50 AM
> *To:* Edson Seabra
> *Cc:* yocto@yoctoproject.org
> *Subject:* Re: [yocto] Build error on dockerode using YP-Core warrior 2.7
>
> Use all lowercase in recipe name you seem to have mixed it with uppercase
>
> On Sat, May 11, 2019 at 5:58 PM Edson Seabra <edson.sea...@zpesystems.com>
> wrote:
>
> Hi,
>
>
> I created the recipe for dockerode 2.5.8 using the command recipetool:
>
>
> recipetool create "npm://registry.npmjs.org;name=dockerode;version=2.5.8"
>
>
> The recipe creates a lot of ipk's package and fails on dockerode-JSONStream
> ipk.
>
>
> I can build dokerode with YP-Coce morty, almost sure I did with YP-Core
> thud.
>
>
> Any hint about how to find what  is this issue will be appreciated.
>
>
> NOTE. Other recipes, using npm.bbclass, build normally.
>
>
> If any additional information is needed just let me know...
>
>
> ==== here is the output of bitbake dockerode ======
>
> Build Configuration:
>
> BB_VERSION           = "1.42.0"
>
> BUILD_SYS            = "x86_64-linux"
>
> NATIVELSBSTRING      = "universal"
>
> TARGET_SYS           = "x86_64-poky-linux"
>
> MACHINE              = "genericx86-64"
>
> DISTRO               = "node-poky"
>
> DISTRO_VERSION       = "2.7"
>
> TUNE_FEATURES        = "m64 core2"
>
> TARGET_FPU           = ""
>
> IMAGE_LINGUAS        = "en-us en-gb"
>
> MACHINE_FEATURES     = "screen keyboard pci usbhost ext4 x86 acpi pcbios
> rtc"
>
> IMAGE_FSTYPES        = "hddimg"
>
> DISTRO_FEATURES      = "argp pam largefile xattr nfs pci x11 ipv4 ipv6
> libc-backtrace libc-big-macros libc-bsd libc-cxx-tests libc-catgets
> libc-charsets libc-crypt libc-crypt-ufc libc-db-aliases libc-envz libc-fcvt
> libc-fmtmsg libc-fstab libc-ftraverse libc-getlogin libc-idn libc-inet-anl
> libc-libm libc-locales libc-locale-code libc-memusage libc-nis
> libc-nsswitch libc-rcmd libc-rtld-debug libc-spawn libc-streams libc-sunrpc
> libc-utmp libc-utmpx libc-wordexp libc-posix-clang-wchar libc-posix-regexp
> libc-posix-regexp-glibc libc-posix-wchar-io multiarch sysvinit opengl
> pulseaudio wifi virtualization"
>
> IMAGE_FEATURES       = "package-management read-only-rootfs tools-debug"
>
> meta-nodegrid
>
> meta-kernel          = "trunk:11630-11620"
>
> meta-zpe             = "trunk:11630-11629"
>
> meta-oe              = "trunk:11630-11620"
>
> meta-graphics        = "trunk:11630-11172"
>
> meta-networking      = "trunk:11630-11560"
>
> meta-python          = "trunk:11630-11620"
>
> meta-selinux         = "master:b1dac7e2b26f869c991c6492aa7fa18eaa4b47f6"
>
> meta-virtualization  = "trunk:11630-11620"
>
> meta-tpm2            = "trunk:11630-11090"
>
> meta-java            = "master:2fc78571483465ca2fc69d6bd77632acd35e0770"
>
> meta
>
> meta-poky
>
> meta-yocto-bsp       = "warrior:1b425a8450872f915c30bd0a35b0b0df92172b70"
>
>
> Initialising tasks: 100%
> |############################################################| Time: 0:00:02
>
> Sstate summary: Wanted 33 Found 27 Missed 6 Current 365 (81% match, 98%
> complete)
>
> *NOTE*: Executing SetScene Tasks
>
> *NOTE*: Executing RunQueue Tasks
>
> *WARNING*: dockerode-2.5.8-r0 do_populate_lic: dockerode: No generic
> license file exists for: Unknown in any provider
>
> *ERROR*: dockerode-2.5.8-r0 do_package_write_ipk: Fatal errors occurred
> in subprocesses:
>
> Command
> 'PATH="/home/edson/ng-trunk/nodegrid/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/edson/ng-trunk/poky/scripts:/home/edson/ng-trunk/nodegrid/tmp/work/core2-64-poky-linux/dockerode/2.5.8-r0/recipe-sysroot-native/usr/bin/x86_64-poky-linux:/home/edson/ng-trunk/nodegrid/tmp/work/core2-64-poky-linux/dockerode/2.5.8-r0/recipe-sysroot/usr/bin/crossscripts:/home/edson/ng-trunk/nodegrid/tmp/work/core2-64-poky-linux/dockerode/2.5.8-r0/recipe-sysroot-native/usr/sbin:/home/edson/ng-trunk/nodegrid/tmp/work/core2-64-poky-linux/dockerode/2.5.8-r0/recipe-sysroot-native/usr/bin:/home/edson/ng-trunk/nodegrid/tmp/work/core2-64-poky-linux/dockerode/2.5.8-r0/recipe-sysroot-native/sbin:/home/edson/ng-trunk/nodegrid/tmp/work/core2-64-poky-linux/dockerode/2.5.8-r0/recipe-sysroot-native/bin:/home/edson/ng-trunk/poky/bitbake/bin:/home/edson/ng-trunk/nodegrid/tmp/hosttools"
> opkg-build -Z xz -a "--memlimit=50% --threads=4" dockerode-JSONStream
> /home/edson/ng-trunk/nodegrid/tmp/work/core2-64-poky-linux/dockerode/2.5.8-r0/deploy-ipks/core2-64'
> returned non-zero exit status 1.: Traceback (most recent call last):
>
>   File "/home/edson/ng-trunk/poky/meta/lib/oe/utils.py", line 272, in run
>
>     ret = self._target(*self._args, **self._kwargs)
>
>   File "/home/edson/ng-trunk/poky/meta/classes/package_ipk.bbclass", line
> 230, in ipk_write_pkg
>
>     shell=True)
>
>   File
> "/opt/poky/2.7/sysroots/x86_64-pokysdk-linux/usr/lib/python3.7/subprocess.py",
> line 395, in check_output
>
>     **kwargs).stdout
>
>   File
> "/opt/poky/2.7/sysroots/x86_64-pokysdk-linux/usr/lib/python3.7/subprocess.py",
> line 487, in run
>
>     output=stdout, stderr=stderr)
>
> subprocess.CalledProcessError: Command
> 'PATH="/home/edson/ng-trunk/nodegrid/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/edson/ng-trunk/poky/scripts:/home/edson/ng-trunk/nodegrid/tmp/work/core2-64-poky-linux/dockerode/2.5.8-r0/recipe-sysroot-native/usr/bin/x86_64-poky-linux:/home/edson/ng-trunk/nodegrid/tmp/work/core2-64-poky-linux/dockerode/2.5.8-r0/recipe-sysroot/usr/bin/crossscripts:/home/edson/ng-trunk/nodegrid/tmp/work/core2-64-poky-linux/dockerode/2.5.8-r0/recipe-sysroot-native/usr/sbin:/home/edson/ng-trunk/nodegrid/tmp/work/core2-64-poky-linux/dockerode/2.5.8-r0/recipe-sysroot-native/usr/bin:/home/edson/ng-trunk/nodegrid/tmp/work/core2-64-poky-linux/dockerode/2.5.8-r0/recipe-sysroot-native/sbin:/home/edson/ng-trunk/nodegrid/tmp/work/core2-64-poky-linux/dockerode/2.5.8-r0/recipe-sysroot-native/bin:/home/edson/ng-trunk/poky/bitbake/bin:/home/edson/ng-trunk/nodegrid/tmp/hosttools"
> opkg-build -Z xz -a "--memlimit=50% --threads=4" dockerode-JSONStream
> /home/edson/ng-trunk/nodegrid/tmp/work/core2-64-poky-linux/dockerode/2.5.8-r0/deploy-ipks/core2-64'
> returned non-zero exit status 1.
>
>
>
> *ERROR*: dockerode-2.5.8-r0 do_package_write_ipk:
>
> *ERROR*: dockerode-2.5.8-r0 do_package_write_ipk: Function failed:
> do_package_ipk
>
> *ERROR*: Logfile of failure stored in:
> /home/edson/ng-trunk/nodegrid/tmp/work/core2-64-poky-linux/dockerode/2.5.8-r0/temp/log.do_package_write_ipk.4213
>
> *ERROR*: Task
> (/home/edson/ng-trunk/meta-extended/meta-oe/recipes-npm/dockerode/dockerode_2.5.8.bb:do_package_write_ipk)
> failed with exit code '1'
>
> *NOTE*: Tasks Summary: Attempted 1357 tasks of which 1344 didn't need to
> be rerun and 1 failed.
>
> ======== IPK's generated until the error =======
>
> cd tmp/work/core2-64-poky-linux/dockerode/2.5.8-r0/packages-split/
>
> *edson@ubuntu-16*:*packages-split*$ ls
>
> *dockerode*                       *dockerode-docker-modem-readable-stream*
>   *dockerode-readable-stream*
>
> *dockerode-bl*                    *dockerode-docker-modem-string-decoder*
>   *dockerode-safe-buffer*
>
> *dockerode-buffer-alloc*          *dockerode-end-of-stream*
>   *dockerode-split-ca*
>
> *dockerode-buffer-alloc-unsafe*   *dockerode-fs-constants*
>   *dockerode-src*
>
> *dockerode-buffer-fill*           *dockerode-inherits*
>   *dockerode-staticdev*
>
> *dockerode-buffer-from*           *dockerode-isarray*
>   *dockerode-string-decoder*
>
> *dockerode-chownr*                *dockerode-jsonparse*
>   *dockerode-tar-fs*
>
> *dockerode-concat-stream*         *dockerode-JSONStream*
>   *dockerode-tar-stream*
>
> *dockerode-core-util-is*          *dockerode-locale*
>   *dockerode-through*
>
> *dockerode-dbg*                   *dockerode-minimist*
>   *dockerode-to-buffer*
>
> *dockerode-debug*                 *dockerode-mkdirp*
>   *dockerode-typedarray*
>
> *dockerode-dev*                   *dockerode-ms*
>   *dockerode-util-deprecate*
>
> *dockerode-doc*                   *dockerode-once*
>   *dockerode-wrappy*
>
> *dockerode-docker-modem*          *dockerode-process-nextick-args*
>   *dockerode-xtend*
>
> *dockerode-docker-modem-isarray*  *dockerode-pump*
>
> *edson@ubuntu-16*:*packages-split*$
>
> NOTE. building dockerode with morty only one ipk is generated:
>
> edson@NodeGrid-CustomKit-SDK:nodegrid$ ls
> tmp/deploy/ipk/core2-64/dockerode*.ipk
>
> tmp/deploy/ipk/core2-64/dockerode_2.4.3-r0_core2-64.ipk
>
> tmp/deploy/ipk/core2-64/dockerode-dbg_2.4.3-r0_core2-64.ipk
>
> tmp/deploy/ipk/core2-64/dockerode-dev_2.4.3-r0_core2-64.ipk
>
> Thanks in advance.
>
>
> Edson Seabra
>
> Principal Engineer
>
> M +1 510 579 0843
> *E   *edson.sea...@zpesystems.com <alvin.c...@zpesystems.com>
>
> [image:
> 1506169147061_OutlookEmoji-1505330244060_ZPELogo_Email.png1e6c5898-d340-4c90-8c28-e559c26bc7d1.png]
> 46757 Fremont Blvd., Fremont, CA 94538
> <https://maps.google.com/?q=46757+Fremont+Blvd.,+Fremont,+CA+94538&entry=gmail&source=g>
> *zpesystems.com* <https://www.zpesystems.com/>* | **Request a Nodegrid
> Demo <https://www.zpesystems.com/demo/>*
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>
-- 
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Reply via email to