mail archive of the meta-rauc mailing list
 help / color / mirror / Atom feed
From: Jeremy Overesch <>
To: "" <>
Subject: [meta-rauc] bundle.bbclass accessing non-existent task do_image_complete
Date: Fri, 28 Jul 2017 14:37:58 +0000	[thread overview]
Message-ID: <> (raw)

[-- Attachment #1.1: Type: text/plain, Size: 2021 bytes --]


I'm attempting to add a kernel to my rauc bundle, based off of phytec's "linux-ti" kernel:  However, when I add the kernel, I'm getting an error " depends upon non-existent task do_image_complete".  It appears that the only class which contains "do_image_complete" is the image class, but as far as I understood, the kernel shouldn't be a system image.  I am able to create a file with just the file system, but adding a kernel or dts file does not work.

Looking inside the bundle.bbclass file, it appears that it is using the do_image_complete task for fetching dependencies.  Am I supposed to create this task for my kernel somehow?  What is it looking for as a return value?

Below is my file:

inherit bundle

RAUC_KEY_FILE = "${THISDIR}/development-1.key.pem"
RAUC_CERT_FILE = "${THISDIR}/development-1.cert.pem"

RAUC_BUNDLE_SLOTS="rootfs kernel"



Jeremy Overesch
Software Engineer

Miller Electric Mfg. Co.  An ITW Welding Company
1635 West Spencer St., P.O. Box 1079, Appleton, WI 54912-1079  Phone: 920.735.4579 <>  │  Facebook<>  │  Twitter<>  │  YouTube<>


This message (including any attachments) is intended for the sole use of the intended recipient/s and may contain material that is CONFIDENTIAL AND PRIVATE COMPANY INFORMATION. If you are not the intended recipient of this message, you are hereby notified that you must delete the message without disseminating, copying or taking any action in reliance upon it. If you have received this message in error, please notify the sender via return e-mail. Thank you.

[-- Attachment #1.2: Type: text/html, Size: 6268 bytes --]

[-- Attachment #2: Type: text/plain, Size: 71 bytes --]

meta-rauc mailing list

                 reply	other threads:[~2017-07-28 14:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

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

  git send-email \ \ \ \

* 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