public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Srinuvasan Arjunan <srinuvasanasv@gmail.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH] classes/image-tools-extension.bbclass: remove prepare isar-apt part
Date: Sun, 7 Jan 2024 20:40:37 -0800 (PST)	[thread overview]
Message-ID: <5af8f7b9-aed0-4fbc-bbda-8bbed6330f08n@googlegroups.com> (raw)
In-Reply-To: <4468ef6f-5b19-4e1a-87cb-85c1edf10648@siemens.com>


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



On Friday, January 5, 2024 at 6:21:42 PM UTC+5:30 Jan Kiszka wrote:

On 05.01.24 12:15, Srinuvasan Arjunan wrote: 
> From: Srinuvasan <srinuv...@siemens.com> 
> 
> Now isar-apt configured during sbuildchroot generation, hence remove the 
prepare 
> isar-apt part from the imager_run method. 
> 
> This changes depends on [1] 
> 
> [1]: https://groups.google.com/g/isar-users/c/k8ZNw3OkWLw 
> 
> Signed-off-by: Srinuvasan <srinuv...@siemens.com> 
> --- 
> meta/classes/image-tools-extension.bbclass | 13 ------------- 
> 1 file changed, 13 deletions(-) 
> 
> diff --git a/meta/classes/image-tools-extension.bbclass 
b/meta/classes/image-tools-extension.bbclass 
> index 58799fcf..46bdf78b 100644 
> --- a/meta/classes/image-tools-extension.bbclass 
> +++ b/meta/classes/image-tools-extension.bbclass 
> @@ -44,19 +44,6 @@ imager_run() { 
> distro="${HOST_BASE_DISTRO}-${BASE_DISTRO_CODENAME}" 
> fi 
> 
> - # prepare isar-apt 
> - schroot -r -c ${session_id} -d / -u root -- sh -c " \ 
> - mkdir -p '/etc/apt/sources.list.d' 
> - echo 'deb [trusted=yes] file:///isar-apt ${DEBDISTRONAME} main' > \ 
> - '/etc/apt/sources.list.d/isar-apt.list' 
> - 
> - mkdir -p '/etc/apt/preferences.d' 
> - cat << EOF > '/etc/apt/preferences.d/isar-apt' 
> -Package: * 
> -Pin: release n=${DEBDISTRONAME} 
> -Pin-Priority: 1000 
> -EOF" 
> - 
> E="${@ isar_export_proxies(d)}" 
> deb_dl_dir_import ${schroot_dir} ${distro} 
> schroot -r -c ${session_id} -d / -u root -- sh -c " \ 

Good catch! I assume this is just redundant but harmless code now, 
right? If not, it should better be folded into a v4 of my patch. 

Jan 

-- 
Siemens AG, Technology 
Linux Expert Center 


   Yes, It is harmless, however we could cleanup this part due to 
redundant, Please fold this into V4.

     Srinu 

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

      reply	other threads:[~2024-01-08  4:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-05 11:15 Srinuvasan Arjunan
2024-01-05 12:51 ` Jan Kiszka
2024-01-08  4:40   ` Srinuvasan Arjunan [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=5af8f7b9-aed0-4fbc-bbda-8bbed6330f08n@googlegroups.com \
    --to=srinuvasanasv@gmail.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