Openembedded Core Discussions
 help / color / mirror / Atom feed
From: akuster808 <akuster808@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [krogoth][PATCH] lib/oe/rootfs: Fix DEBUGFS generation, without openssl
Date: Wed, 29 Jun 2016 07:42:32 -0700	[thread overview]
Message-ID: <5773DE58.3020909@gmail.com> (raw)
In-Reply-To: <20160627070349.GA20550@ad.chargestorm.se>



On 06/27/2016 12:03 AM, Anders Darander wrote:
> Ping.
> 
> What's the current status?

Submitted again. Hope it makes in this time.

- armin

> 
>  Anders Darander <anders@chargestorm.se> [160607 09:31]:
>> * akuster808 <akuster808@gmail.com> [160523 07:29]:
>>> On 05/22/2016 10:03 PM, Anders Darander wrote:
>>>> In commit 20ea6d274bb0a9a5addb111f32793de49b907865, debugfs generation
>>>> for images using opkg, which included openssl was fixed.
> 
>>>> However, that broke the generation of the opkg-based images, that lacks
>>>> openssl. The error is a python stack trace, showing that shutil.copytree
>>>> tries to copy a non-existing directory.
> 
>>>> This relates to [YOCTO #9040].
> 
>>>> Signed-off-by: Anders Darander <anders@chargestorm.se>
>>>> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
>>>> (cherry picked from commit f6b0b260ce18a30d04edfb0afb7942b9f9a5480b)
> 
>>> pulled in.
> 
>> What's the status of this? Waiting for autobuilders?
> 
>> Martin sent a query for this patch last week.
> 
> I'm also eager to get this into the krogoth-branch. I'd like to enable
> debugfs, though, I'm also trying my best to not have to fork the krogoth
> branch...
> 
> Cheers,
> Anders
> 


      reply	other threads:[~2016-06-29 14:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-23  5:03 [krogoth][PATCH] lib/oe/rootfs: Fix DEBUGFS generation, without openssl Anders Darander
2016-05-23  5:26 ` akuster808
2016-06-07  7:31   ` Anders Darander
2016-06-27  7:03     ` Anders Darander
2016-06-29 14:42       ` akuster808 [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=5773DE58.3020909@gmail.com \
    --to=akuster808@gmail.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