From: Baurzhan Ismagulov <ibr@radix50.net>
To: Isar users <isar-users@googlegroups.com>
Cc: Uladzimir Bely <ubely@ilbers.de>,
Cedric Hombourger <cedric.hombourger@siemens.com>
Subject: Re: [PATCH] dpkg: use find to create symlinks to downloaded .deb files vs ln -sf wildcard
Date: Wed, 28 Feb 2024 10:09:01 +0100 [thread overview]
Message-ID: <Zd74Lex2i12bGp1Y@ilbers.de> (raw)
In-Reply-To: <494fd4502c156b657994cc20be133946df33e81c.camel@siemens.com>
On 2024-02-27 09:46, 'cedric.hombourger@siemens.com' via isar-users wrote:
> > The patch itself is worth applying and we'll pass it through CI right
> > now.
>
> Sure thing. FWIW, I used ci_build -T fast for a quick non-regression
> tests and no failures were reported.
Thanks, this is a big help.
> Let me know if you see any issues with your full CI test.
Full CI has passed. Uladzimir has also reviewed the patch; we will merge it
before 0.10.
> I came across this issue while doing a clean build against our base-apt
> feeds. The generated base-apt.list file reads (there are more feeds
> than just base in our case but all follow the same pattern and I am
> only showing the base feed for brevity)
>
> deb file:///base-apt/base bookworm build debug extra main
>
> Here we only have (as expected) only file:// feed(s) => apt will not
> download anything in /var/cache/apt/archives/
Independently of merging this one, do you see a possibility to prepare a
testcase for that?
With kind regards,
Baurzhan
next prev parent reply other threads:[~2024-02-28 9:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 9:55 Cedric Hombourger
2024-02-26 10:08 ` cedric.hombourger
2024-02-27 9:10 ` Uladzimir Bely
2024-02-27 9:46 ` cedric.hombourger
2024-02-27 11:40 ` Uladzimir Bely
2024-02-28 9:09 ` Baurzhan Ismagulov [this message]
2024-02-29 13:17 ` Uladzimir Bely
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=Zd74Lex2i12bGp1Y@ilbers.de \
--to=ibr@radix50.net \
--cc=cedric.hombourger@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=ubely@ilbers.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