public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Kazunori Kobayashi <kazunori.kobayashi@miraclelinux.com>
To: Florian Bezdeka <florian.bezdeka@siemens.com>,
	isar-users@googlegroups.com
Cc: hiraku.toyooka@miraclelinux.com, masami.ichikawa@miraclelinux.com
Subject: Re: [PATCH] dpkg-source: Export proxy settings
Date: Wed, 29 Oct 2025 10:43:03 +0900	[thread overview]
Message-ID: <e272142d-c48b-4818-ad54-6795164aa03e@miraclelinux.com> (raw)
In-Reply-To: <c3564d3205b64dc2f219c9cf35ba20b3656296f6.camel@siemens.com>

Hi,

On 10/28/25 20:59, Florian Bezdeka wrote:
> On Tue, 2025-10-28 at 10:35 +0900, Kazunori Kobayashi wrote:
>> This sets proxy environment variables to be passed to schroot.
> I see, but could you please elaborate a bit more why this is actually
> needed? What goes wrong at the moment? Why do you need networking
> inside the schroot environment?
>
> Best regards,
> Florian

I assume Isar considers networking via proxy in such as downloading 
something in do_fetch, resolving dependencies in do_dpkg_build and 
package installation on the target root filesystem in do_rootfs_install. 
We can actually use it in such typical cases with no problem.

This change has effect on a very limited case, where a self-built 
package fetching a source package via the apt:// scheme in SRC_URI is 
specified as a native package (<package>-native) to IMAGE_INSTALL or 
SDK_INSTALL. In this case, the source package is fetched via apt-get in 
schroot in do_fetch_common_source but proxy environment variables are 
not set in the executing shell function.

Isar would overlook this case compared to other fetching cases 
considering proxy and this change is to improve it.

Regards,
Kazunori


>
>> Signed-off-by: Kazunori Kobayashi <kazunori.kobayashi@miraclelinux.com>
>> ---
>>   meta/classes/dpkg-source.bbclass | 2 ++
>>   1 file changed, 2 insertions(+)
>>
>> diff --git a/meta/classes/dpkg-source.bbclass b/meta/classes/dpkg-source.bbclass
>> index 4877abd6..a16e5812 100644
>> --- a/meta/classes/dpkg-source.bbclass
>> +++ b/meta/classes/dpkg-source.bbclass
>> @@ -65,6 +65,8 @@ do_fetch_common_source() {
>>       trap 'exit 1' INT HUP QUIT TERM ALRM USR1
>>       trap 'schroot_cleanup' EXIT
>>   
>> +    E="${@ isar_export_proxies(d)}"
>> +
>>       schroot -r -c ${session_id} -d / -u root -- \
>>           apt-get update -o Dir::Etc::SourceList="sources.list.d/isar-apt.list" -o Dir::Etc::SourceParts="-" -o APT::Get::List-Cleanup="0"
>>       schroot -r -c ${session_id} -d / -- \
>> -- 
>> 2.39.5
>>
>> -- 
>> 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/20251028013532.1388325-1-kazunori.kobayashi%40miraclelinux.com.


-- 
Kazunori Kobayashi
Cybertrust Japan Co., Ltd.
https://www.cybertrust.co.jp/

-- 
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/e272142d-c48b-4818-ad54-6795164aa03e%40miraclelinux.com.

  reply	other threads:[~2025-10-29  1:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-28  1:35 Kazunori Kobayashi
2025-10-28 11:59 ` 'Florian Bezdeka' via isar-users
2025-10-29  1:43   ` Kazunori Kobayashi [this message]
2025-10-29 13:53     ` 'Florian Bezdeka' via isar-users
2025-10-30  2:36       ` Kazunori Kobayashi
2025-10-30  9:37         ` [PATCH v2] " Kazunori Kobayashi
2025-10-30  9:48         ` [PATCH] " Kazunori Kobayashi
2025-10-30 10:13         ` 'Florian Bezdeka' via isar-users
2025-10-30 12:30           ` Kazunori Kobayashi

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=e272142d-c48b-4818-ad54-6795164aa03e@miraclelinux.com \
    --to=kazunori.kobayashi@miraclelinux.com \
    --cc=florian.bezdeka@siemens.com \
    --cc=hiraku.toyooka@miraclelinux.com \
    --cc=isar-users@googlegroups.com \
    --cc=masami.ichikawa@miraclelinux.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