public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Subject: Re: [PATCH 1/2] meta/classes/rootfs: carry bootstrap list file until the image rootfs
Date: Wed, 7 May 2025 15:19:54 +0200	[thread overview]
Message-ID: <aBtd-oPjRmdz1m0M@abai.de> (raw)
In-Reply-To: <20250403125857.2525698-1-srinuvasan.a@siemens.com>

On 2025-04-03 18:28, srinuvasan.a via isar-users wrote:
> From: srinuvasan <srinuvasan.a@siemens.com>
> 
> If the user selects a different debian mirror (http://ftp.de.debian.org)
> by using DISTRO_APT_PREMIRRORS to pull the packages, the proper list
> updated in the bootstrap rootfs and buildchroot rootfs, but in the imag rootfs
> it contains the upstream list rather than the selected debian mirror.
> 
> Due to this issue in the deb-src caching stage, we are copying the packages
> state (/var/lib/apt/lists) from the bootstrap rootfs to the image rootfs,
> With the present implementation, we are copying (http://ftp.de.debian.org)
> list to image rootfs's var/lib/apt/lists but image rootfs /etc/apt/sources.list.d
> contains the upstream (http://deb.debian.org) list.
> 
> With this mismatch list, it throws the below error during the deb-src download stage
> 
> Logs:
> 
> Reading package lists... Done
> E: You must put some 'deb-src' URIs in your sources.list
> 
> Make sure the selected debian list available till the image rootfs, except
> user can define their own list in SRC_URI.
> 
> Signed-off-by: srinuvasan <srinuvasan.a@siemens.com>

Applied to next, thanks.

With kind regards,
Baurzhan

-- 
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/aBtd-oPjRmdz1m0M%40abai.de.

      parent reply	other threads:[~2025-05-07 13:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-10 11:51 [PATCH 0/1] Fix deb-src caching issue srinuvasan.a via isar-users
2025-03-10 11:51 ` [PATCH 1/1] image: move deb-src-caching functionality after image creation srinuvasan.a via isar-users
2025-03-18 16:45   ` 'Arjunan, Srinu' via isar-users
2025-03-20  5:31     ` Uladzimir Bely
2025-03-20  7:18       ` 'Arjunan, Srinu' via isar-users
2025-03-20  8:27         ` 'cedric.hombourger@siemens.com' via isar-users
2025-03-20 17:56         ` Uladzimir Bely
2025-03-20 18:02           ` 'cedric.hombourger@siemens.com' via isar-users
2025-03-21  5:32             ` Uladzimir Bely
2025-03-21  6:27         ` Uladzimir Bely
2025-03-21  6:32           ` 'cedric.hombourger@siemens.com' via isar-users
2025-03-21  7:06             ` Uladzimir Bely
2025-03-21  8:39             ` Uladzimir Bely
2025-03-21 13:50               ` 'cedric.hombourger@siemens.com' via isar-users
2025-03-27 16:55                 ` Srinuvasan Arjunan
2025-04-03 12:58                   ` [PATCH 1/2] meta/classes/rootfs: carry bootstrap list file until the image rootfs srinuvasan.a via isar-users
2025-04-03 12:58                     ` [PATCH 2/2] image: move deb-src-caching functionality after image creation srinuvasan.a via isar-users
2025-05-07 13:19                     ` Baurzhan Ismagulov [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=aBtd-oPjRmdz1m0M@abai.de \
    --to=ibr@radix50.net \
    --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