From: Roy Li
A ordinary use should not to access auditd configuration files
Signed-off-by: Roy Li
---
recipes-security/audit/audit_2.3.2.bb |3 +++
1 file changed, 3 insertions(+)
diff --git a/recipes-security/audit/audit_2.3.2.bb
b/recipes-security/audit/audit_2.3.2.bb
index eafcd30..4a
From: Roy Li
Audit unit file is from
https://fedorahosted.org/audit/browser/trunk/init.d/auditd.service
Signed-off-by: Roy Li
---
recipes-security/audit/audit/audit-volatile.conf |1 +
recipes-security/audit/audit/auditd.service | 21 +
recipes-security/audit/au
From: Roy Li
The following changes since commit a6079a43719e79e12a57e609923a0cccdba06916:
refpolicy: fix real path for su.shadow (2014-02-13 10:52:07 -0500)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib roy/audit-two-fix
http://git.pokylinux.org/cgit.cgi/po
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
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
Agenda:
* Opens collection - 5 min (Stephen)
* Yocto 1.6 status - 10 min (Stephen/team)
https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.6_Status
https://wiki.yoctoproject.org/wiki/Yocto_1.6_Features
* SWAT team rotation: Beth -> Paul
https://wiki.yoctoproject.org/wiki/Yocto_Build_
On 3 March 2014 20:05, Rick Bianchi wrote:
> Which linux distro is the preferred build environment? Is it better to use
> Debian instead of Ubuntu?
Use whatever you prefer. The tested distribution list can be seen in git:
http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta-yocto/conf/distr
Which linux distro is the preferred build environment? Is it better to use
Debian instead of Ubuntu?
Thanks,
Rick
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
On 3 Mar 2014, at 12:17, Burton, Ross wrote:
> On 3 March 2014 07:10, Nicolas Dechesne wrote:
>>> How do I find out what (e.g.) gstreamer1.0-plugins-base.bb actually
>>> provides? Once I've got it to build for one plugin I can go to the work
>>> directory to see what gets packaged to find the
Hi Michael,
On Sunday 02 March 2014 19:58:41 Michael Gloff wrote:
> Is there a reason why the toolchain cannot be built with a machine name
> that contains capital letters? Seems weird, everything else builds fine,
> but meta-toolchain fails complaining about caps.
Although machine names are trad
On Monday 03 March 2014 17:13:57 Paul Eggleton wrote:
> On Monday 03 March 2014 09:56:59 Rick Bianchi wrote:
> > undefined symbol: _ZN14OpenJade_Grove8ClassDef12sgmlDocumentE
>
> This looks familiar - we've seen this issue before:
>
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=2972
>
> Un
On Monday 03 March 2014 09:56:59 Rick Bianchi wrote:
> undefined symbol: _ZN14OpenJade_Grove8ClassDef12sgmlDocumentE
This looks familiar - we've seen this issue before:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=2972
Unfortunately we were never able to reproduce it, despite numerous peopl
Please see following patch
The following changes since commit 7f3178c393a9ad71bcda4e6c3aebbaaf16037d10:
fsharp: Add support for F# programming language v3.1 (2014-03-03 16:46:59
+)
are available in the git repository at:
git://git.yoctoproject.org/meta-mono ajl/dbus-sharp
http://git.
Signed-off-by: Alex J Lennon
---
recipes-mono/dbus-sharp-glib/dbus-sharp-glib.inc | 35
.../dbus-sharp-glib/dbus-sharp-glib_0.6.0.bb |6
.../fix-message-reader-writer.patch| 29
recipes-mono/dbus-sharp/dbus-sharp.inc
Any help you can give me on patching it would be greatly appreciated.
On Mon, Mar 3, 2014 at 9:55 AM, Rick Bianchi wrote:
> | jade: symbol lookup error:
> /home/infinitezero/yoctousbip/build/tmp/sysroots/x86_64-linux/usr/bin/../../usr/lib/libospgrove.so.0:
> undefined symbol: _ZN14OpenJade_Grove
| jade: symbol lookup error:
/home/infinitezero/yoctousbip/build/tmp/sysroots/x86_64-linux/usr/bin/../../usr/lib/libospgrove.so.0:
undefined symbol: _ZN14OpenJade_Grove8ClassDef12sgmlDocumentE
| jade: symbol lookup error:
/home/infinitezero/yoctousbip/build/tmp/sysroots/x86_64-linux/usr/bin/../../u
Wrong one, sorry about that. Here is the output:
SRC_URI="http://downloads.sourceforge.net/openjade/openjade-0.6.14.tar.gzfile://makefile.patch
file://msggen.pl.patch file://reautoconf.patch
file://user-declared-default-constructor.patch"
On Mon, Mar 3, 2014 at 9:40 AM, Rick Bianchi wrote:
> He
On Monday 03 March 2014 09:47:16 Rick Bianchi wrote:
> No, I have not made any changes to the yoctousbip/build/conf/local.conf.
>
> The only change I made was to the file:
> yoctousbip/poky/meta/recipes-devtools/docbook-utils/
> docbook-utils-native_0.6.14.bb
Ah - that explains it. This is not th
On 03/03/2014 16:47, Rick Bianchi
wrote:
No, I have not made any changes to the
yoctousbip/build/conf/local.conf.
The only change I made was to the file:
yoctousbip/poky/meta/recipes-devtools/docbo
No, I have not made any changes to the yoctousbip/build/conf/local.conf.
The only change I made was to the file:
yoctousbip/poky/meta/recipes-devtools/docbook-utils/
docbook-utils-native_0.6.14.bb
It was throwing an error and I understood that it needed to be patched.
On Mon, Mar 3, 2014 at 9:4
On Monday 03 March 2014 09:40:16 Rick Bianchi wrote:
> On Mon, Mar 3, 2014 at 9:27 AM, Paul Eggleton
> wrote:
> > Before doing this, Rick could you run the following and post the output:
> >
> > bitbake -e docbook-utils-native | grep ^SRC_URI=
>
> Here is the ouput:
>
> SRC_URI="
> ftp://sources
Here is the ouput:
SRC_URI="
ftp://sources.redhat.com/pub/docbook-tools/new-trials/SOURCES/docbook-utils-0.6.14.tar.gzfile://re.patch";
On Mon, Mar 3, 2014 at 9:27 AM, Paul Eggleton wrote:
> On Monday 03 March 2014 14:53:26 Alex J Lennon wrote:
> > On 03/03/2014 14:36, Rick Bianchi wrote:
> >
On 03/03/2014 16:27, Paul Eggleton wrote:
> On Monday 03 March 2014 14:53:26 Alex J Lennon wrote:
>> On 03/03/2014 14:36, Rick Bianchi wrote:
>>> Does anyone know how I can get around this error? There is no such
>>> package on sourceforge "Fetcher failure for URL:
>>> 'http://downloads.sourceforg
On Monday 03 March 2014 14:53:26 Alex J Lennon wrote:
> On 03/03/2014 14:36, Rick Bianchi wrote:
> > Does anyone know how I can get around this error? There is no such
> > package on sourceforge "Fetcher failure for URL:
> > 'http://downloads.sourceforge.net/openjade/openjade-0.6.14.tar.gz'.
> > Un
Il 03/03/2014 10:09, Federico Vitali ha scritto:
Thank you Marco! What is the best pratice for application developement
purposed?
Should I use a qemuarm arch or a qemux86 is better for performance
reasons debugging
on a x86_64 machine?
Thank you again
IMHO
Depends on what is you goal.
Just
On 03/03/2014 14:36, Rick Bianchi
wrote:
Does anyone know how I can get around this error? There is
no such package on sourceforge "Fetcher failure for URL: 'http://downloads.sourceforge.net/openjade/openjade-0.6.14.tar.gz'.
Unable
Does anyone know how I can get around this error? There is no such package
on sourceforge "Fetcher failure for URL: '
http://downloads.sourceforge.net/openjade/openjade-0.6.14.tar.gz'. Unable
to fetch URL from any source."
Build Configuration:
BB_VERSION = "1.18.0"
BUILD_SYS = "x86_64-linux"
NATIV
See following patch for details
The following changes since commit 3caf7ee6e56c2c0f009724f36665afe647b7873a:
mono-native: Modify build to eliminate dependency on on host system
mscorlib.dll (2014-03-03 10:37:28 +)
are available in the git repository at:
git://git.yoctoproject.org/meta-
Testing
===
qemux86 image was created including the interactive shell (fsharpi) and the
compiler (fsharpc) which could both be executed
Examples from the Wikipiedia page were successfully compiled and executed with
mono, including Hello World, Windows Forms, and Asynchronous Parallel
Progr
On 3 March 2014 07:10, Nicolas Dechesne wrote:
>> How do I find out what (e.g.) gstreamer1.0-plugins-base.bb actually
>> provides? Once I've got it to build for one plugin I can go to the work
>> directory to see what gets packaged to find the names of other plugins, but
>> I can't find a way i
Thank you Marco! What is the best pratice for application developement
purposed?
Should I use a qemuarm arch or a qemux86 is better for performance reasons
debugging
on a x86_64 machine?
Thank you again
2014-02-28 16:02 GMT+01:00 Marco :
> Il 28/02/2014 15:54, Federico Vitali ha scritto:
>
> T
On 1 March 2014 14:29, Paul Barker wrote:
> On 25 February 2014 20:26, Thilo Cestonaro wrote:
>> With a change from last august in dpkg-deb, the packages generated by
>> opkg-build will not be accepted by dpkg-deb anymore.
>> The change disallows that the data.tar.gz is packed into the ipk/opk b
32 matches
Mail list logo
