From: Andreas Pretzsch <apr@cn-eng.de>
To: ptxdist@pengutronix.de
Subject: [ptxdist] Documentation: Pre-Built Toolchain installation on Ubuntu: minor glitches or outdated
Date: Mon, 17 Apr 2023 22:59:13 +0200 [thread overview]
Message-ID: <84dfdc59f16242e3e6fa495cc2a28d3fff5409f5.camel@cn-eng.de> (raw)
Following the documentation about installation of an OSELAS.Toolchain
from Pengutronix Debian Archive [1] on a (mostly) fresh Ubuntu 22.04
derived installation, I ran into some details.
Don't know about stock Debian resp. apt-get instead of apt behaviour,
but I assume the same applies.
According to docs, added "/etc/apt/sources.list.d/pengutronix.list" as:
deb https://debian.pengutronix.de/debian/ jammy main contrib non-free
Result:
# apt update
[...]
Get:11 https://debian.pengutronix.de/debian jammy InRelease [4.042 B]
Err:11 https://debian.pengutronix.de/debian jammy InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 69E81E916B7A3E09 NO_PUBKEY 94F58BAD054406A9
Reading package lists... Done
W: GPG error: https://debian.pengutronix.de/debian jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 69E81E916B7A3E09 NO_PUBKEY 94F58BAD054406A9
E: The repository 'https://debian.pengutronix.de/debian jammy InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
# apt install pengutronix-archive-keyring
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package pengutronix-archive-keyring
Plausible, as list was not installed above, due to missing key.
So I manually fetched and installed (dpkg -i) the keyring:
https://debian.pengutronix.de/debian/pool/main/p/pengutronix-archive-keyring/pengutronix-archive-keyring_2023.01.09_all.deb
Now, package list is downloaded and used, but with some annoyance about
missing arch in repo:
# apt update
[...]
Get:8 https://debian.pengutronix.de/debian jammy/main amd64 Packages [14,9 kB]
[...]
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
N: Skipping acquire of configured file 'main/binary-i386/Packages' as repository 'https://debian.pengutronix.de/debian jammy InRelease' doesn't support architecture 'i386'
N: Skipping acquire of configured file 'contrib/binary-i386/Packages' as repository 'https://debian.pengutronix.de/debian jammy InRelease' doesn't support architecture 'i386'
N: Skipping acquire of configured file 'non-free/binary-i386/Packages' as repository 'https://debian.pengutronix.de/debian jammy InRelease' doesn't support architecture 'i386'
Limited "/etc/apt/sources.list.d/pengutronix.list" accordingly, by
adding "[arch=amd64]", so we now have:
deb [arch=amd64] https://debian.pengutronix.de/debian/ jammy main contrib non-free
Final result is a working setup, without any annoying warnings.
Unfortunately, I'm busy setting up a customer VM, so I'll just throw in
these pointers, instead of trying to find a suitable updated wording
for the docs, sorry.
Best regards,
Andreas
[1]
https://www.ptxdist.org/doc/environment.html#add-the-pengutronix-debian-archive
--
carpe noctem engineering
Ingenieurbuero fuer Hard- & Software-Entwicklung Andreas Pretzsch
Dipl.-Ing. (FH) Andreas Pretzsch Tel. +49-(0)711-3908735-7
Tuebinger Strasse 63 Fax: +49-(0)711-3908735-9
70178 Stuttgart, Germany email: apr@cn-eng.de
reply other threads:[~2023-04-17 20:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=84dfdc59f16242e3e6fa495cc2a28d3fff5409f5.camel@cn-eng.de \
--to=apr@cn-eng.de \
--cc=ptxdist@pengutronix.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