public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: Balasubramanian Sundaram <balasubramanian.sundaram@sanmina.com>
Cc: Anton Mikanovich <amikan@ilbers.de>, isar-users@googlegroups.com
Subject: Re: [PATCH] image.bbclass: set file timestamps inside the rootfs and initramfs image
Date: Thu, 10 Nov 2022 19:05:30 +0200	[thread overview]
Message-ID: <20221110190530.766e3d31@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20221110183058.4746aed6@md1za8fc.ad001.siemens.net>

Am Thu, 10 Nov 2022 18:30:58 +0200
schrieb Henning Schild <henning.schild@siemens.com>:

> Hey Balasubramanian,
> 
> you are making some fundamental mistakes here so that is why people
> might not want to help you or would not know how to do so.
> 
> When you have a question for help please formulate it clearly and
> give some context. You just want to install a debian package in your
> image, use IMAGE_PREINSTALL.
> You have to modify/rebuild that package ... check out the hello
> example and use IMAGE_INSTALL.
> 
> So say you can just use the meta-package "bluetooth" you can have a
> look at this part of the docs.
> https://github.com/ilbers/isar/blob/master/doc/user_manual.md#create-a-custom-image-recipe

I used plain isar, added "IMAGE_PREINSTALL += "bluetooth"" to the end
of meta-isar/recipes-core/images/isar-image-base.bb and did build it
with "bitbake mc:qemuamd64-bullseye:isar-image-base".

I booted it with
qemu-system-x86_64 -smp 2 -enable-kvm -M q35 -m 2G -snapshot
build/tmp/deploy/images/qemuamd64/isar-image-base-debian-bullseye-qemuamd64.wic
-bios /usr/share/OVMF/OVMF_CODE.fd

Works as expected. Well i have the packages like "bluez" installed ...

Of cause in a real project one would create a layer with an own image
recipe and add the line there.

Henning

> And consider giving this whole manual a read. It is not the best and
> maybe not all clear when you read it first. But over time it should
> make sense.
> 
> That said. Please avoid these mistakes:
> 
> - taking over a random discussion to talk about something totally
>   different, rather open a new one
> - send debug output as screenshots ... they are hard to read and cite
>   (they all have the same name), and you leak stuff like the model of
>   your cell phone, or that your firmware is "Music" ... send the
>   relevant bits as text and say how you got there. Without your recipe
>   or change it is really hard to put your errors into any context.
>   the last one looks like you modified the image recipe of the cip
>   layer and added bluez as IMAGE_INSTALL where it should have been
>   IMAGE_PREINSTALL
> - do not send html mails
> - do not include CONFIDENTIALITY disclaimers, your mails are super
>   public so that does not make any sense
> 
> regards,
> Henning
> 
> Am Thu, 10 Nov 2022 16:21:18 +0530
> schrieb Balasubramanian Sundaram
> <balasubramanian.sundaram@sanmina.com>:
> 
> > Thank you for the clarification.
> > 
> > but iam getting following error can you tell what it can be
> > [image: image.png]
> > 
> > Regards
> > 
> > On Thu, Nov 10, 2022 at 3:58 PM Anton Mikanovich <amikan@ilbers.de>
> > wrote:
> >   
> > > 10.11.2022 13:17, Balasubramanian Sundaram wrote:
> > >
> > > Hi Anton
> > >
> > > Iam getting this error for bluez
> > > [image: image.png]
> > >
> > > Thanks & Regards
> > >
> > > Sorry, I've meant IMAGE_PREINSTALL, not IMAGE_INSTALL.
> > > IMAGE_PREINSTALL should be used for any package from external
> > > repos. IMAGE_INSTALL should be used in case you will rebuild the
> > > package from repo with your custom recipe.
> > >
> > > hello.bb is located in Isar examples:
> > >
> > > https://github.com/ilbers/isar/blob/master/meta-isar/recipes-app/hello/hello.bb
> > >    
> > 
> >   
> 


      reply	other threads:[~2022-11-10 17:05 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-07  8:25 venkata.pyla
2022-11-07  8:50 ` Moessbauer, Felix
2022-11-09  6:56   ` Venkata.Pyla
2022-11-07  8:53 ` Henning Schild
2022-11-09  9:27   ` Venkata.Pyla
2022-11-10  7:12     ` Henning Schild
2022-11-20  7:53       ` [PATCH] scripts/repro-test.sh: script to test reproducibility of Isar image venkata.pyla
2022-11-22  7:28         ` Anton Mikanovich
2022-11-22  8:49           ` Venkata.Pyla
2022-12-19 14:41             ` [PATCH 0/2] Test for verifiying reproducible images venkata.pyla
2022-12-28  8:40               ` Anton Mikanovich
2023-01-02  6:24                 ` [PATCH] repro-build-test.py: Fix date_epoch time contains byte character b'' venkata.pyla
2023-01-11  5:42                   ` Uladzimir Bely
2022-12-19 14:41             ` [PATCH 1/2] cibuilder.py: Add source_date_epoch to build configuration venkata.pyla
2022-12-19 14:41             ` [PATCH 2/2] repro-build-test.py: Test to check images are reproducible venkata.pyla
2023-01-07  0:01               ` Henning Schild
2022-11-21  5:16       ` [PATCH] image.bbclass: set file timestamps inside the rootfs and initramfs image Venkata.Pyla
2022-11-10  9:52 ` Balasubramanian Sundaram
2022-11-10 10:03   ` Anton Mikanovich
2022-11-10 10:17     ` Balasubramanian Sundaram
2022-11-10 10:19       ` Balasubramanian Sundaram
2022-11-10 10:27       ` Anton Mikanovich
2022-11-10 10:51         ` Balasubramanian Sundaram
2022-11-10 16:30           ` Henning Schild
2022-11-10 17:05             ` Henning Schild [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=20221110190530.766e3d31@md1za8fc.ad001.siemens.net \
    --to=henning.schild@siemens.com \
    --cc=amikan@ilbers.de \
    --cc=balasubramanian.sundaram@sanmina.com \
    --cc=isar-users@googlegroups.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