Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Roman I Khimov <khimov@altell.ru>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] cpan.bbclass: removed legacy staging
Date: Mon, 26 Jul 2010 12:53:53 +0400	[thread overview]
Message-ID: <201007261253.53814.khimov@altell.ru> (raw)
In-Reply-To: <1280075525-31322-1-git-send-email-fransmeulenbroeks@gmail.com>

В сообщении от Воскресенье 25 июля 2010 20:32:05 автор Frans Meulenbroeks 
написал:
> bumped PR for the main perl recipes so this change takes effect
> 
> Signed-off-by: Frans Meulenbroeks <fransmeulenbroeks@gmail.com>
> ---
> 
> removed legacy staging
> 
> as QA compared with the poky version.
> Also build all perl/lib* recipes with it (using perl 5.8.8).
> 5 of these fail:
> ERROR:
>  'virtual:native:/home/frans/oe/openembedded/recipes/perl/libcurses-perl_1.
> 28.bb' failed ERROR:
>  '/home/frans/oe/openembedded/recipes/perl/libcurses-perl_1.28.bb' failed
>  ERROR: '/home/frans/oe/openembedded/recipes/perl/libsocket6-perl_0.23.bb'
>  failed ERROR:
>  '/home/frans/oe/openembedded/recipes/perl/libdbd-mysql-perl-native_4.010.b
> b' failed ERROR:
>  '/home/frans/oe/openembedded/recipes/perl/libencode-detect-perl_1.01.bb'
>  failed However these 5 also failed before making the change.
> These recipes are broken and I did not see an apparent fix

Acked-by: Roman I Khimov <khimov@altell.ru>

As for the broken recipes, changes are high for at least mine part of them 
that they actually require Perl 5.10 (I'm not using 5.8.8 for almost a year 
now).



      parent reply	other threads:[~2010-07-26  8:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-25 16:32 [PATCH] cpan.bbclass: removed legacy staging Frans Meulenbroeks
2010-07-26  7:50 ` Koen Kooi
2010-07-26  8:53 ` Roman I Khimov [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201007261253.53814.khimov@altell.ru \
    --to=khimov@altell.ru \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox