From: Wenzong Fan
* rebase patch audit-python-configure.patch
* 2.4.4 includes CVE-2015-5186 and bug fixes, detials refer to:
http://people.redhat.com/sgrubb/audit/ChangeLog
Signed-off-by: Wenzong Fan
---
recipes-security/audit/audit/audit-python-configure.patch | 7 ---
recipes-securit
Hi,
1. could you please keep the emails thread? receiving a new email for each
of your replies is not funny.
2. could you please use the proper raspberrypi tag in the subject? check
README.txt
3. I asked additional questions. could you please reply?
4. can you try to replicate on meta-rpi master?
On 12/11/15 17:03, Mark Hatle wrote:
> On 11/12/15 3:17 AM, Toby Gomersall wrote:
>> Hi,
>>
>> I want to build yocto with hard float support. I understand that I can
>> point the EXTERNAL_TOOLCHAIN variable at the appropriate external hard
>> float compiler (gcc-5-arm-linux-gnueabihf). However, I
When installed to the sysroot, this makes the symlink point to the
workdir, which is invalid in the sstate package. Since we cd to
${D} before creating the symlink, this ensures the link is created
in the correct install location, so just point the link to the final
target so that the patch is cor
On 26.10.2015 20:18, Cliff Brake wrote:
> Hi,
>
> I'd like to get some feedback on the following questions -- feel free
> to respond to list, or directly to me, and I'll withhold your
> name/company from any results.
>
> I would like to collect feedback until 2015-11-02, and will summarize
> the
> On Nov 12, 2015, at 9:03 AM, Mark Hatle wrote:
>
> On 11/12/15 3:17 AM, Toby Gomersall wrote:
>> Hi,
>>
>> I want to build yocto with hard float support. I understand that I can
>> point the EXTERNAL_TOOLCHAIN variable at the appropriate external hard
>> float compiler (gcc-5-arm-linux-gnueab
Current Dev Position: YP 2.1 Planning
Next Deadline: YP 2.1 M1 Cutoff December 7, 2015 noon GMT
SWAT team rotation: Tracy -> Alejandro
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
Key Status/Updates:
* 2.0 was released!
* Undergoing planning for 2.1
* Have various
Virgil,
Thank you for pointing this out, I've updated the post to override the
variable instead!
On 11/11/15 08:50, Smith, Virgil wrote:
> The recommendations on your blog suggest modifying image-buildinfo.bbclass to
> change IMAGE_BUILDINFO_VARS.
> You /should/ be able to avoid this by simply a
