* Addresses CVE-2010-0751
* Use new-style checksums
Signed-off-by: Scott Garman
---
recipes/libnids/libnids-1.24/configure.patch | 60 ++
recipes/libnids/libnids_1.24.bb | 26 +++
2 files changed, 86 insertions(+), 0 deletions(-)
create mode 1006
Sorry, cancel that patch - I just discovered that libnids 1.18 is a
PREFERRED_VERSION in openmoko.
I will delete this patch from patchwork and submit a new one that
doesn't delete the old version.
Scott
--
Scott Garman
sgarman at zenlinux dot com
___
* Addresses CVE-2010-0751
* Use new-style checksums
Signed-off-by: Scott Garman
---
conf/checksums.ini |8 ---
recipes/libnids/libnids-1.18/configure.patch | 60 --
recipes/libnids/libnids-1.24/configure.patch | 60 +++
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09-04-10 21:39, Antonio Ospite wrote:
> Hi,
>
> when building libmokoui2 I get this:
> http://tinderbox.openembedded.org/packages/544186/
>
> basically:
> /bin/sh: pygtk-codegen-2.0: command not found
>
> With this change to python-pygtk_2.16.0.b
Hi,
when building libmokoui2 I get this:
http://tinderbox.openembedded.org/packages/544186/
basically:
/bin/sh: pygtk-codegen-2.0: command not found
With this change to python-pygtk_2.16.0.bb I can make it build:
diff --git a/recipes/python/python-pygtk_2.16.0.bb
b/recipes/python/python-pygtk_
edbus-ehal is not available anywhere in current metadata, just depend on
edbus to make images which include paroli build.
See also http://tinderbox.openembedded.org/packages/544404/
Signed-off-by: Antonio Ospite
---
This fixes an issue when building fso-zhone-image:
* satisfy_dependencies_for:
On Fri, 09 Apr 2010 09:51:31 +0200
Koen Kooi wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 08-04-10 23:20, Antonio Ospite wrote:
> > Having these around can cause some conflict in recipes depending on
> > recent glib-2.0-native, see [1].
> >
> > What can happen is that, when n
Hello,
I am trying to write a 'task-' recipe to pull together the separate recipes of
my application. I then use IMAGE_INSTALL += in my image recipe to pull in the
task recipe. I based it on the existing task- recipes.
All the recipes run, but the files to placed in the rootfs don't make it the
Hi, all!
I need to install additional package to image (which is inpossible
using IMAGE_INSTALL due to conflicts.
That's because I do it in ROOTFS_POSTPROCESS_COMMAND.
so I first remove conflicting package, then install one which is
needed. Removing works perfectly,
but installing doesn't, since o
Looks good to me. The script could always set +e to disable it anyway if it
really wanted to :)
Acked-by: Chris Larson
On Fri, Apr 9, 2010 at 4:19 AM, Roman I Khimov wrote:
> There are scripts that can and should work when being ran on build
> host (for example, simple update-rc.d), but there
Recipes are using update-rc.d to do postinst and postinst scripts are being
ran on build hosts where native version is needed to run properly. It is
needed only at image build stage, but it's easier to have it in DEPENDS,
build time for it is almost zero anyway.
Signed-off-by: Roman I Khimov
---
Sergey Lapin wrote:
>> Actually, update-rc.d scripts should work on build host (that "$OPT" in
>> script
>> is exactly for that purpose) and so are update-alternatives (thanks to
>> OPKG_OFFLINE_ROOT magic), so there might be something wrong with your setup.
> I found the reason for that error - u
Paul Menzel writes:
> I ran a build from scratch with `EXTRA_AUTORECONF = "--exclude=autopoint"`
> from `autotools.bbclass` and did not see any regressions.
There are regressions in projects using 'intltool' (e.g. 'pmount');
./configure will fail with 'po/Makefile.in.in was not created by
intlto
>
> Actually, update-rc.d scripts should work on build host (that "$OPT" in script
> is exactly for that purpose) and so are update-alternatives (thanks to
> OPKG_OFFLINE_ROOT magic), so there might be something wrong with your setup.
I found the reason for that error - update-rc.d is not being sta
В сообщении от Пятница 09 апреля 2010 14:53:22 автор Sergey Lapin написал:
> On Fri, Apr 9, 2010 at 2:39 PM, Roman I Khimov wrote:
> > В сообщении от Пятница 09 апреля 2010 14:26:22 автор Sergey Lapin написал:
> >> So, with recent images I have to run all postinst scripts again on
> >> device for
There are scripts that can and should work when being ran on build
host (for example, simple update-rc.d), but there are also many which
can't and won't ever (for example, anything adding users/groups).
The second group sometimes doesn't get "unpacked" flag because
scripts throw errors in the middl
Previous episodes:
736c06e8d8 image.bbclass: reorder do_rootfs
049a7998d0 Revert "image.bbclass: reorder do_rootfs"
As I still build many interdependent images and as I still don't want
to write "do_rootfs[depends] = ..." in images, I think we can easily
solve the problem by recrdep-ing do_rootfs
On Fri, Apr 9, 2010 at 2:39 PM, Roman I Khimov wrote:
> В сообщении от Пятница 09 апреля 2010 14:26:22 автор Sergey Lapin написал:
>> So, with recent images I have to run all postinst scripts again on
>> device for services
>> like udev or dropbear to work. These packages get 'installed' status,
>
В сообщении от Пятница 09 апреля 2010 14:26:22 автор Sergey Lapin написал:
> So, with recent images I have to run all postinst scripts again on
> device for services
> like udev or dropbear to work. These packages get 'installed' status,
> so postinst
> scripts won't normally run during 'opkg confi
Awesome, congrats!
Please keep up that work, it certainly would be very interesting for
OpenEmbedded.
Cheers,
--
:M:
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/op
Am Freitag, den 09.04.2010, 09:51 +0200 schrieb Koen Kooi:
> On 08-04-10 23:20, Antonio Ospite wrote:
> > Having these around can cause some conflict in recipes depending on
> > recent glib-2.0-native, see [1].
> >
> > What can happen is that, when no preferred versions are set (like in
> > DISTRO
Hi, all!
If I understand properly, during image preparation, postinst scripts
for each package are run.
If they fail, package gets status 'unpacked'. Otherwise, it gets
status 'installed'.
So, with recent images I have to run all postinst scripts again on
device for services
like udev or dropbear
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08-04-10 23:53, Paul Menzel wrote:
> Dear Koen,
>
>
> Am Montag, den 15.03.2010, 00:08 +0100 schrieb Paul Menzel:
>> Am Sonntag, den 14.03.2010, 16:53 +0100 schrieb Koen Kooi:
>>> Thanks for the patch! I have a hge stack of changed queued for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08-04-10 23:20, Antonio Ospite wrote:
> Having these around can cause some conflict in recipes depending on
> recent glib-2.0-native, see [1].
>
> What can happen is that, when no preferred versions are set (like in
> DISTRO=minimal), bitbake picks
On Fri, Apr 09, 2010 at 11:23:08AM +0400, Roman I Khimov wrote:
> Is there any reason not to use latest tzdata?
I don't see one too and I guess that nobody is using
preferred-om-2008-versions anymore..
> Signed-off-by: Roman I Khimov
Acked-by: Martin Jansa
> ---
> conf/distro/include/preferr
On Fri, Apr 09, 2010 at 11:23:07AM +0400, Roman I Khimov wrote:
> I don't see any value in old tzdata/tzcode-native recipes as tzcode is only
> used to compile tzdata and compiled tzdata should be compatible with any
> version of glibc and it's good to have it latest. So I think we should only
> le
I don't see any value in old tzdata/tzcode-native recipes as tzcode is only
used to compile tzdata and compiled tzdata should be compatible with any
version of glibc and it's good to have it latest. So I think we should only
leave latest tzdata version and move that forward whenever someone discove
Is there any reason not to use latest tzdata?
Signed-off-by: Roman I Khimov
---
conf/distro/include/preferred-om-2008-versions.inc |2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/conf/distro/include/preferred-om-2008-versions.inc
b/conf/distro/include/preferred-om-2008
28 matches
Mail list logo
