From: "'MOESSBAUER, Felix' via isar-users" <isar-users@googlegroups.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: breaking change on Trixie: deb822 style sources file needed
Date: Thu, 23 Jan 2025 07:46:52 +0000 [thread overview]
Message-ID: <7e14b796c57bea7cc9033a0853ec6d727c541880.camel@siemens.com> (raw)
Hi,
the "apt" tool was recently updated in Debian Trixie to version 2.9.24.
This update brings the following breaking change:
apt (2.9.24) unstable; urgency=medium
/etc/apt/trusted.gpg is no longer trusted. Setting the
Dir::Etc::trusted
option manually continues to work for some more time.
sources.list(5) entries without the Signed-By field are deprecated;
migrate any legacy entries to the deb822 .sources format. See the
apt-secure(7) manual page for best practices for signer
configuration.
This deprecates the /etc/apt/trusted.gpg.d directory.
By that, we need a signed-by per entry (i.e. deb [signed-
by=/usr/share/...] in the pre deb822 format. Further, it deprecates the
pre deb822 format and already prints warnings if the format is used.
To switch over to deb822, a lot of infrastructure around the handling
of the sources needs to be changed in ISAR.
Best regards,
Felix
--
Siemens AG
Linux Expert Center
Friedrich-Ludwig-Bauer-Str. 3
85748 Garching, Germany
--
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/7e14b796c57bea7cc9033a0853ec6d727c541880.camel%40siemens.com.
reply other threads:[~2025-01-23 7:47 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=7e14b796c57bea7cc9033a0853ec6d727c541880.camel@siemens.com \
--to=isar-users@googlegroups.com \
--cc=felix.moessbauer@siemens.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