Now performing a release upgrade to kinetic with the system in the above state:
- like before, the summary presents that two (unrelated to cyrus-sasl2) packages will be removed
- in the end, 13 unrelated packages were removed:
13 packages are going to be removed.
Jammy verification (continued), test (d)
d) It's now possible to have SCRAM and gssapi heimdal mechanisms installed at the same time
Start with SCRAM available on jammy, by installing the gssapi-mit package:
$ sudo apt install libsasl2- modules- gssapi- mit x86_64- linux-gnu/ sasl2/libscram. so.2 x86_64- linux-gnu/ sasl2/libscram. so.2 -> libscram.so.2.0.25
...
$ ll /usr/lib/
lrwxrwxrwx 1 root root 18 Oct 19 21:06 /usr/lib/
$ dpkg -S /usr/lib/ x86_64- linux-gnu/ sasl2/libscram. so.2 modules- gssapi- mit:amd64: /usr/lib/ x86_64- linux-gnu/ sasl2/libscram. so.2
libsasl2-
Confirming that installing libsasl2- modules- gssapi- heimdal from jammy removes libsasl2- modules- gssapi- mit:
$ sudo apt install libsasl2- modules- gssapi- heimdal modules- gssapi- mit
(...)
The following packages will be REMOVED:
libsasl2-
And that removes the SCRAM module with it.
Switching to jammy-proposed, however, while still removing libsasl2- modules- gssapi- mit, will NOT remove the SCRAM module:
$ dpkg -l | grep -E "^ii.*sasl2" | awk '{print $2,$3}' dfsg2-3ubuntu1. 1 modules: amd64 2.1.27+ dfsg2-3ubuntu1. 2 modules- db:amd64 2.1.27+ dfsg2-3ubuntu1. 1 modules- gssapi- heimdal: amd64 2.1.27+ dfsg2-3ubuntu1. 2
libsasl2-2:amd64 2.1.27+
libsasl2-
libsasl2-
libsasl2-
$ apt-cache policy libsasl2-modules dfsg2-3ubuntu1. 2 dfsg2-3ubuntu1. 2 dfsg2-3ubuntu1. 2 500 br.archive. ubuntu. com/ubuntu jammy-proposed/main amd64 Packages dpkg/status 1.27+dfsg2- 3ubuntu1. 1 500 br.archive. ubuntu. com/ubuntu jammy-updates/main amd64 Packages 1.27+dfsg2- 3ubuntu1 500 br.archive. ubuntu. com/ubuntu jammy/main amd64 Packages
libsasl2-modules:
Installed: 2.1.27+
Candidate: 2.1.27+
Version table:
*** 2.1.27+
500 http://
100 /var/lib/
2.
500 http://
2.
500 http://
And even though we no longer have libsasl2- modules- gssapi- mit (due to the expected conflict with -heimdal), the SCRAM module is available:
$ ll /usr/lib/ x86_64- linux-gnu/ sasl2/libscram. so.2 x86_64- linux-gnu/ sasl2/libscram. so.2 -> libscram.so.2.0.25
lrwxrwxrwx 1 root root 18 Dec 12 11:52 /usr/lib/
$ dpkg -S /usr/lib/ x86_64- linux-gnu/ sasl2/libscram. so.2 modules: amd64: /usr/lib/ x86_64- linux-gnu/ sasl2/libscram. so.2
libsasl2-
Now performing a release upgrade to kinetic with the system in the above state:
- like before, the summary presents that two (unrelated to cyrus-sasl2) packages will be removed
- in the end, 13 unrelated packages were removed:
13 packages are going to be removed.
Continue [yN] Details [d]d x86-64- linux-gnu inetutils-telnet libbinutils
Remove (was auto installed) binutils binutils-common
binutils-
libctf-nobfd0 libctf0 libdns-export1110 libgprofng0 libicu70
libisc-export1105 python3-openssl telnet
After the release upgrade, these were the sasl2 packages installed (from kinetic): dfsg-6ubuntu2 modules: amd64 2.1.28+ dfsg-6ubuntu2 modules- db:amd64 2.1.28+ dfsg-6ubuntu2 modules- gssapi- heimdal: amd64 2.1.28+ dfsg-6ubuntu2
$ dpkg -l | grep sasl2 | awk '{print $2,$3}'
libsasl2-2:amd64 2.1.28+
libsasl2-
libsasl2-
libsasl2-
$ apt-cache policy libsasl2-modules dfsg-6ubuntu2 dfsg-6ubuntu2 dfsg-6ubuntu2 500 br.archive. ubuntu. com/ubuntu kinetic/main amd64 Packages dpkg/status
libsasl2-modules:
Installed: 2.1.28+
Candidate: 2.1.28+
Version table:
*** 2.1.28+
500 http://
100 /var/lib/
And SCRAM remained available: x86_64- linux-gnu/ sasl2/libscram. so.2 x86_64- linux-gnu/ sasl2/libscram. so.2 -> libscram.so.2.0.25
$ ll /usr/lib/
lrwxrwxrwx 1 root root 18 Aug 16 2022 /usr/lib/
$ dpkg -S /usr/lib/ x86_64- linux-gnu/ sasl2/libscram. so.2 modules: amd64: /usr/lib/ x86_64- linux-gnu/ sasl2/libscram. so.2
libsasl2-
Test (d) succeeded.