From: Anton Mikanovich <amikan@ilbers.de>
To: Vladimir Burkin <mxvisor@gmail.com>
Cc: isar-users@googlegroups.com, Baurzhan Ismagulov <ibr@ilbers.de>
Subject: Re: [PATCH v2] Fix missing /var/lib/dpkg/available in Buster rootfs
Date: Mon, 22 Dec 2025 11:10:47 +0200 [thread overview]
Message-ID: <95be0ec8-bc14-4b0e-94ae-75d14d338ac5@ilbers.de> (raw)
In-Reply-To: <20251222090030.1922930-1-amikan@ilbers.de>
Hello Vladimir,
Thanks for submitting the patch.
I've resent your commit as v2 with some formatting applied.
Here is the way how we send patches for the review on the list:
- Send in text form (no attachments, no html allowed).
- Title should shortly describe the fix.
- Commit message should describe what is done and why it is done.
- Field Signed-off is required to point on commit authors.
- Field From is nice to have.
- Title ~50 symbols, commit message lines <72 symbols.
Sending the patch can be done from git itself by the command like:
git send-email -1 --subject-prefix="PATCH v2" --to
isar-users@googlegroups.com
where:
-1 - send 1 commit from the HEAD of current repo.
--subject-prefix="PATCH v2" - version 2 of patchset, can be just "PATCH"
for v1.
22/12/2025 11:00, Anton Mikanovich wrote:
> From: Vladimir Burkin <mxvisor@gmail.com>
>
> When building an image based on Debian Buster the rootfs installation
> fails on dpkg because /var/lib/dpkg/available is missing.
> isar-mmdebstrap.inc tries to work around this by adding an mmdebstrap
> hook. The hook uses touch /var/lib/dpkg/available, but it runs on the
> host rather than inside the mmdebstrap rootfs. The proposed fix is to
> use the hook parameter $1 (the mmdebstrap rootfs path) when creating
> the file.
>
> Signed-off-by: Vladimir Burkin <mxvisor@gmail.com>
> Signed-off-by: Anton Mikanovich <amikan@ilbers.de>
> ---
> meta/recipes-core/isar-mmdebstrap/isar-mmdebstrap.inc | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-core/isar-mmdebstrap/isar-mmdebstrap.inc b/meta/recipes-core/isar-mmdebstrap/isar-mmdebstrap.inc
> index 80b13a9e..73fe9434 100644
> --- a/meta/recipes-core/isar-mmdebstrap/isar-mmdebstrap.inc
> +++ b/meta/recipes-core/isar-mmdebstrap/isar-mmdebstrap.inc
> @@ -18,7 +18,7 @@ BOOTSTRAP_TMPDIR = "${WORKDIR}/tempdir"
> MM_HOOK_JESSIE = "/usr/share/mmdebstrap/hooks/jessie-or-older"
> DPKG_HOOKS ?= "${@'--hook-dir='+d.getVar('MM_HOOK_JESSIE') \
> if os.path.isdir(d.getVar('MM_HOOK_JESSIE')) \
> - else '--customize-hook=\'touch /var/lib/dpkg/available\''}"
> + else '--customize-hook=\'touch $1/var/lib/dpkg/available\''}"
> MMHOOKS:focal ?= "${DPKG_HOOKS}"
> MMHOOKS:buster ?= "${DPKG_HOOKS}"
>
--
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/95be0ec8-bc14-4b0e-94ae-75d14d338ac5%40ilbers.de.
next prev parent reply other threads:[~2025-12-22 9:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-22 9:00 Anton Mikanovich
2025-12-22 9:10 ` Anton Mikanovich [this message]
2026-01-05 9:21 ` Anton Mikanovich
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=95be0ec8-bc14-4b0e-94ae-75d14d338ac5@ilbers.de \
--to=amikan@ilbers.de \
--cc=ibr@ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=mxvisor@gmail.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