public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Anton Mikanovich <amikan@ilbers.de>
To: isar-users@googlegroups.com, Ulrich Teichert <ulrich.teichert@kumkeo.de>
Subject: Re: Using private apt-repositories
Date: Thu, 23 Apr 2026 12:26:57 +0300	[thread overview]
Message-ID: <74855666-cabc-4768-a926-e09fbbd11cae@ilbers.de> (raw)
In-Reply-To: <acd50625-b3eb-491e-9173-57ca254f80d2n@googlegroups.com>

Hello Ulrich,

IMAGE_INSTALL variable is used for recipe dependency, those recipes will be
built and debs with those names will be installed.
What you are trying to achieve should be done with IMAGE_PREINSTALL 
variable,
it will just install the deb.

23.04.2026 12:11, Ulrich Teichert wrote:
> Hi,
>
> I'm in the process of moving our image generation from ELBE to Isar - 
> and of course
> I'm running into unforseen situations ;-)
>
> ELBE relies on apt-repositories where already build packages are 
> stored, ready for
> installation on the target, therefore we have all our custom stuff 
> already build and
> available as Debian packages and I surely do not want to rebuild these 
> packages in
> Isar.
>
> So, I added an extra layer and appended a sources list file 
> to DISTRO_APT_SOURCES,
> pointing to our local apt-repository (aptly) and added one of our 
> locally hosted
> packages to IMAGE_INSTALL. This somewhat naive approach backfired 
> immediatetly
> when trying to build an image:
>
> ERROR: Nothing PROVIDES 'XXXX' (but 
> mc:qemuarm64-trixie:/home/isar/isar-image/isar/meta-isar/recipes-core/images/isar-image-base.bb 
> DEPENDS on or otherwise requires it
>
> where XXXX is the locally hosted package name.
>
> This is probably expected behaviour, I assume. What would be the best 
> way to tackle that?
> Overwriting the part of the Isar-bootstrapping where the package lists 
> are build?
> Defining another list of packages to be installed after bootstrapping 
> is complete?
> I'd like to avoid adding recipies for every local package,
>
> thanks in advance for every suggestion,
> Uli
> -- 
> You received this message because you are subscribed to the Google 
> Groups "isar-users" group.
> To unsubscribe from this group and stop receiving emails from it, send 
> an email to isar-users+unsubscribe@googlegroups.com.
> To view this discussion visit 
> https://groups.google.com/d/msgid/isar-users/acd50625-b3eb-491e-9173-57ca254f80d2n%40googlegroups.com 
> <https://groups.google.com/d/msgid/isar-users/acd50625-b3eb-491e-9173-57ca254f80d2n%40googlegroups.com?utm_medium=email&utm_source=footer>.

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/74855666-cabc-4768-a926-e09fbbd11cae%40ilbers.de.

  reply	other threads:[~2026-04-23  9:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-23  9:11 Ulrich Teichert
2026-04-23  9:26 ` Anton Mikanovich [this message]
2026-04-23  9:37   ` AW: " Ulrich Teichert

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=74855666-cabc-4768-a926-e09fbbd11cae@ilbers.de \
    --to=amikan@ilbers.de \
    --cc=isar-users@googlegroups.com \
    --cc=ulrich.teichert@kumkeo.de \
    /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