Re: [yocto] linux-yocto defaulting to 3.4.52 for new qemuarmhf.conf

Hi Bruce, On Aug 25, 2013, at 9:22 AM, Bruce Ashfield wrote: >> Another quick question, why is it that when I create a new qemuarmhf.conf >> machine configuration, it doesn't automatically pick up the latest >> linux-yocto_3.8.bb recipe? Why does it attempt to use the 3.4 recipe? > > Are you

Re: [yocto] bitbake with cmake recipe

Hi Stefan, I updated my recipe: DESCRIPTION = "cameracapture application" SECTION = "examples" LICENSE = "CLOSED" PR = "r0" DEPENDS = "opencv" SRC_URI = "git://github.com/zafrullahsyed/cameracapture.git ;protocol=https;tag=v0.1" S = "${WORKDIR}/git" inherit pkgconfig cmake I have my source fi

Re: [yocto] bitbake with cmake recipe

Am 25.08.2013 17:03, schrieb Zafrullah Syed: Hi Stefan, I updated my recipe: DESCRIPTION = "cameracapture application" SECTION = "examples" LICENSE = "CLOSED" PR = "r0" DEPENDS = "opencv" SRC_URI = "git://github.com/zafrullahsyed/cameracapture.git

[yocto] [PATCH 0/5] [meta-security] Bastille bug fixes and enhancements

The patches in this set consist of a number of actual bug fixes and a few enhancements. The two enhancements are: 1) A change in the semantics of the -l flag so that it lists configuration files even if Bastille has not been run previously. 2) A change in the distributions are inferred, specified,

[yocto] [PATCH 1/5] Bastille: Preliminary cleanup of existing patches.

[YOCTO #3867] Renames existing patches and removes some changes. Curses-and-IOLoader-changes.patch is renamed to call_output_config.patch. The new patch omits the removal of the pruning step in Load_Questions but retains the replacement of a call to a non-existant function with a call to an appro

[yocto] [PATCH 3/5] Bastille: change in behavior of bastille -l.

[YOCTO #3867] bastille -l now reports existing configuration file paths even if it has not previously been run. Previously, it exited with an error if it detected an absence of log files indicating a previous run. Signed-off-by: mulhern --- recipes-security/bastille/bastille_3.2.1.bb|

[yocto] [PATCH 4/5] Bastille: accept and observe --os flag in multiple situations.

[YOCTO #3867] Five additional patches which cause the --os flag to be accepted and observed are added. An additional distro, Yocto, is added. The individual patches are described below. upgrade_options_processing.patch: Changes setOptions procedure so that it accepts named parameters for greater

[yocto] [PATCH 2/5] Bastille: Miscellaneous fixes to the Bastille code base.

[YOCTO #3867] Adds four additional small patches which address miscellaneous small problems in Bastille. The four patches are: fix_missing_use_directives.patch: A number of use directives were missing from several files. These were added as discovered. fix_number_of_modules.patch: The curses in

[yocto] [PATCH 5/5] Bastille: set Yocto specific questions via config file.

[YOCTO #3867] The python script, set_required_questions.py reads the list of questions and answers from the config file and edits the REQUIRE_DISTRO field for those questions in the questions file so that it includes "Yocto" if it is not already present. This has the effect of causing Bastille, wh

Re: [yocto] linux-yocto defaulting to 3.4.52 for new qemuarmhf.conf

On 13-08-25 10:25 AM, Elvis Dowson wrote: Hi Bruce, On Aug 25, 2013, at 9:22 AM, Bruce Ashfield mailto:bruce.ashfi...@windriver.com>> wrote: Another quick question, why is it that when I create a new qemuarmhf.conf machine configuration, it doesn't automatically pick up the latest linux-yocto_

[yocto] [Package Report System]Upgrade recipes name list

This mail was sent out by Package Report System. This message list those recipes which need to be upgraded. If maintainers believe some of them needn't to upgrade this time, they can fill in RECIPE_NO_UPDATE_REASON_pn-"xxx" in upstream_tracking files to ignore this recipe remainder until newer u

[yocto] [Package Report System]Manual check recipes name list

This mail was sent out by Package Report System. It will list all the recipes which can't check upstream version by script, and will show how long it is since their last mannual version check. You can check the detail information at http://packages.yoctoproject.org/manuallychkinfo PackageName