Re: [yocto] [meta-intel] ERROR: - package networkmanager-1.10.6-r0.aarch64 conflicts with connman provided by connman-1.35-r0.aarch64
You'll have to not install either connman or network manager. Ross On Tue, 15 Jan 2019 at 05:18, srinivasan wrote: > > Dear Yocto experts, > > I am seeing the below error when I am trying to integrate the > "fsl-image-validation-imx.bb" into my custom yocto build and trigger > the build using "bitbake custom-image-debug-imx8.bb", I somewhat feel > networkmanager is conflicting with conman, could you please let me > know how this issue can be resolved? > > I have attached the recipe files for your information > > Error: > > ERROR: custom-image-debug-imx8-1.0-r0 do_rootfs: Could not invoke dnf. > Command > '/home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/recipe-sysroot-native/usr/bin/dnf > -y -c > /home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/rootfs/etc/dnf/dnf.conf > --setopt=reposdir=/home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/rootfs/etc/yum.repos.d > --repofrompath=oe-repo,/home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/oe-rootfs-repo > --installroot=/home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/rootfs > --setopt=logdir=/home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/temp > --nogpgcheck install alsa-server alsa-tools alsa-utils apt apt-repo > bash basicquick bc binutils binutils-symlinks bmap-tools-git > build-config bzip2 cmake coreutils crashme crda dfu-util diffutils dnf > dnsmasq ethtool file libfreetype6 gdb gdbserver gettext git > glibc-gconv-utf-32 gnupg libharfbuzz0 hidapi hostapd htop iperf3 iw > kernel-dev kernel-devsrc kernel-modules ldd libasound liberation-fonts > libfftw libfftwf libjack libjpeg62 libpng16-16 libtool libxerces-c > libsensors4 lmsensors-sensors lsof lttng-modules make memtester > merge-files nano networkmanager ni-isolcpus ninja openssl > packagegroup-base-extended packagegroup-core-boot > packagegroup-core-full-cmdline packagegroup-core-sdk > packagegroup-core-ssh-dropbear packagegroup-core-standalone-sdk-target > packagegroup-core-tools-debug packagegroup-core-tools-profile > packagegroup-core-tools-testapps packagegroup-fsl-optee-imx > packagegroup-fsl-tools-audio packagegroup-fsl-tools-gpu-external > packagegroup-tools-bluetooth pbzip2 pciutils perf pkgconfig procps > psplash python python-dbus python-modules python-pandas python-pip > python3 python3-dbus python3-misc python3-modules python3-pip > python3-psutil python3-robotframework python3-six qt3d qt3d-dev > qt3d-mkspecs qtbase qtbase-dev qtbase-mkspecs qtbase-plugins > qtbase-tools libqt5charts5 libqt5charts-dev libqt5charts-mkspecs > qtconnectivity-dev qtconnectivity-mkspecs qtdeclarative > qtdeclarative-dev qtdeclarative-mkspecs qtgraphicaleffects > qtgraphicaleffects-dev qtquickcontrols qtquickcontrols-dev > qtquickcontrols-qmlplugins qtquickcontrols2 qtquickcontrols2-dev > qtquickcontrols2-mkspecs libqt5svg5 libqt5svg-dev libqt5svg-mkspecs > rpm rt-tests rtirq run-postinsts screen ssh-keys-server strace stress > sysstat tar tmux trace-cmd ttf-bitstream-vera udev udev-automount > unzip usbreset usbutils util-linux valgrind wget wireless-tools > wpa-supplicant zip libz1 locale-base-en-us' returned 1: > Added oe-repo repo from > /home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/oe-rootfs-repo > Last metadata expiration check: 0:00:00 ago on Mon 14 Jan 2019 04:06:18 PM > UTC. > Error: > Problem: package connman-tools-1.35-r0.aarch64 requires connman, but > none of the providers can be installed > - package packagegroup-core-tools-testapps-1.0-r2.imx8mmevk requires > connman-tools, but none of the providers can be installed > - package networkmanager-1.10.6-r0.aarch64 conflicts with connman > provided by connman-1.35-r0.aarch64 > - conflicting requests > (try to add '--allowerasing' to command line to replace conflicting > packages or '--skip-broken' to skip uninstallable packages) > > ERROR: custom-image-debug-imx8-1.0-r0 do_rootfs: Function failed: do_rootfs > ERROR: Logfile of failure stored in: > /home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/temp/log.do_rootfs.56617 > ERROR: Task > (/home/user/test/os/sources/meta-custom-imx8/recipes-core/images/custom-image-debug-imx8.bb:do_rootfs) > failed with exit code '1' > NOTE: Tasks Summary: Attempted 8016 tasks of which 7974 didn't need to > be rerun and 1 failed. > > Many Thanks in advance, > -- > ___ > meta-intel mailing list > meta-in...@yoctoproject.org > https://lists.yoctoproject.org/listinfo/meta-intel -- ___ yocto mailing list yocto@yoctoproject.org https://li
Re: [yocto] bitbake: DataSmart.expandWithRefs causing exception when handed "${@...}"
On Sun, 2019-01-13 at 22:53 +0100, Ulf Samuelsson wrote:
> I am trying to add a new image class "SWU" in "sumo" for a "software
> update image".
> As a result:
> do_sdk_depends[depends] = '${@get_ext_sdk_depends(d)} meta-extsdk-
> toolchain:do_populate_sysroot'
>
> When data_smart.py works on this, it will call
>
> DataSmart.expandWithRefs(self, s, varname)
> s= '${@get_ext_sdk_depends(d)} meta-extsdk-
> toolchain:do_populate_sysroot'
> varname = 'do_sdk_depends[depends]'
>
> I will get an exception in this statement:
>
> while s.find('${') != -1:
> olds = s
> try:
> s = __expand_var_regexp__.sub(varparse.var_sub, s)
>
> The definition of __expand_var_regexp__ is:
> __expand_var_regexp__ = re.compile(r"\${[^{}@\n\t :]+}")
>
> That is, it is looking for the string "${}"
> but may not contains anything in [{}@\n\t :]
>
> since the "variable" in "s" is actually a call to
> get_ext_sdk_depends,
> and thus contains a '@' character it is not matched.
>
> The build aborts with an exception.
>
> I am not sure, if '${@get_ext_sdk_depends(d)}' should be expanded
> before
> DataSmart,expandWithRefs, or if expandWithRefs needs to be extended
> to handle the case where the variable is a "call".
>
> This is blocking us from upgrading from pyro to sumo.
>
> Any ideas on a solution?
Can you firstly say what the error is you're seeing. Your attempt to
understand it is good but I'm not sure which error you see?
Secondly, is there a way someone else could reproduce this bug?
The fragment you quote looks correct. If you have variable and function
names conflicting that would be a problem though as they're all in the
same namespace. I'm unclear whether that is a problem here or not
though based on the available information.
Cheers,
Richard
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Python upgrade path?
On Thu, Jan 3, 2019 at 5:36 AM Alexander Kanavin wrote: > On Thu, 3 Jan 2019 at 10:11, Derek Dresser wrote: > > I have an application that uses features introduced in Python 3.6, so I > am trying to add a new version of Python to my Yocto build. I know that > 3.5.6 is the latest version of Python that has been included in a Yocto > release. I found the patches here > > https://patchwork.openembedded.org/series/14778/ > > and was able to build Python3.7.1 for the commit specified in the > patch. I looked briefly at rebasing the patches on the Thud branch, but I > think that is beyond my current Python and Yocto capabilities. > > > > Are there any paths forward for me to get a newer version of Python > using Yocto? Would it be possible for me to use a package created from > that patched build and integrate it with my current thud build? Are there > any other workarounds I could use until a newer version of Python is > supported? > > > > I'd be happy to spend some time on this if I could help move this > forward, but I don't think this is something I can do by myself at this > point. I'm quite new to Yocto. > > Sadly there is no good answer. There are patches, but they need > further work (see oe-core list for details). Worse yet, thud is likely > to stay with 3.5, as such drastic version upgrades are usually not > done in stable branches (you are still free to do it via a custom > layer with backported recipes though). > > If you can take solving the issues and getting py 3.7 merged into > master as an exercise, this would be greatly appreciated by everyone, > and would take you out of 'new to yocto' :) > > > Alex > Thanks for the response. I will take a look at getting 3.7 to build, but I'd benefit from some guidance on the process to do so. I was able to get the patches to build on the specified commit that they target (although I just tried again and ran into some issues. I'll have to figure out what I did the first time.) This is what I did. 1. download patches from https://patchwork.openembedded.org/series/14778/ 2. checkout poky at specified commit "e349b239c8833bcdad9b1ff1a0702ace2db71959" 3. apply patch 4. bitbake python3 I then tried to rebase the patches on the master branch and ran into many merge conflicts that I didn't really have the context to resolve. I believe that is where I'll have to dig in to get things working. My questions are, is that a reasonable process? Is there a better process using devtool or something? Any guidance is appreciated. Thanks, Derek -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] ERROR: - package networkmanager-1.10.6-r0.aarch64 conflicts with connman provided by connman-1.35-r0.aarch64
Dear Yocto experts, I am seeing the below error when I am trying to integrate the "fsl-image-validation-imx.bb" into my custom yocto build and trigger the build using "bitbake custom-image-debug-imx8.bb", I somewhat feel networkmanager is conflicting with conman, could you please let me know how this issue can be resolved? I have attached the recipe files for your information Error: ERROR: custom-image-debug-imx8-1.0-r0 do_rootfs: Could not invoke dnf. Command '/home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/recipe-sysroot-native/usr/bin/dnf -y -c /home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/rootfs/etc/dnf/dnf.conf --setopt=reposdir=/home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/rootfs/etc/yum.repos.d --repofrompath=oe-repo,/home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/oe-rootfs-repo --installroot=/home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/rootfs --setopt=logdir=/home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/temp --nogpgcheck install alsa-server alsa-tools alsa-utils apt apt-repo bash basicquick bc binutils binutils-symlinks bmap-tools-git build-config bzip2 cmake coreutils crashme crda dfu-util diffutils dnf dnsmasq ethtool file libfreetype6 gdb gdbserver gettext git glibc-gconv-utf-32 gnupg libharfbuzz0 hidapi hostapd htop iperf3 iw kernel-dev kernel-devsrc kernel-modules ldd libasound liberation-fonts libfftw libfftwf libjack libjpeg62 libpng16-16 libtool libxerces-c libsensors4 lmsensors-sensors lsof lttng-modules make memtester merge-files nano networkmanager ni-isolcpus ninja openssl packagegroup-base-extended packagegroup-core-boot packagegroup-core-full-cmdline packagegroup-core-sdk packagegroup-core-ssh-dropbear packagegroup-core-standalone-sdk-target packagegroup-core-tools-debug packagegroup-core-tools-profile packagegroup-core-tools-testapps packagegroup-fsl-optee-imx packagegroup-fsl-tools-audio packagegroup-fsl-tools-gpu-external packagegroup-tools-bluetooth pbzip2 pciutils perf pkgconfig procps psplash python python-dbus python-modules python-pandas python-pip python3 python3-dbus python3-misc python3-modules python3-pip python3-psutil python3-robotframework python3-six qt3d qt3d-dev qt3d-mkspecs qtbase qtbase-dev qtbase-mkspecs qtbase-plugins qtbase-tools libqt5charts5 libqt5charts-dev libqt5charts-mkspecs qtconnectivity-dev qtconnectivity-mkspecs qtdeclarative qtdeclarative-dev qtdeclarative-mkspecs qtgraphicaleffects qtgraphicaleffects-dev qtquickcontrols qtquickcontrols-dev qtquickcontrols-qmlplugins qtquickcontrols2 qtquickcontrols2-dev qtquickcontrols2-mkspecs libqt5svg5 libqt5svg-dev libqt5svg-mkspecs rpm rt-tests rtirq run-postinsts screen ssh-keys-server strace stress sysstat tar tmux trace-cmd ttf-bitstream-vera udev udev-automount unzip usbreset usbutils util-linux valgrind wget wireless-tools wpa-supplicant zip libz1 locale-base-en-us' returned 1: Added oe-repo repo from /home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/oe-rootfs-repo Last metadata expiration check: 0:00:00 ago on Mon 14 Jan 2019 04:06:18 PM UTC. Error: Problem: package connman-tools-1.35-r0.aarch64 requires connman, but none of the providers can be installed - package packagegroup-core-tools-testapps-1.0-r2.imx8mmevk requires connman-tools, but none of the providers can be installed - package networkmanager-1.10.6-r0.aarch64 conflicts with connman provided by connman-1.35-r0.aarch64 - conflicting requests (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages) ERROR: custom-image-debug-imx8-1.0-r0 do_rootfs: Function failed: do_rootfs ERROR: Logfile of failure stored in: /home/user/test/os/build_fsl-image-validation-imx/tmp/work/imx8mmevk-poky-linux/custom-image-debug-imx8/1.0-r0/temp/log.do_rootfs.56617 ERROR: Task (/home/user/test/os/sources/meta-custom-imx8/recipes-core/images/custom-image-debug-imx8.bb:do_rootfs) failed with exit code '1' NOTE: Tasks Summary: Attempted 8016 tasks of which 7974 didn't need to be rerun and 1 failed. Many Thanks in advance, fsl-image-validation-imx.bb Description: Binary data custom-image-debug-imx8.bb Description: Binary data custom-image-debug.bbclass Description: Binary data -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Qemu Launch Issue:
Hi Team, I'm new to yocto environment, I need clarification on this: Launching Qemu default and launching by using "-nographic" option makes any difference. Please clarify this. Regards, Kumar -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [documentation][PATCH] documentation: remove True option to getVar calls
From: André Draszik
getVar() has been defaulting to expanding by default for
a long time (2016), thus remove the True option from
getVar() examples with a regex search and replace.
Search & replace made using the following command:
sed -e 's|\(d\.getVar \?\)( \?\([^,()]*\), \?True)|\1(\2)|g' \
-i $(git grep -E 'getVar ?\( ?([^,()]*), ?True\)' \
| cut -d':' -f1 \
| sort -u)
Note that there are are several other examples of getVar()
usage which already don't explicitly add the True option,
this patch just align some stray remainders.
Signed-off-by: André Draszik
---
documentation/dev-manual/dev-manual-common-tasks.xml | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml
b/documentation/dev-manual/dev-manual-common-tasks.xml
index c75e718d67..af0e4d53bf 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -5116,15 +5116,15 @@
So, commands such as the following are useful when exploring the
data
store and running functions:
- pydevshell> d.getVar("STAGING_DIR", True)
+ pydevshell> d.getVar("STAGING_DIR")
'/media/build1/poky/build/tmp/sysroots'
- pydevshell> d.getVar("STAGING_DIR", False)
+ pydevshell> d.getVar("STAGING_DIR")
'${TMPDIR}/sysroots'
pydevshell> d.setVar("FOO", "bar")
- pydevshell> d.getVar("FOO", True)
+ pydevshell> d.getVar("FOO")
'bar'
pydevshell> d.delVar("FOO")
- pydevshell> d.getVar("FOO", True)
+ pydevshell> d.getVar("FOO")
pydevshell> bb.build.exec_func("do_unpack", d)
pydevshell>
@@ -6892,8 +6892,8 @@
MACHINE = "qemux86-64"
DEFAULTTUNE = "x86-64-x32"
- baselib = "${@d.getVar('BASE_LIB_tune-' + (d.getVar('DEFAULTTUNE', True) \
-or 'INVALID'), True) or 'lib'}"
+ baselib = "${@d.getVar('BASE_LIB_tune-' + (d.getVar('DEFAULTTUNE') \
+or 'INVALID')) or 'lib'}"
Once you have set up your configuration file, use BitBake to
build an image that supports the x32 psABI.
--
2.20.1
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-poky][PATCH] meta-poky: remove True option to getVar calls
From: André Draszik
A couple have still been missed in the past despite multiple
attempts at doing so (or simply have re-appeared?).
Search made using the following command:
git grep -E 'getVar ?\(([^,)]*), True\)'
Signed-off-by: André Draszik
---
meta-poky/classes/poky-sanity.bbclass | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/meta-poky/classes/poky-sanity.bbclass
b/meta-poky/classes/poky-sanity.bbclass
index 81cd2eb6a6..a068c7368c 100644
--- a/meta-poky/classes/poky-sanity.bbclass
+++ b/meta-poky/classes/poky-sanity.bbclass
@@ -1,8 +1,8 @@
# Provide some extensions to sanity.bbclass to handle poky-specific conf file
upgrades
python poky_update_bblayersconf() {
-current_version = int(d.getVar('POKY_BBLAYERS_CONF_VERSION', True) or -1)
-latest_version = int(d.getVar('REQUIRED_POKY_BBLAYERS_CONF_VERSION', True)
or -1)
+current_version = int(d.getVar('POKY_BBLAYERS_CONF_VERSION') or -1)
+latest_version = int(d.getVar('REQUIRED_POKY_BBLAYERS_CONF_VERSION') or -1)
if current_version == -1 or latest_version == -1:
# one or the other missing => malformed configuration
raise NotImplementedError("You need to update bblayers.conf manually
for this version transition")
@@ -11,7 +11,7 @@ python poky_update_bblayersconf() {
# check for out of date templateconf.cfg file
lines = []
-fn = os.path.join(d.getVar('TOPDIR', True), 'conf/templateconf.cfg')
+fn = os.path.join(d.getVar('TOPDIR'), 'conf/templateconf.cfg')
lines = sanity_conf_read(fn)
index, meta_yocto_line = sanity_conf_find_line(r'^meta-yocto/', lines)
--
2.20.1
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Qemu Launch Issue:
On 1/15/19 5:54 AM, sadu A wrote: Hi Team, I'm new to yocto environment, I need clarification on this: Launching Qemu default and launching by using "-nographic" option makes any difference. Please clarify this. Using: $ runqemu nographic is useful when you have logged into a server and you don't want to allow X11 forwarding to your workstation/laptop. See: google: qemu nographic for example: https://serverfault.com/questions/471719/how-to-start-qemu-directly-in-the-console-not-in-curses-or-sdl for details. ../Randy Regards, Kumar -- # Randy MacLeod # Wind River Linux -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Yocto Project Status WW03'19
Current Dev Position: YP 2.7 M2 Next Deadline: YP 2.7 M2 Cutoff is Jan. 21, 2019 SWAT Team Rotation: * SWAT lead is currently: Paul * SWAT team rotation: Paul -> Chen on Jan. 18, 2019 * SWAT team rotation: Chen -> Armin on Jan. 25, 2019 * https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team Key Status/Updates: * YP 2.7 M1 was released on Jan. 10, 2019 * YP 2.6.1 is in QA and 79% complete. See: https://wiki.yoctoproject.org/wiki/2.6_QA_Status * We merged the perl changes and version upgrade. This exposed some race issues but we're hoping those have now been resolved. Thanks AlexK! This may cause fallout for perl module recipes in other layers. * There is a proposed patchset to add GL passthrough support for qemu, feedback on the proposals is welcome. There are build time performance implications, particularly due to the use of gtk3+-native. * There is a -dev kernel recipe for the Linux 5.0 kernel, thanks Bruce. * M2 cutoff is next week! Planned Releases for YP 2.7: * YP 2.7 M2 Cutoff is Jan. 21, 2019 * YP 2.7 M2 Release Target is Feb. 1, 2019 * YP 2.7 M3 Cutoff is Feb. 25, 2019 * YP 2.7 M3 Release Target is Mar. 8, 2019 * YP 2.7 M4 Cutoff is Apr. 1, 2019 * YP 2.7 M4 Release Target is Apr. 26, 2019 Planned upcoming dot releases: * YP 2.6.1 (Thud) will is in QA. * YP 2.5.3 (Sumo) will be targeted after YP 2.7 M2 is done. * YP 2.5.4 (Sumo) will be targeted after YP 2.7 M4 is done. * YP 2.6.2 (Thud) will be targeted after YP 2.5.4 is done. Tracking Metrics: * WDD 2391 (last week 2364) (https://wiki.yoctoproject.org/charts/combo.html) * Poky Patch Metrics oTotal patches found: 1565 (last week 1618) oPatches in the Pending State: 667 (43%) [last week 718 (44%)] Key Status Links for YP: https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.7_Status https://wiki.yoctoproject.org/wiki/Yocto_2.7_Schedule https://wiki.yoctoproject.org/wiki/Yocto_2.7_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] Updated meta-darwin, OSX Toolchain
Hi All, The current meta-darwin layer is outdated and cannot be used with the current Yocto releases. http://git.yoctoproject.org/cgit/cgit.cgi/meta-darwin/log/ I have created a working layer for OSX toolchain support in the repository liked below. It is based upon the original layer, but most recipes needed to be adjusted. We are using it with the latest Sumo release. I have not tested it with Thud yet. https://bitbucket.org/dominikschnitzer/meta-darwin/ If there is interest in upsteaming these changes, I am happy to either provide patches/work on the meta-darwin repo itself or just continue working on the bitbucket git repo. BR, Dominik -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [documentation][PATCH] documentation: remove True option to getVar calls
Hi Andre,
Thanks for the patch. See
http://www.yoctoproject.org/docs/2.7/dev-manual/dev-manual.html#platdev-appdev-devpyshell
and
http://www.yoctoproject.org/docs/2.7/dev-manual/dev-manual.html#using-x32-psabi
sections for the changes.
Thanks,
Scott Rifenbark
On Tue, Jan 15, 2019 at 7:03 AM André Draszik wrote:
> From: André Draszik
>
> getVar() has been defaulting to expanding by default for
> a long time (2016), thus remove the True option from
> getVar() examples with a regex search and replace.
>
> Search & replace made using the following command:
> sed -e 's|\(d\.getVar \?\)( \?\([^,()]*\), \?True)|\1(\2)|g' \
> -i $(git grep -E 'getVar ?\( ?([^,()]*), ?True\)' \
> | cut -d':' -f1 \
> | sort -u)
>
> Note that there are are several other examples of getVar()
> usage which already don't explicitly add the True option,
> this patch just align some stray remainders.
>
> Signed-off-by: André Draszik
> ---
> documentation/dev-manual/dev-manual-common-tasks.xml | 12 ++--
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml
> b/documentation/dev-manual/dev-manual-common-tasks.xml
> index c75e718d67..af0e4d53bf 100644
> --- a/documentation/dev-manual/dev-manual-common-tasks.xml
> +++ b/documentation/dev-manual/dev-manual-common-tasks.xml
> @@ -5116,15 +5116,15 @@
> So, commands such as the following are useful when exploring
> the data
> store and running functions:
>
> - pydevshell> d.getVar("STAGING_DIR", True)
> + pydevshell> d.getVar("STAGING_DIR")
> '/media/build1/poky/build/tmp/sysroots'
> - pydevshell> d.getVar("STAGING_DIR", False)
> + pydevshell> d.getVar("STAGING_DIR")
> '${TMPDIR}/sysroots'
> pydevshell> d.setVar("FOO", "bar")
> - pydevshell> d.getVar("FOO", True)
> + pydevshell> d.getVar("FOO")
> 'bar'
> pydevshell> d.delVar("FOO")
> - pydevshell> d.getVar("FOO", True)
> + pydevshell> d.getVar("FOO")
> pydevshell> bb.build.exec_func("do_unpack", d)
> pydevshell>
>
> @@ -6892,8 +6892,8 @@
>
> MACHINE = "qemux86-64"
> DEFAULTTUNE = "x86-64-x32"
> - baselib = "${@d.getVar('BASE_LIB_tune-' + (d.getVar('DEFAULTTUNE',
> True) \
> -or 'INVALID'), True) or 'lib'}"
> + baselib = "${@d.getVar('BASE_LIB_tune-' + (d.getVar('DEFAULTTUNE') \
> +or 'INVALID')) or 'lib'}"
>
> Once you have set up your configuration file, use BitBake to
> build an image that supports the x32 psABI.
> --
> 2.20.1
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Updated meta-darwin, OSX Toolchain
There is definitely interest, please submit your patches to the list. Send enough quality patches and you could become the official maintainer, as meta-darwin is currently missing one (which is why it bitrotted). Ross On Tue, 15 Jan 2019 at 20:09, Dominik Schnitzer wrote: > > Hi All, > > The current meta-darwin layer is outdated and cannot be used with the current > Yocto releases. > http://git.yoctoproject.org/cgit/cgit.cgi/meta-darwin/log/ > > I have created a working layer for OSX toolchain support in the repository > liked below. It is based upon the original layer, but most recipes needed to > be adjusted. We are using it with the latest Sumo release. I have not tested > it with Thud yet. > > https://bitbucket.org/dominikschnitzer/meta-darwin/ > > If there is interest in upsteaming these changes, I am happy to either > provide patches/work on the meta-darwin repo itself or just continue working > on the bitbucket git repo. > > BR, > Dominik > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] bitbake: DataSmart.expandWithRefs causing exception when handed "${@...}"
Den 2019-01-15 kl. 14:38, skrev Richard Purdie:
On Sun, 2019-01-13 at 22:53 +0100, Ulf Samuelsson wrote:
I am trying to add a new image class "SWU" in "sumo" for a "software
update image".
As a result:
do_sdk_depends[depends] = '${@get_ext_sdk_depends(d)} meta-extsdk-
toolchain:do_populate_sysroot'
When data_smart.py works on this, it will call
DataSmart.expandWithRefs(self, s, varname)
s= '${@get_ext_sdk_depends(d)} meta-extsdk-
toolchain:do_populate_sysroot'
varname = 'do_sdk_depends[depends]'
I will get an exception in this statement:
while s.find('${') != -1:
olds = s
try:
s = __expand_var_regexp__.sub(varparse.var_sub, s)
The definition of __expand_var_regexp__ is:
__expand_var_regexp__ = re.compile(r"\${[^{}@\n\t :]+}")
That is, it is looking for the string "${}"
but may not contains anything in [{}@\n\t :]
since the "variable" in "s" is actually a call to
get_ext_sdk_depends,
and thus contains a '@' character it is not matched.
The build aborts with an exception.
I am not sure, if '${@get_ext_sdk_depends(d)}' should be expanded
before
DataSmart,expandWithRefs, or if expandWithRefs needs to be extended
to handle the case where the variable is a "call".
This is blocking us from upgrading from pyro to sumo.
Any ideas on a solution?
Can you firstly say what the error is you're seeing. Your attempt to
understand it is good but I'm not sure which error you see?
Secondly, is there a way someone else could reproduce this bug?
The fragment you quote looks correct. If you have variable and function
names conflicting that would be a problem though as they're all in the
same namespace. I'm unclear whether that is a problem here or not
though based on the available information.
Cheers,
Richard
I found the problem.
The "image_swu.bbclass" in the customer contained a statement:
"addtask do_packageswu after do_image_complete before do_image_qa"
The dependencies of the image recipe is:
do_fetch
do_prepare_recipe_sysroot:do_fetch
do_unpack:do_fetch
do_patch: do_unpack
do_populate_lic: do_patch
do_configure: do_patch
do_compile: do_configure
do_install: do_compile
do_package: do_install
do_package_data: do_package
do_rootfs:do_package_data \
do_prepare_recipe_sysroot \
do_populate_lic
1do_image_qa: do_rootfs
do_image: do_image_qa do_rootfs
do_image_tar: do_image
2do_image_complete:do_image_tar do_image
do_build do_image_complete \
do_package_data \
do_populate_lic
The addtask statement want something which is after (2) but before (1)
and bitbake responds by creating a circular dependency.
When I changed this to:
"addtask do_packageswu after do_image_ubifs before do_image_complete"
the build works.
(the swu image will work on a previously created file system, which
happens to be ubifs in this case)
I think a simple good improvement would be to have an addtask
check if this would create a circular dependency.
KNOWN_TASKS = [ 'do_fetch', 'do_unpack', ... , 'do_build' ]
# Some tasks which has a fuzzy order like do_prepare_recipe_sysroot
# may have to be omitted.
TASK_ORDER['do_fetch'] = 1
...
TASK_ORDER['do_build'] =
def circular(before, after)
if not before in KNOWN_TASKS
return false
if not after in KNOWN_TASKS:
return false
before_prio = TASK_ORDER[before]
after_prio = TASK_ORDER[after]
return after_prio > before_prio
This would at least catch the more common tasks, and would be quick,
since the particular recipe would not have to be parsed.
Where could such code be added (not used to hacking bitbake)?
A better implementation would of course analyze the specific recipe
before accepting the addtask statement.
--
Best Regards
Ulf Samuelsson
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH V2] patchwork: Add a dockerfile for deploy patchwork and patchtest
change in v2: run getmail in crontab Changqing Li (1): patchwork: Add a dockerfile for deploy patchwork and patchtest Dockerfile.pw | 52 +++ README.pw | 32 ++ requirements.txt | 12 ++ scripts/pw_createsuperuser.sh | 5 + scripts/pw_getmail.sh | 11 + scripts/pw_migrate.sh | 5 + scripts/pw_runwebserver.sh| 12 ++ 7 files changed, 129 insertions(+) create mode 100644 Dockerfile.pw create mode 100644 README.pw create mode 100644 requirements.txt create mode 100755 scripts/pw_createsuperuser.sh create mode 100755 scripts/pw_getmail.sh create mode 100755 scripts/pw_migrate.sh create mode 100755 scripts/pw_runwebserver.sh -- 2.7.4 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH V2] patchwork: Add a dockerfile for deploy patchwork and patchtest
From: Changqing Li Add a dockerfile for easy deploy patchwork and patchtest in docker Signed-off-by: Changqing Li --- Dockerfile.pw | 52 +++ README.pw | 32 ++ requirements.txt | 12 ++ scripts/pw_createsuperuser.sh | 5 + scripts/pw_getmail.sh | 11 + scripts/pw_migrate.sh | 5 + scripts/pw_runwebserver.sh| 12 ++ 7 files changed, 129 insertions(+) create mode 100644 Dockerfile.pw create mode 100644 README.pw create mode 100644 requirements.txt create mode 100755 scripts/pw_createsuperuser.sh create mode 100755 scripts/pw_getmail.sh create mode 100755 scripts/pw_migrate.sh create mode 100755 scripts/pw_runwebserver.sh diff --git a/Dockerfile.pw b/Dockerfile.pw new file mode 100644 index 000..ae3c1ee --- /dev/null +++ b/Dockerfile.pw @@ -0,0 +1,52 @@ +FROM ubuntu:latest +MAINTAINER owner + +EXPOSE 8080 + +ENV PYTHONUNBUFFERED=1 \ +LANG=en_US.UTF-8 \ +LC_ALL=en_US.UTF-8 \ +LC_CTYPE=en_US.UTF-8 \ +PATH="$PATH:/opt/patchwork/git-pw:/opt/patchtest:/opt/patchtest/scripts" + +RUN apt-get update \ +&& apt-get dist-upgrade -y \ +&& apt-get install -y --no-install-recommends \ +autoconf \ +gcc \ +g++ \ +make \ +locales \ +wget \ +curl \ +cron \ +python-pip \ +python-dev \ +python-setuptools \ +python3-pip \ +python3-dev \ +libmysqlclient-dev \ +git-core \ +getmail4 \ +&& sh -c "echo \"en_US.UTF-8 UTF-8\" >> /etc/locale.gen" \ +&& locale-gen en_US.UTF-8 \ +&& update-locale \ +&& pip2 install wheel \ +&& pip3 install wheel \ +&& pip3 install setuptools \ +&& apt-get autoremove --purge -y \ +&& rm -rf /var/lib/apt/lists/* \ +&& apt-get clean +ADD ./patchwork /opt/patchwork +ADD ./patchtest /opt/patchtest +ADD ./patchtest-oe /opt/patchtest-oe +ADD ./getmailrc /opt/getmail/getmailrc +RUN pip2 install -r /opt/patchwork/requirements.txt \ +&& pip3 install -r /opt/patchtest/requirements.txt \ +&& pip3 install -r /opt/patchtest-oe/requirements.txt \ +&& mkdir -p /opt/getmail \ +&& mkdir -p /opt/pw-logs \ +&& git config --global user.email "patcht...@patchtest.com" \ +&& git config --global user.name "patchtest" \ +&& /opt/patchtest/scripts/create-host-test-folder -t /opt/pw-test \ +&& /opt/patchtest/scripts/create-host-crontab -c /opt/pw-test-cron diff --git a/README.pw b/README.pw new file mode 100644 index 000..ffa7af1 --- /dev/null +++ b/README.pw @@ -0,0 +1,32 @@ +* Dockerfile.pw deploy patchwork, patchtest, patchtest-oe in docker + +* Dockerfile.pw is just an example, you can adjust according to your + deploy condition, like not use getmail, but use postfix. + +* requirements.txt, just for refer, you can also rewrite this + according to patchwork'doc and accoridng to your deploy condition. + +* scripts folder hold the files will be used during deploy with docker. + +* Deploy steps: + +1. Clone patchwork, patchtest, patchtest-oe first, also put getmailrc used by + Dockerfile.pw under the same folder. + +2. Build docker image with Dockerfile.pw +$docker build -t pw -f ./patchwork/Dockerfile.pw . + +3. use mariadb as dataserver: +$ docker pull mariadb +$ docker run -d --name pw-db -e MYSQL_ROOT_PASSWORD=123456 -e MYSQL_DATABASE=pwdb -v /pw/pwdb:/var/lib/mysql mariadb + +5. run web server +docker run -d --name pw-web --link pw-db:pw-db -p 8080:8080 pw "/opt/patchwork/scripts/pw_runwebserver.sh" + +6. config pw +docker exec -it pw-web /opt/patchwork/scripts/pw_migrate.sh +docker exec -it pw-web /opt/patchwork/scripts/pw_createsuperuser.sh + +7. run patchwork +docker run -d --name pw-mail --link pw-db:pw-db pw "/opt/patchwork/scripts/pw_getmail.sh" + diff --git a/requirements.txt b/requirements.txt new file mode 100644 index 000..b8f68f2 --- /dev/null +++ b/requirements.txt @@ -0,0 +1,12 @@ +django==1.8.0 +sqlparse==0.2.4 +celery==3.1.20 +django_filter==0.11.0 +djangorestframework==2.4.8 +drf-nested-routers==0.11.1 +psycopg2>=2.7,<2.8 +mysqlclient +jsonfield +enum34 +GitPython +requests diff --git a/scripts/pw_createsuperuser.sh b/scripts/pw_createsuperuser.sh new file mode 100755 index 000..324ce72 --- /dev/null +++ b/scripts/pw_createsuperuser.sh @@ -0,0 +1,5 @@ +#!/bin/bash + +pw_dir='/opt/patchwork' + +(cd $pw_dir; ./manage.py createsuperuser) diff --git a/scripts/pw_getmail.sh b/scripts/pw_getmail.sh new file mode 100755 index 000..fadf7c9 --- /dev/null +++ b/scripts/pw_getmail.sh @@ -0,0 +1,11 @@ +#!/bin/bash + +sudo /etc/init.d/cron start +echo "*/5 * * * * sudo getmail --getmaildir=/opt/getmail/ --idle INBOX >> /opt/pw-test-cron/getmail.log 2>&1" > /opt/pw-test-cron/cron-getmail +sudo crontab -u wrlbuild /opt/pw-test-cron/cron-getmail + +while
[yocto] Firewalld failing to build
Hello all, I've been attempting to build firewalld by adding it through 'devtool add ' and then 'devtool build firewalld'. However, I am stuck with the following errors. I have no idea what could be causing this. Could someone please help? xsltproc -o ../html/firewall-cmd.html --nonet --xinclude transform-html.xsl firewall-cmd.xml | xsltproc -o ../html/firewalld.dbus.html --nonet --xinclude transform-html.xsl ../../../../../../../../workspace/sources/firewalld/doc/xml/firewalld.dbus.xml | xsltproc -o ../html/firewalld.conf.html --nonet --xinclude transform-html.xsl ../../../../../../../../workspace/sources/firewalld/doc/xml/firewalld.conf.xml | xsltproc -o ../html/firewalld.html --nonet --xinclude transform-html.xsl firewalld.xml | 134 translated messages, 281 untranslated messages. | bn_IN: 293 translated messages, 122 untranslated messages. | ca: 415 translated messages. | cs: 415 translated messages. | da: warning: failed to load external entity "authors.xml" | firewall-cmd.xml:36: parser error : Failure to process entity authors | &authors; | ^ | firewall-cmd.xml:36: parser error : Entity 'authors' not defined | &authors; | ^ | warning: failed to load external entity "seealso.xml" | firewall-cmd.xml:2297: parser error : Failure to process entity seealso | &seealso; |^ | firewall-cmd.xml:2297: parser error : Entity 'seealso' not defined | &seealso; Thanks Sam. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH V2] patchtest: several enhancement for docker
change in V2: fix bug in pw-host-test change in V1: based on previous script guest, which run qemu, and run testcase in qemu, change to pw-host-test, change to run directly on host. and will be used by dockerfile in patchwork, detail deploy can refer change in patchwork for docker deployment. Changqing Li (1): patchtest: several enhancement requirements.txt| 2 + scripts/create-host-crontab | 88 +++ scripts/create-host-test-folder | 151 scripts/fetch-mboxes| 9 +- scripts/pw-host-test| 185 scripts/test-mboxes | 2 +- usage.adoc | 8 ++ 7 files changed, 442 insertions(+), 3 deletions(-) create mode 100755 scripts/create-host-crontab create mode 100755 scripts/create-host-test-folder create mode 100755 scripts/pw-host-test -- 2.7.4 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH V2] patchtest: several enhancement
From: Changqing Li
* since we need use git-pw in patchwork, and that need GitPython/
requests, so add them into requirements.txt
* fetch-mboxes: add option for supprt select which project to fetch
, not always use default oe-core for pull-events
* test-mboxes: crontab's stdin is not atty, curret way will make
patchtest get patch from stdin, but not the patch
downloaded to folder mboxes. Use pipe stdin way to
suppprt run test-mboxes in crontab
* pw-host-test/create-host-test-folder/create-host-crontab:
These scripts are for run test in docker, detail see
usage.adoc
Signed-off-by: Changqing Li
---
requirements.txt| 2 +
scripts/create-host-crontab | 88 +++
scripts/create-host-test-folder | 151
scripts/fetch-mboxes| 9 +-
scripts/pw-host-test| 185
scripts/test-mboxes | 2 +-
usage.adoc | 8 ++
7 files changed, 442 insertions(+), 3 deletions(-)
create mode 100755 scripts/create-host-crontab
create mode 100755 scripts/create-host-test-folder
create mode 100755 scripts/pw-host-test
diff --git a/requirements.txt b/requirements.txt
index 7f7afbf..62a4b5d 100644
--- a/requirements.txt
+++ b/requirements.txt
@@ -1 +1,3 @@
jinja2
+GitPython
+requests
diff --git a/scripts/create-host-crontab b/scripts/create-host-crontab
new file mode 100755
index 000..583955f
--- /dev/null
+++ b/scripts/create-host-crontab
@@ -0,0 +1,88 @@
+#!/usr/bin/env bash
+# ex:ts=4:sw=4:sts=4:et
+# -*- tab-width: 4; c-basic-offset: 4; indent-tabs-mode: nil -*-
+#
+# create-host-crontab: creates a crontab file used to run patchtest
+#
+# Copyright (C) 2016 Intel Corporation
+#
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License version 2 as
+# published by the Free Software Foundation.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License along
+# with this program; if not, write to the Free Software Foundation, Inc.,
+# 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
+#
+
+CRONDIR=$PWD
+FREQ='*/30 * * * *'
+
+function usage() {
+cat << EOF
+\$ $(basename $0) OPTIONS [SERIES]
+
+where OPTIONS are
+-c: Cron directory to place the crontab. Default:
'$CRONDIR'
+-f : Cron frequency: Default '$FREQ'
+
+EOF
+>&2
+
+exit 1
+}
+
+while getopts ":c:f:h" opt; do
+case $opt in
+ c)
+ CRONDIR=$OPTARG
+ ;;
+ f)
+ FREQ="$OPTARG"
+ ;;
+ \?)
+ echo "Invalid option: -$OPTARG" >&2
+ usage
+ ;;
+ :)
+ echo "Option -$OPTARG requires an argument." >&2
+ usage
+ ;;
+esac
+done
+shift $((OPTIND-1))
+
+# create crondir if necessary
+[ ! -d "$CRONDIR" ] && { mkdir -p $CRONDIR; }
+
+CRONDIR="$(readlink -e $CRONDIR)"
+
+# create crontab
+cat > $CRONDIR/cronenv << EOF
+#!/bin/sh
+#
+# Place any environment variables needed
+# before running 'guest' script
+#
+# include patch* repos into PATH
+PATH="/opt/patchwork/git-pw:/opt/patchtest:/opt/patchtest/scripts:\$PATH"
+
+# Possible settings if cron is run under a proxy
+#unset SSH_AUTH_SOCK
+#export GIT_PROXY_COMMAND=""
+#export ftp_proxy=""
+#export http_proxy=""
+#export https_proxy=""
+#export no_proxy=""
+EOF
+
+chmod +x $CRONDIR/cronenv
+
+cat > "$CRONDIR/crontab" <> $CRONDIR/cronlog 2>&1
+EOF
diff --git a/scripts/create-host-test-folder b/scripts/create-host-test-folder
new file mode 100755
index 000..464ba8a
--- /dev/null
+++ b/scripts/create-host-test-folder
@@ -0,0 +1,151 @@
+#!/usr/bin/env bash
+# ex:ts=4:sw=4:sts=4:et
+# -*- tab-width: 4; c-basic-offset: 4; indent-tabs-mode: nil -*-
+#
+# create-host-test-folder: Create a test folder on host
+#
+# Copyright (C) 2016 Intel Corporation
+#
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License version 2 as
+# published by the Free Software Foundation.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License along
+# with this program; if not, write to the Free Software Foundation, Inc.,
+# 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
+
+
+# defaults values
+TESTDIR=''
+PWURL='https://patchwork.openembedded.org'
+PWPRO='oe-core'
+P
