[yocto] Tracking changes in image
Hi, I want to be able to track different parts of my image, accessible from within userspace so I can programmatically (via an environment variable or something) what version of my patches have been applied. Ultimately, I want to be able to answer questions from the field to know 'what changed' in a deployed image. Is there already a method to do this? For example, our project has u-boot, a zImage and rootfs. Is there a way to tell the patched version (from my layer) for each of those so I can connect what is in the field to what is in my layer in version control? Thanks in advance -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Yocto Project Unassigned Bugs - Help Needed
All, 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 313 unassigned 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 three different "priority" classes right now, "2.6", "2.99" and "Future", the more pressing/urgent issues being in "2.6". 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 (stephen.k.jol...@intel.com) 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#Unassigned_Bugs 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] [meta-security][PATCH 1/1] keynote: add dependency on bison-native
bison/yacc is no longer automatically supplied. Signed-off-by: Joe Slater --- recipes-security/keynote/keynote_2.3.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/recipes-security/keynote/keynote_2.3.bb b/recipes-security/keynote/keynote_2.3.bb index e692485..0300894 100644 --- a/recipes-security/keynote/keynote_2.3.bb +++ b/recipes-security/keynote/keynote_2.3.bb @@ -23,7 +23,7 @@ inherit autotools-brokensep ptest SRC_URI[md5sum] = "a14553e6ad921b5c85026ce5bec3afe7" SRC_URI[sha256sum] = "38d2acfa1c3630a07adcb5c8fe92d2aef7f0e6d242b8998b2bbb1c6e4c408d46" -DEPENDS = "flex openssl" +DEPENDS = "flex openssl bison-native" EXTRA_OEMAKE += "test-sample -j1" -- 2.7.4 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [yocto-builds] Newbe first build failure
Welcome! We have a few (too many?) lists: https://www.yoctoproject.org/community/mailing-lists/ For general discussion, start on: yocto@yoctoproject.org On 08/26/2018 04:19 AM, Scott Wimberley wrote: First, thank you in advance for your help. After cloning poky, I entered: bitbake core-image-sato What branch are you using? https://wiki.yoctoproject.org/wiki/Releases For production work you should be using a recent stable branch such as yocto-2.5.1 which happens to also include a fix for this problem as described below. It went fine for quite awhile, but ultimately failed. I a using ubuntu 16.04 Here is the relevant output: NOTE: Fetching uninative binary shim from http://downloads.yoctoproject.org/releases/uninative/1.9/x86_64-nativesdk-libc.tar.bz2;sha256sum=c26622a1f27dbf5b25de986b11584b5c5b2f322d9eb367f705a744f58a5561ec Initialising tasks: 100% |##| Time: 0:00:07 NOTE: Executing SetScene Tasks NOTE: Executing RunQueue Tasks WARNING: bzip2-1.0.6-r5 do_fetch: Checksum mismatch for local file /home/scott/projects/yacto/poky/build/downloads/bzip2-1.0.6.tar.gz Cleaning and trying again. WARNING: bzip2-1.0.6-r5 do_fetch: Renaming /home/scott/projects/yacto/poky/build/downloads/bzip2-1.0.6.tar.gz to /home/scott/projects/yacto/poky/build/downloads/bzip2-1.0.6.tar.gz_bad-checksum_c043a22bb6ac55b54cb0827cb837bd61 WARNING: bzip2-1.0.6-r5 do_fetch: Checksum failure encountered with download of http://www.bzip.org/1.0.6/bzip2-1.0.6.tar.gz - will attempt other sources if available WARNING: shadow-4.2.1-r0 do_fetch: Failed to fetch URL http://pkg-shadow.alioth.debian.org/releases/shadow-4.2.1.tar.xz, attempting MIRRORS if available WARNING: chrpath-native-0.16-r0 do_fetch: Failed to fetch URL https://alioth.debian.org/frs/download.php/file/3979/chrpath-0.16.tar.gz, attempting MIRRORS if available WARNING: iso-codes-3.77-r0 do_fetch: Failed to fetch URL https://pkg-isocodes.alioth.debian.org/downloads/iso-codes-3.77.tar.xz, attempting MIRRORS if available ERROR: iso-codes-3.77-r0 do_fetch: Fetcher failure: Fetch command export PSEUDO_DISABLED=1; export DBUS_SESSION_BUS_ADDRESS="unix:abstract=/tmp/dbus-LVaJXG9LBf"; export SSH_AUTH_SOCK="/run/user/1000/keyring/ssh"; export PATH="/home/scott/projects/yacto/poky/build/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/scott/projects/yacto/poky/scripts:/home/scott/projects/yacto/poky/build/tmp/work/all-poky-linux/iso-codes/3.77-r0/recipe-sysroot-native/usr/bin/allarch-poky-linux:/home/scott/projects/yacto/poky/build/tmp/work/all-poky-linux/iso-codes/3.77-r0/recipe-sysroot/usr/bin/crossscripts:/home/scott/projects/yacto/poky/build/tmp/work/all-poky-linux/iso-codes/3.77-r0/recipe-sysroot-native/usr/sbin:/home/scott/projects/yacto/poky/build/tmp/work/all-poky-linux/iso-codes/3.77-r0/recipe-sysroot-native/usr/bin:/home/scott/projects/yacto/poky/build/tmp/work/all-poky-linux/iso-codes/3.77-r0/recipe-sysroot-native/sbin:/home/scott/projects/yacto/poky/build/tmp/work/all-poky-linux/iso-codes/3.77-r0/recipe-sysroot-native/bin:/home/scott/projects/yacto/poky/bitbake/bin:/home/scott/projects/yacto/poky/build/tmp/hosttools"; export HOME="/home/scott"; /usr/bin/env wget -t 2 -T 30 -nv --passive-ftp --no-check-certificate -P /home/scott/projects/yacto/poky/build/downloads 'https://pkg-isocodes.alioth.debian.org/downloads/iso-codes-3.77.tar.xz' --progress=dot -v failed with exit code 4, output: --2018-08-26 07:41:22-- https://pkg-isocodes.alioth.debian.org/downloads/iso-codes-3.77.tar.xz Resolving pkg-isocodes.alioth.debian.org (pkg-isocodes.alioth.debian.org)... failed: Name or service not known. wget: unable to resolve host address ‘pkg-isocodes.alioth.debian.org’ ERROR: iso-codes-3.77-r0 do_fetch: Fetcher failure for URL: 'https://pkg-isocodes.alioth.debian.org/downloads/iso-codes-3.77.tar.xz'. Unable to fetch URL from any source. Packages on the net move around, we've fixed this fetch problem and it's in the release tagged as: yocto-2.5.1 : https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?h=sumo&id=0f3409c19595d5fe7b1ffbf11dce651548808e6f Does that help? See below for what I did to confirm that the fetch really works. Basic stuff but you did say that you're a newbie! :) ../Randy $ git checkout yocto-2.5.1 $ git log -3 --oneline 24a833f40d (HEAD, tag: yocto-2.5.1, tag: sumo-19.0.1) build-appliance-image: Update to sumo head revision 2464dd4040 poky.conf: Bump version for sumo 2.5.1 22e02daa5b binutls: Security fix CVE-2018-10534 $ git tag --contains 0f3409c19 sumo-19.0.1 yocto-2.5.1 $ git branch --contains 0f3409c19 * (HEAD detached at yocto-2.5.1) sumo $ cd ../b $ . ../poky.git/oe-init-build-env iso $ bitbake -c fetch iso-codes ... $ echo $? 0 ../Randy ERROR: iso-codes-3.77-r0 do_fetch: Function failed: base_do_fetch ERROR: Logfile of failure stored in: /home/scott/projects/yacto/poky/build/tmp/work/al
Re: [yocto] [PATCH][meta-dpdk] dpdk-dev-libibverbs: fix do_fetch error
On 08/23/2018 04:40 PM, Changqing Li wrote:
>
>
> On 08/14/2018 10:27 AM, Anuj Mittal wrote:
>> On 08/14/2018 09:37 AM, Changqing Li wrote:
>>> On 08/13/2018 02:35 PM, Anuj Mittal wrote:
On 08/13/2018 01:22 PM, changqing...@windriver.com wrote:
> From: Changqing Li
>
> original URI have been deleted(don't know why). I noticed there is
> an official libibverbs(https://git.kernel.org/pub/scm/libs/infiniband
> /libibverbs.git),
The deprecation notice seems to imply that rdma-core on github should be
used instead and that's what debian does too. Perhaps that should be
used instead?
https://tracker.debian.org/pkg/rdma-core
>>> About you mentioned "deprecation notice " , I don't find it on original
>>> github of Mellanox
>>> can you send me a link of this notice? Thanks.
>> https://git.kernel.org/pub/scm/libs/infiniband/libibverbs.git/commit/?id=1a6ab7f4c4aa048e8cf0c6cbed5935181f660bd8
>>
>> And, this:
>>
>> https://www.openfabrics.org/downloads/verbs/README.html
>>
>>> besides, from https://tracker.debian.org/pkg/rdma-core, I can get the
>>> repo is here
>>> https://github.com/linux-rdma/rdma-core, but it is not only
>>> libibverbs, it is source
>>> include some other package, I think it is not proper here.
>>>
>> If you take a look at older version of libibverbs there, you'd see the
>> code that we had. The later versions are pulling from rdma-core.
>>
>> You don't need to install everything, just the things that are needed
>> for dpdk ...
>>
> Thanks. I checked oldest
> https://github.com/linux-rdma/rdma-core/tree/rdma-core-12/libibverbs,
> yes, it is ported from
> https://git.kernel.org/pub/scm/libs/infiniband/libibverbs.git.
>
> But my problem is current v19 of rdma-core/libibverbs have big
> difference with original tar
> libibverbs-1.2.1-3.4-2.0.0.0.tar.gz download from
> https://github.com/Mellanox/
> dpdk-dev-libibverbs/archive/libibverbs-${PV}.tar.gz, Include code
> structure, and compile way(autotool to cmake), and others
> Actually, oldest version rdma-core-12 already have code structure, and
> compile way change.
>
> I don't have condition to test the function of this lib and dpdk, I can
> only go far as build success.
> what I worried is upgrade with big difference without test maybe cause
> big problem.
>
> if we don't want to use tar on
> "https://autobuilder.yocto.io/pub/sources/", I propose who
> can test this to upgrade the SRC_URI to rdma-core/libibverbs.
>
Thank you for checking. Can you please edit the patch to point to yocto
project mirror (downloads.yoctoproject.org/mirror/sources) for now,
include the info that it should be replaced by libibverbs from rdma-core
in commit message and send the patch to meta-intel list?
Thanks,
Anuj
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH][meta-dpdk] dpdk-dev-libibverbs: fix do_fetch error
On 08/28/2018 09:42 AM, Anuj Mittal wrote:
On 08/23/2018 04:40 PM, Changqing Li wrote:
On 08/14/2018 10:27 AM, Anuj Mittal wrote:
On 08/14/2018 09:37 AM, Changqing Li wrote:
On 08/13/2018 02:35 PM, Anuj Mittal wrote:
On 08/13/2018 01:22 PM, changqing...@windriver.com wrote:
From: Changqing Li
original URI have been deleted(don't know why). I noticed there is
an official libibverbs(https://git.kernel.org/pub/scm/libs/infiniband
/libibverbs.git),
The deprecation notice seems to imply that rdma-core on github should be
used instead and that's what debian does too. Perhaps that should be
used instead?
https://tracker.debian.org/pkg/rdma-core
About you mentioned "deprecation notice " , I don't find it on original
github of Mellanox
can you send me a link of this notice? Thanks.
https://git.kernel.org/pub/scm/libs/infiniband/libibverbs.git/commit/?id=1a6ab7f4c4aa048e8cf0c6cbed5935181f660bd8
And, this:
https://www.openfabrics.org/downloads/verbs/README.html
besides, from https://tracker.debian.org/pkg/rdma-core, I can get the
repo is here
https://github.com/linux-rdma/rdma-core, but it is not only
libibverbs, it is source
include some other package, I think it is not proper here.
If you take a look at older version of libibverbs there, you'd see the
code that we had. The later versions are pulling from rdma-core.
You don't need to install everything, just the things that are needed
for dpdk ...
Thanks. I checked oldest
https://github.com/linux-rdma/rdma-core/tree/rdma-core-12/libibverbs,
yes, it is ported from
https://git.kernel.org/pub/scm/libs/infiniband/libibverbs.git.
But my problem is current v19 of rdma-core/libibverbs have big
difference with original tar
libibverbs-1.2.1-3.4-2.0.0.0.tar.gz download from
https://github.com/Mellanox/
dpdk-dev-libibverbs/archive/libibverbs-${PV}.tar.gz, Include code
structure, and compile way(autotool to cmake), and others
Actually, oldest version rdma-core-12 already have code structure, and
compile way change.
I don't have condition to test the function of this lib and dpdk, I can
only go far as build success.
what I worried is upgrade with big difference without test maybe cause
big problem.
if we don't want to use tar on
"https://autobuilder.yocto.io/pub/sources/", I propose who
can test this to upgrade the SRC_URI to rdma-core/libibverbs.
Thank you for checking. Can you please edit the patch to point to yocto
project mirror (downloads.yoctoproject.org/mirror/sources) for now,
include the info that it should be replaced by libibverbs from rdma-core
in commit message and send the patch to meta-intel list?
Thanks,
Anuj
OK, I will resend as you mentioned. Thanks.
Sandy
--
BRs
Sandy(Li Changqing)
Wind River Linux
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Any Linux/Yocto Image Installer (for target system)
On 2018年07月07日 05:52, Raymond Yeung wrote: Is there any installer that I could download along with the .hddimg (or .iso) image to the RAM, invoke the installer, so we could have a bootable image installed on a SSD? Sorry for replying late There is a target installer meta-anaconda in yocto, which is derived from fedora's installer (anaconda) Here is the README: http://git.yoctoproject.org/cgit/cgit.cgi/meta-anaconda/tree/README //Hongxu History: I can already create USB live image with dd and .hddimg. I could also dd the .hddimg onto SSD and make it bootable. The problem is that I need multiple partitions on my 250MB SSD, some reserved for other purposes. I find that when booting up with USB running SysLinux, I could install GRUB, vmlinuz, along with boot.img and core.img under /boot directory, and the rootFs under root (i.e. '/') directory. That's 4 partitions. I believe I could resize the largest partition after installation to do what I want. Is there a way to do this manually, possibly with a utility or a shell script? Thanks, Raymond -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Tracking changes in image
On Mon, Aug 27, 2018 at 10:13 Bryan Fishell wrote: > Hi, > I want to be able to track different parts of my image, accessible from > within userspace so I can programmatically (via an environment variable or > something) what version of my patches have been applied. Ultimately, I want > to be able to answer questions from the field to know 'what changed' in a > deployed image. Is there already a method to do this? For example, our > project has u-boot, a zImage and rootfs. Is there a way to tell the patched > version (from my layer) for each of those so I can connect what is in the > field to what is in my layer in version control? > > Thanks in advance > > -- > Take a look at the documentation for the Build History feature. I think that may be a good starting point for you. https://www.yoctoproject.org/docs/2.5.1/dev-manual/dev-manual.html#maintaining-build-output-quality Ultimately, the Build History provides you with the "what changed" in terms of build artifacts, which you can then trace back to individual packages and recipes. On the other hand, version control of your own Yocto/OE layers (which has nothing to do with build history) should capture the "why was X changed". Of course, this requires that your organization uses version control in a disciplined manner for any layer metadata they maintain. Between these two, you should be able to develop a pretty clear picture of the "what and why" with respect to changes in an image. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-security][PATCH] ecryptfs-utils: fix usrmerge install path
From: Mingli Yu
Update rootsbindir from /sbin to ${base_sbindir}
to fix below do_install error when usrmerge
enabled in DISTRO_FEATURES
| chmod: cannot access
'/poky-build/tmp-glibc/work/core2-64-wrs-linux/ecryptfs-utils/111-r0/image/usr/sbin/mount.ecryptfs_private':
No such file or directory
And pass "--with-pamdir=${base_libdir}/security"
to configure script to fix below warning when
usrmerge enabled in DISTRO_FEATURES
| WARNING: ecryptfs-utils-111-r0 do_package: QA Issue: ecryptfs-utils:
Files/directories were installed but not shipped in any package:
/lib64/security/pam_ecryptfs.so
Signed-off-by: Mingli Yu
---
recipes-security/ecryptfs-utils/ecryptfs-utils_111.bb | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/recipes-security/ecryptfs-utils/ecryptfs-utils_111.bb
b/recipes-security/ecryptfs-utils/ecryptfs-utils_111.bb
index f55b0c3..1f780f9 100644
--- a/recipes-security/ecryptfs-utils/ecryptfs-utils_111.bb
+++ b/recipes-security/ecryptfs-utils/ecryptfs-utils_111.bb
@@ -29,6 +29,7 @@ EXTRA_OECONF = "\
--libdir=${base_libdir} \
--disable-pywrap \
--disable-nls \
+--with-pamdir=${base_libdir}/security \
"
PACKAGECONFIG ??= "nss \
@@ -43,12 +44,16 @@ do_configure_prepend() {
export NSS_LIBS="-L${STAGING_BASELIBDIR} -lssl3 -lsmime3 -lnss3 -lsoftokn3
-lnssutil3"
export KEYUTILS_CFLAGS="-I${STAGING_INCDIR}"
export KEYUTILS_LIBS="-L${STAGING_LIBDIR} -lkeyutils"
+sed -i -e "s;rootsbindir=\"/sbin\";rootsbindir=\"\${base_sbindir}\";g"
${S}/configure.ac
}
do_install_append() {
chmod 4755 ${D}${base_sbindir}/mount.ecryptfs_private
-mkdir -p ${D}/${libdir}
-mv ${D}/${base_libdir}/pkgconfig ${D}/${libdir}
+# ${base_libdir} is identical to ${libdir} when usrmerge enabled
+if ! ${@bb.utils.contains('DISTRO_FEATURES','usrmerge','true','false',d)};
then
+mkdir -p ${D}/${libdir}
+mv ${D}/${base_libdir}/pkgconfig ${D}/${libdir}
+fi
sed -i -e 's:-I${STAGING_INCDIR}::' \
-e 's:-L${STAGING_LIBDIR}::' ${D}/${libdir}/pkgconfig/libecryptfs.pc
sed -i -e "s: ${base_sbindir}/cryptsetup: ${sbindir}/cryptsetup:"
${D}${bindir}/ecryptfs-setup-swap
--
2.7.4
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
