Your message dated Thu, 28 May 2026 16:00:55 +0000
with message-id
<cam8zjqsfuu+tzzjdd7s7su8bsf0aohckbv7oj0aumui-58c...@mail.gmail.com>
and subject line Re: Bug#1133281: transition: libsodium
has caused the Debian Bug report #1133281,
regarding transition: libsodium
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.)
--
1133281: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1133281
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
Control: affects -1 + src:libsodium
User: [email protected]
Usertags: transition
Hi RMs,
There's a quick transition for libsodium, but I'm open to talk about
it. Reason is that there's an even newer libsodium soname release
that's not yet packaged.
Would it be a problem if libsodium is updated to 1.0.20 already in
experimental and then package release 1.0.22 causing another
transition? Should I go for a direct update to 1.0.22 instead?
All reverse build dependencies were built correctly. I had a problem
with vim, due to one of its self-tests saying it can't start a GUI or
something like that. I didn't investigate it further. For some reason,
I always have a problem with rebuilding vim due to its self-testing.
Thanks for consideration,
Laszlo/GCS
--- End Message ---
--- Begin Message ---
libsodium23 is gone from testing, closing
--- End Message ---
