public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Claudius Heine <claudius.heine.ext@siemens.com>
To: "[ext] Jan Kiszka" <jan.kiszka@siemens.com>,
	isar-users <isar-users@googlegroups.com>,
	Claudius Heine <ch@denx.de>
Subject: Re: [PATCH] rootfs: Add missing dependency for rootfs_postprocess
Date: Tue, 20 Aug 2019 16:55:50 +0200	[thread overview]
Message-ID: <fcd669ff-4e3e-f696-a62f-b4508e402a85@siemens.com> (raw)
In-Reply-To: <b90ba06c-89c0-cb6a-de6a-5ee1b8d7e41e@siemens.com>

Hi Jan,

On 20/08/2019 16.48, [ext] Jan Kiszka wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
> 
> This task needs the unpacked files from SRC_URI, specifically
> DISTRO_CONFIG_SCRIPT.
> 
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
>   meta/classes/rootfs.bbclass | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/meta/classes/rootfs.bbclass b/meta/classes/rootfs.bbclass
> index c7e0435..7d22452 100644
> --- a/meta/classes/rootfs.bbclass
> +++ b/meta/classes/rootfs.bbclass
> @@ -227,7 +227,7 @@ python do_rootfs_postprocess() {
>       for cmd in cmds:
>           bb.build.exec_func(cmd, d)
>   }
> -addtask rootfs_postprocess before do_rootfs
> +addtask rootfs_postprocess before do_rootfs after do_unpack

No, I think the dependency between do_unpack and do_fetch is missing.

rootfs_postprocess depends on rootfs_install which depends on do_unpack 
already:

classes/rootfs.bbclass
159:addtask rootfs_install before do_rootfs_postprocess after do_unpack

regards,
Claudius

>   
>   python do_rootfs() {
>       """Virtual task"""
> 

-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de

  reply	other threads:[~2019-08-20 14:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-20 14:48 Jan Kiszka
2019-08-20 14:55 ` Claudius Heine [this message]
2019-08-20 14:57   ` Claudius Heine
2019-08-20 14:58   ` Jan Kiszka
2019-08-20 15:34     ` Jan Kiszka

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=fcd669ff-4e3e-f696-a62f-b4508e402a85@siemens.com \
    --to=claudius.heine.ext@siemens.com \
    --cc=ch@denx.de \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.com \
    /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