Your message dated Mon, 04 Nov 2024 18:19:43 +0000
with message-id <e1t81fz-0031af...@fasolo.debian.org>
and subject line Bug#1079961: Removed package(s) from unstable
has caused the Debian Bug report #880220,
regarding should not install a globally valid trust anchor
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
880220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880220
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: leap-archive-keyring
Version: 2016.03.08
Severity: normal
This package installs a keyring in /etc/apt/trusted.gpg.d which is
great as it allows people to easily install LEAP applications by
leveraging the trust path already in Debian.
It does, however, mean that LEAP could, in theory, sign releases for
the official Debian archive, which is probably not what you
want. There are some efforts underway to standardize a process for
third-party repositories like LEAP, and the current proposal is to
store those certificates in /usr/share/keyrings/ instead. See:
https://wiki.debian.org/DebianRepository/UseThirdParty#OpenPGP_Key_distribution
Then that key can be refered to in the sources.list, which connects
the repository with its trust anchor without polluting the global
trust space:
deb [signed-by=/usr/share/keyrings/deriv-archive-keyring.gpg]
https://deriv.example.net/debian/ stable main
In the case of LEAP, this would probably be something like:
sudo sh -c 'echo "deb [signed-by=/usr/share/keyrings/leap-archive-keyring.gpg]
http://deb.leap.se/client release stretch" >
/etc/apt/sources.list.d/bitmask.list'
I would also recommend setting up a pinned preferences file in the
archive as well, to keep the sources.list from upgrading random
packages from the main archive. I guess the preferences file could
look something like:
Package: bitmask* python-sqlcipher python-leap-common soledad*
Pin: origin deb.leap.se
Pin-Priority: 100
I would be happy to help you make those changes if you accept.
A.
-- System Information:
Debian Release: 9.1
APT prefers stable
APT policy: (500, 'stable'), (1, 'experimental'), (1, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8),
LANGUAGE=fr_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 2017.11.24+nmu1+rm
Dear submitter,
as the package leap-archive-keyring has just been removed from the Debian
archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/1079961
The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)
--- End Message ---
