From: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
To: isar-users@googlegroups.com
Subject: after system update a strange erron about schroot
Date: Fri, 25 Nov 2022 01:47:57 +0100 [thread overview]
Message-ID: <CAJGKYO63d3fYhdu8TfPW4fGH21zSXZakNiyP0J9zeNnfsKhiCg@mail.gmail.com> (raw)
Hi all,
I recently updated my system and then I tried a run of my usual
building but it is broken with a strange error about schroot in many
receipts. Also those are ISAR standards like the ssh key generation.
Someone could give me a hint? Thanks, R-
| Package: sshd-regen-keys
| Version: 0.4
| Source Version: 0.4
| Distribution: isar
| Machine Architecture: amd64
| Host Architecture: amd64
| Build Architecture: amd64
| Build Type: binary
|
| E: 15killprocs: E: Failed to execute “15killprocs”: Exec format error
| E: isar-builder-a0f06e58-8115-475d-9417-3755d8a08896-100-ea5aba2a-0d77-493c-94d9-264d5950e06b:
Chroot setup failed: stage=setup-start
| Chroot setup failed
| E: Error creating chroot session: skipping sshd-regen-keys
next reply other threads:[~2022-11-25 0:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-25 0:47 Roberto A. Foglietta [this message]
2022-11-25 1:33 ` Roberto A. Foglietta
2022-11-25 2:09 ` Roberto A. Foglietta
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=CAJGKYO63d3fYhdu8TfPW4fGH21zSXZakNiyP0J9zeNnfsKhiCg@mail.gmail.com \
--to=roberto.foglietta@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