From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Lewis, Nick" <nick.lewis@usa.g4s.com>
Cc: "'openembedded-core@lists.openembedded.org'"
<openembedded-core@lists.openembedded.org>
Subject: Re: Problems with PACKAGE_CLASSES = "package_tar"
Date: Wed, 24 Apr 2013 17:28:25 +0100 [thread overview]
Message-ID: <1366820905.23738.153.camel@ted> (raw)
In-Reply-To: <AAE0766F5AF36B46BAB7E0EFB927320630E4A540CC@GBTWK10E001.Technology.local>
On Wed, 2013-04-24 at 16:58 +0100, Lewis, Nick wrote:
> I am seeing problems when using PACKAGE_CLASSES = "package_tar"
>
> There are many warnings about python indents and there are errors
> regarding missing populate_sdk_tar.bbclass and rootfs_tar.bbclass
With 1.3 (danny)? These should be fixed in 1.4 (dyland) and master...
Cheers,
Richard
next prev parent reply other threads:[~2013-04-24 16:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-24 15:58 Problems with PACKAGE_CLASSES = "package_tar" Lewis, Nick
2013-04-24 16:18 ` Mark Hatle
2013-04-24 16:28 ` Richard Purdie [this message]
2013-04-24 16:57 ` Otavio Salvador
2013-04-25 7:29 ` Lewis, Nick
2013-04-25 10:21 ` Lewis, Nick
2013-04-25 12:00 ` Otavio Salvador
2013-04-25 17:05 ` Paul Eggleton
2013-04-25 18:21 ` Burton, Ross
2013-04-25 12:19 ` Richard Purdie
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=1366820905.23738.153.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=nick.lewis@usa.g4s.com \
--cc=openembedded-core@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