Re: [yocto] Release Candidate Build for yocto-1.7.rc1 now available.
Hi Atul, M3 was released so yes, the build below is a weekly build for M4. This week is starting the 1.7_M4.rc1 build according to the Yocto calendar: https://wiki.yoctoproject.org/wiki/YoctoCalendar Regards, -- Alexandru Georgescu Yocto QA Engineer SSG/SSD Open Source Technology Center Romania From: atulkumar singh atul.singh...@gmail.commailto:atul.singh...@gmail.com Date: Wednesday 24 September 2014 16:50 To: yocto@yoctoproject.orgmailto:yocto@yoctoproject.org yocto@yoctoproject.orgmailto:yocto@yoctoproject.org Subject: [yocto] Release Candidate Build for yocto-1.7.rc1 now available. Hi All, Please let me know whether the release candidate mentioned below with commit is for 1.7M4? Regards, Atul A release candidate build for yocto-1.7.rc1 is now available at: http://autobuilder.yoctoproject.org/pub/releases/yocto-1.7.rc1 Please begin QA on this build as soon as possible. Build hash information: meta-intel : a369fa8f2d76528cb296ef9314e613e26585d54d meta-fsl-arm : 2680f54d02fa6efe4cd2aaef7bda9e46cf3e9672 meta-minnow : 238a45e9da8bbfff7a6af220b48c11cabd31e01c meta-qt3 : 3016129d90b7ac8517a5227d819f10ad417b5b45 meta-fsl-ppc : 478f29c3e97760f2ff443227950ce21d9510a280 poky : 8ac8eca2e3bd8c78e2b31ea974930ed0243258a3 This is an automated message from The Yocto Project Autobuilder Git: git://git.yoctoproject.org/yocto-autobuilderhttp://git.yoctoproject.org/yocto-autobuilder Email: elizabeth.flanagan at intel.comhttp://intel.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] PR and bbappend files
Hi, 2014-09-28 11:47 GMT+02:00 Chris Tapp opensou...@keylevel.com: I'm currently using a bbappend file to patch bash under 'danny' due to Shellshocked - basically by adding patches 11..50 to the SRC_URI. However, patches are still coming out ;-) How do I make sure that new ones get reflected in the build? I would normally bump PR in a .bb file, but I don't think a .bbappend should be changing this? For danny you can use PRINC http://www.yoctoproject.org/docs/1.3.2/poky-ref-manual/poky-ref-manual.html#var-PRINC For newer releases this is deprecated. Could you please be so kind and share your bbappend + patches? Is there any chance to get this in the official poky branches? regards, Christian -- Chris Tapp opensou...@keylevel.com www.keylevel.com You can tell you're getting older when your car insurance gets real cheap! -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto -- http://project-magpie.github.io/ -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Wildcard in RDEPENDS when exporting perl modules to SDK
On Monday 29 September 2014 08:09:33 Joseph Andrew de la Peña wrote: On Fri, Sep 26, 2014 at 5:02 PM, Paul Eggleton paul.eggle...@linux.intel.com wrote: There isn't, but you can just add nativesdk-perl-modules to your SDK (via appending to TOOLCHAIN_TARGET_TASK) to accomplish the same thing - it's a meta-package that will bring in all of the core modules. I would like to ask why you specifically noted the TOOLCHAIN_TARGET_TASK and not the TOOLCHAIN_HOST_TASK? Why are you inclined to putting it into the target sysroot and not the host sysroot? Or plainly what are the guidelines on where to put the unit to that toolchain task? Actually I had this wrong, it should be TOOLCHAIN_HOST_TASK - it's not a target package. Where to put a particular package in the two parts of the SDK depends on where the package is normally designed to run - the build host or the target. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Yocto Daisy with MariaDB 5.5
Hi Albert, On Monday 29 September 2014 13:13:50 Albert K wrote: May I ask if there is any recipe for MariaDB 5.5 on the Daisy Branch? Thanks. There is a mariadb recipe in meta-oe, but the daisy branch has only version 5.1.67. However in theory you should be able to take the 5.5 recipe from meta- oe master and use that with daisy. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Wildcard in RDEPENDS when exporting perl modules to SDK
Good day Paul, Thank you for the clarification. - Joseph On Mon, Sep 29, 2014 at 4:39 PM, Paul Eggleton paul.eggle...@linux.intel.com wrote: On Monday 29 September 2014 08:09:33 Joseph Andrew de la Peña wrote: On Fri, Sep 26, 2014 at 5:02 PM, Paul Eggleton paul.eggle...@linux.intel.com wrote: There isn't, but you can just add nativesdk-perl-modules to your SDK (via appending to TOOLCHAIN_TARGET_TASK) to accomplish the same thing - it's a meta-package that will bring in all of the core modules. I would like to ask why you specifically noted the TOOLCHAIN_TARGET_TASK and not the TOOLCHAIN_HOST_TASK? Why are you inclined to putting it into the target sysroot and not the host sysroot? Or plainly what are the guidelines on where to put the unit to that toolchain task? Actually I had this wrong, it should be TOOLCHAIN_HOST_TASK - it's not a target package. Where to put a particular package in the two parts of the SDK depends on where the package is normally designed to run - the build host or the target. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] yocto 1.6 - beaglebone black - cape manager
On 26.09.2014 15:17, TakkTakk wrote: ok, I removed uEnv.txt, pressed the boot switch. Starting kernel ... and hang. why - Image Name: Linux-3.14.0-yocto-standard ? I don't have a solution to your problem, but I can at least assure to you that you are not alone ;) I'm facing the same problem. I have a Beaglebone Black Rev. A6 which boots fine with Yocto 1.6 (no meta-beaglebone) and kernel 3.14. On another newer board with Rev. B it hangs after Starting Kernel. I have no idea why. According to the elinux.org wiki the difference between Revision A and B is mainly another Version of the SoC (AM3358BZCZ100 in Rev. B and AM3359AZCZ100 in Rev. A). Did you manage to fix your problem by now? - Andy -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] PR and bbappend files
On 29 Sep 2014, at 08:52, Christian Ege k423...@gmail.com wrote: Hi, 2014-09-28 11:47 GMT+02:00 Chris Tapp opensou...@keylevel.com: I'm currently using a bbappend file to patch bash under 'danny' due to Shellshocked - basically by adding patches 11..50 to the SRC_URI. However, patches are still coming out ;-) How do I make sure that new ones get reflected in the build? I would normally bump PR in a .bb file, but I don't think a .bbappend should be changing this? For danny you can use PRINC http://www.yoctoproject.org/docs/1.3.2/poky-ref-manual/poky-ref-manual.html#var-PRINC For newer releases this is deprecated. Could you please be so kind and share your bbappend + patches? Sure - I'll make this public after I finish work today. Is there any chance to get this in the official poky branches? regards, Christian -- Chris Tapp opensou...@keylevel.com www.keylevel.com You can tell you're getting older when your car insurance gets real cheap! -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto -- http://project-magpie.github.io/ -- Chris Tapp opensou...@keylevel.com www.keylevel.com You can tell you're getting older when your car insurance gets real cheap! -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Issues removing RRECOMMENDS packages with BAD_RECOMMENDATIONS
Hi, I have successfully built a custom root filesystem, but I'm having issues stopping certain packages from being installed. Basically the BAD_RECOMMENDATIONS that I have defined is not removing/preventing the installation of the RRECOMMENDS packages. This is using opkg as the package manager. I am using: BAD_RECOMMENDATIONS= \ busybox-udhcpc \ e2fsprogs-e2fsck \ udev-hwdb \ update-rc.d \ vim-help \ vim-syntax \ vim-tutor \ All of which are specified as RRECOMMENDS in various recipes. The BAD_RECOMMENDATIONS all seem to write the correct entries to the /var/lib/opkg/status file (desinstall hold not-installed), which I've confirmed with some debug in the package_manager.py. However when the packages are being installed in the rootfs stage, then only a couple of them are processed and ignored. The strange thing is, that depending on the verbosity of the opkg-cl command, the number of packages successfully processed changes. The higher the verbosity the more packages from BAD_RECOMMENDATIONS are processed. I include the output of the rootfs creation below, with the ignoring recommendation lines pulled out. I believe that I am using BAD_RECOMMENDATIONS correctly, I just cannot see what is going wrong. I've tried with the a newer version of opkg (0.2.3) but that showed the same issues. Thanks for any help Chris Carr --- -bash-4.2$ /srv/nfs/chris/owc_up/poky/build/tmp/sysroots/x86_64-linux/usr/bin/opkg-cl -v opkg version 0.2.2 Default Run: NOTE: /srv/nfs/chris/owc_up/poky/build/tmp/sysroots/x86_64-linux/usr/bin/opkg-cl -f /srv/nfs/chris/owc_up/poky/build/tmp/work/da923rc-owc_cc-linux-gnuspe/openware-core/1.0-r0/opkg.conf -o /srv/nfs/chris/owc_up/poky/build/tmp/work/da923rc-owc_cc-linux-gnuspe/openware-core/1.0-r0/rootfs --force_postinstall --prefer-arch-to-version install opkg-collateral packagegroup-owc-system packagegroup-owc-boot packagegroup-owc-net opkg packagegroup-owc-ruby vim: ignoring recommendation for vim-syntax at user request systemd: ignoring recommendation for e2fsprogs-e2fsck at user request Debug V1: NOTE: /srv/nfs/chris/owc_up/poky/build/tmp/sysroots/x86_64-linux/usr/bin/opkg-cl -V1 -f /srv/nfs/chris/owc_up/poky/build/tmp/work/da923rc-owc_cc-linux-gnuspe/openware-core/1.0-r0/opkg.conf -o /srv/nfs/chris/owc_up/poky/build/tmp/work/da923rc-owc_cc-linux-gnuspe/openware-core/1.0-r0/rootfs --force_postinstall --prefer-arch-to-version install opkg-collateral packagegroup-owc-system packagegroup-owc-boot packagegroup-owc-net opkg packagegroup-owc-ruby vim: ignoring recommendation for vim-syntax at user request systemd: ignoring recommendation for e2fsprogs-e2fsck at user request Debug V2: NOTE: /srv/nfs/chris/owc_up/poky/build/tmp/sysroots/x86_64-linux/usr/bin/opkg-cl -V2 -f /srv/nfs/chris/owc_up/poky/build/tmp/work/da923rc-owc_cc-linux-gnuspe/openware-core/1.0-r0/opkg.conf -o /srv/nfs/chris/owc_up/poky/build/tmp/work/da923rc-owc_cc-linux-gnuspe/openware-core/1.0-r0/rootfs --force_postinstall --prefer-arch-to-version install opkg-collateral packagegroup-owc-system packagegroup-owc-boot packagegroup-owc-net opkg packagegroup-owc-ruby vim: ignoring recommendation for vim-syntax at user request systemd: ignoring recommendation for udev-hwdb at user request systemd: ignoring recommendation for e2fsprogs-e2fsck at user request Debug V3: NOTE: /srv/nfs/chris/owc_up/poky/build/tmp/sysroots/x86_64-linux/usr/bin/opkg-cl -V3 -f /srv/nfs/chris/owc_up/poky/build/tmp/work/da923rc-owc_cc-linux-gnuspe/openware-core/1.0-r0/opkg.conf -o /srv/nfs/chris/owc_up/poky/build/tmp/work/da923rc-owc_cc-linux-gnuspe/openware-core/1.0-r0/rootfs --force_postinstall --prefer-arch-to-version install opkg-collateral packagegroup-owc-system packagegroup-owc-boot packagegroup-owc-net opkg packagegroup-owc-ruby vim: ignoring recommendation for vim-help at user request vim: ignoring recommendation for vim-syntax at user request vim: ignoring recommendation for vim-tutor at user request rsyslog: ignoring recommendation for update-rc.d at user request busybox: ignoring recommendation for update-rc.d at user request busybox: ignoring recommendation for busybox-udhcpc at user request dbus-1: ignoring recommendation for update-rc.d at user request systemd: ignoring recommendation for update-rc.d at user request systemd: ignoring recommendation for udev-hwdb at user request systemd: ignoring recommendation for e2fsprogs-e2fsck at user request run-postinsts: ignoring recommendation for update-rc.d at user request ntp: ignoring recommendation for update-rc.d at user request quagga: ignoring recommendation for update-rc.d at user request dropbear: ignoring recommendation for update-rc.d at user request rarpd: ignoring recommendation for update-rc.d at user request Debug V4: NOTE: /srv/nfs/chris/owc_up/poky/build/tmp/sysroots/x86_64-linux/usr/bin/opkg-cl -V4 -f
Re: [yocto] PR and bbappend files
On 29 Sep 2014, at 08:52, Christian Ege k423...@gmail.com wrote: Hi, 2014-09-28 11:47 GMT+02:00 Chris Tapp opensou...@keylevel.com: I'm currently using a bbappend file to patch bash under 'danny' due to Shellshocked - basically by adding patches 11..50 to the SRC_URI. However, patches are still coming out ;-) How do I make sure that new ones get reflected in the build? I would normally bump PR in a .bb file, but I don't think a .bbappend should be changing this? For danny you can use PRINC http://www.yoctoproject.org/docs/1.3.2/poky-ref-manual/poky-ref-manual.html#var-PRINC For newer releases this is deprecated. Could you please be so kind and share your bbappend + patches? This is now available in a layer at https://github.com/keylevel/meta-danny-maintenance. bash --version will report 4.2.50 Is there any chance to get this in the official poky branches? regards, Christian -- Chris Tapp opensou...@keylevel.com www.keylevel.com You can tell you're getting older when your car insurance gets real cheap! -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto -- http://project-magpie.github.io/ -- Chris Tapp opensou...@keylevel.com www.keylevel.com You can tell you're getting older when your car insurance gets real cheap! -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
