Your message dated Sat, 12 Apr 2025 16:15:12 +0000
with message-id <[email protected]>
and subject line Bug#1053462: fixed in debian-security-support 1:13+2025.04.12
has caused the Debian Bug report #1053462,
regarding debian-security-support: merge .ended and .limited files together
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 [email protected]
immediately.)
--
1053462: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053462
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: debian-security-support
Severity: normal
El 27/09/23 a las 09:25, Raphael Hertzog escribió:
> Hi,
>
> On Tue, 26 Sep 2023, Santiago Ruano Rincón wrote:
> > > > Agreed, a split makes sense, it causes marginal additional overhead and
> > > > makes
> > > > the whole setup more explicit.
> > >
> > > cloning this bug once more so we don't forget about this.
> >
> > (I think the moreinfo tag comes from the original bug)
> >
> > I hope this MR correctly splits the limited support file:
> > https://salsa.debian.org/debian/debian-security-support/-/merge_requests/17
>
> As I commented on the MR, I think it would be a good move to merge "ended"
> and "limited" files together. This will require more code changes but
> gives a clearer overview of the restrictions affecting a given release.
>
> We could have a single file per release with 3 fields:
>
> * package (or package regexp)
> * supported (true/false), trues implies limited support, false means not
> supported
> * comment (should explain the limitation if supported == true)
>
> We could keep an unversioned file (for unstable?) that would serve as
> template when we have to create a new release.
Since #975301 has been closed now, I think this should be discussed in a
new bug report.
I like the above suggestion. Just wondering why don't keep the "latest
version with support" and "Date when support ended or will end" fields
currently found in "ended" files.
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: debian-security-support
Source-Version: 1:13+2025.04.12
Done: Holger Levsen <[email protected]>
We believe that the bug you reported is fixed in the latest version of
debian-security-support, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Holger Levsen <[email protected]> (supplier of updated debian-security-support
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Sat, 12 Apr 2025 18:00:29 +0200
Source: debian-security-support
Architecture: source
Version: 1:13+2025.04.12
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Team <[email protected]>
Changed-By: Holger Levsen <[email protected]>
Closes: 1053462
Changes:
debian-security-support (1:13+2025.04.12) unstable; urgency=medium
.
[ Jochen Sprickerhof ]
* Merge -ended and -limited files. Closes: #1053462.
.
[ Holger Levsen ]
* Declare trixie as stable, so these codepathes can be tested.
* README.source: update instructions what to do for new Debian releases, now
that -ended and -limited files have been merged.
Checksums-Sha1:
284a8196e118f5044c765d467c0e21ef607845d5 1908
debian-security-support_13+2025.04.12.dsc
6f3b676cfd2f93abfb8210d780e5d40c78516389 36292
debian-security-support_13+2025.04.12.tar.xz
5c77ac524c7ec87e80bd190c24287e931d2c3866 8021
debian-security-support_13+2025.04.12_source.buildinfo
Checksums-Sha256:
b371bae2cf8daea46614c4b50963b4fbe85497e2b2c840330e673a160e675f3d 1908
debian-security-support_13+2025.04.12.dsc
3c8e52f21217d1a77d96d0389363ca6b787b847236542c32511690217278d7ff 36292
debian-security-support_13+2025.04.12.tar.xz
55f6b4de48bc3087bf4a4b5162442b7fcd8f5578ef00f4686ffc256fa1b446c5 8021
debian-security-support_13+2025.04.12_source.buildinfo
Files:
3e3d4c780812a09f26ebe735a0200b6b 1908 admin optional
debian-security-support_13+2025.04.12.dsc
85b1c05cc4e8ee8cf136824adaa361e8 36292 admin optional
debian-security-support_13+2025.04.12.tar.xz
0045b19c031f6b729fb0cb7123013df5 8021 admin optional
debian-security-support_13+2025.04.12_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEuL9UE3sJ01zwJv6dCRq4VgaaqhwFAmf6jyUACgkQCRq4Vgaa
qhwnOQ//bc/RyE+1r6ukEdA8lZh/5GLcjcQdpBqzBBOdgaEa59p+QhFOHHBy2l6j
mk/xphMuiXOdbGXqFFaIZKiJGGdvOdX7ZWg73m/RpDWYu3oQ8WNKnZhY6Ed9Jl9A
gkUK4PuhdaqL/vSwB8amHP156T0yYKqLoXCDXISrq+2FgZ/vxPaELN8Jl+z/A8TS
SRhi5uXO/e9RqypyVxRP5kwp6L8zEHyZ06c1qciirdYXF2kYL0ZghAXIRuM5h5Aw
FuduYU39eD0Yvb4N0OT4EVbjGQokZczwrI1S3DU5B12wxh0iHK0upg4Uh1cKTdfW
ilyOBHHg52/O4vTeQInjB4zDNoftcaepwA5sgXCj+NAVKUQikfcgaWr/DbjtqlCa
+OnZhcVWNDJJLJi3o+gDim1wAqNxoDCFZYtbQCVUsHRLSkiAFxklkPwb9qB89OlD
UosKSIxdkyUXEAGqp8wFN/0+kZ39I60BTy3ikGVpbUCWxuu2olDkZKqNXXoqxCN9
yQCMPnCzL4fMwjmFIAfQTfcFyf4QLIfINL1tXwzANN7V0cMgLZDMWcKXPo6Y9fMC
OsADatp+//zXAHrqosQ0iA+NTxRt/aQa0FcUy6P0IF053AkLqXua496YtBk5Uhou
7JjNQRCS62fLAuWvzXiV9ZaY+fBNbgzW/Lhz9GP7B9LIqivnz1M=
=5UZe
-----END PGP SIGNATURE-----
pgp1VOuTxLVAT.pgp
Description: PGP signature
--- End Message ---
