Le 25/05/2023 à 10:06, Hans a écrit :
Hi folks,
just a little thing, I am somehow confused about.
I read that debian/testing is now in state "freeze" as the next release is
shortly to come.
As I running "bookworm" now, I am wondering, that debian/testing (aka
bookworm), still gets a lot of changed packages last days.
Obviously I seem to misunderstand the meaning of "freeze".
Does "freeze" mean "No new packages" od does it mean "actual packages in
testing will not be changed any more till next release".
What did I not understand? For me "freeze" means "stay at actual status and do
only necessary changes for security or breaking reasons".
There are almost a hundered packages I got untill "freeze" and my change to
bookworm (aka testing).
If you look at the changelogs, you'll see that those upgrades are either
because of security corrections, or to handle packaging or upgrade problems
eg (today upgrade for me)
--- Changes for texlive-bin (texlive-binaries libptexenc1 libsynctex2
libtexlua53-5 libtexluajit2 libkpathsea6) ---
texlive-bin (2022.20220321.62855-5.1) unstable; urgency=high
* Non-maintainer upload.
* Fix improperly secured shell-escape in LuaTeX (CVE-2023-32700)
-- Salvatore Bonaccorso <car...@debian.org> Thu, 18 May 2023 23:15:13
+0200
--- Changes for boost1.74 (libboost-chrono1.74.0
libboost-filesystem1.74.0 libboost-iostreams1.74.0 libboost-thread1.74.0
libboost-locale1.74.0 libboost-program-options1.74.0
libboost-python1.74.0 libboost-regex1.74.0 libboost1.74-dev) ---
boost1.74 (1.74.0+ds1-21) unstable; urgency=medium
[ Andreas Beckmann ]
* [f41f9a1] libboost-thread1.74.0: Add Breaks:
libboost-regex1.74.0-icu67 for
smoother upgrades from bullseye. (Closes: #1036070)
-- Anton Gladky <gl...@debian.org> Fri, 19 May 2023 09:24:56 +0200
(output of apt-changelogs)
freeze is that the software at kept at the same versions so that the
teams preparing the distribution can concentrate on those problems.
