Missing dep8 tests

We were recently hit by bug #1956833, where GSS-SPNEGO was suddenly disabled and nobody noticed until an app tried to use it.

For that case, I'm thinking about a very simple test that would be like this:

for algo in $ALGORITHMS; do
  saslpluginviewer -m $algo > /dev/null || {
    echo "Algorithm $algo not available"
    exit 1
  }
done

And ALGORITHMS is a list of the algorithms we expect to always be available, like:
  SCRAM-SHA-1 SCRAM-SHA-256 GS2-IAKERB GS2-KRB5 GSS-SPNEGO GSSAPI DIGEST-MD5 EXTERNAL CRAM-MD5 NTLM PLAIN LOGIN ANONYMOUS

Sent new dep8 tests to debian, and then synced the package back into ubuntu:
https://launchpad.net/ubuntu/+source/cyrus-sasl2/2.1.28+dfsg-5

Fixed in https://launchpad.net/ubuntu/+source/cyrus-sasl2/2.1.28+dfsg-6

Hello Joshua, or anyone else affected,

Accepted cyrus-sasl2 into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cyrus-sasl2/2.1.27+dfsg2-3ubuntu1.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

All autopkgtests for the newly accepted cyrus-sasl2 (2.1.27+dfsg2-3ubuntu1.1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

python-bonsai/1.3.0+ds-3build1 (armhf)
librdkafka/1.8.0-1build1 (amd64)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/jammy/update_excuses.html#cyrus-sasl2

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

The tests are green, except for i386 which has "always" been red due to dependency problems.

The new tests ran fine in all architectures:

(paste from amd64, it's the same for the others)
autopkgtest [00:21:02]: @@@@@@@@@@@@@@@@@@@@ summary
pluginviewer PASS
saslauthd PASS
gssapi PASS
shared-secret-mechs PASS

Jammy verification succeeded.

This bug was fixed in the package cyrus-sasl2 - 2.1.27+dfsg2-3ubuntu1.1

---------------
cyrus-sasl2 (2.1.27+dfsg2-3ubuntu1.1) jammy; urgency=medium

  * Add SASL channel binding support for GSSAPI and GSS-SPNEGO
    (LP: #1912256):
    - d/p/0034-channel-binding-gssapi-gss-spnego.patch: add SASL channel
      binding support for GSSAPI and GSS-SPNEGO
    - d/p/0035-Add-support-for-setting-max-ssf-0-to-GSS-SPNEGO-1.patch:
      allow setting maxssf to 0 when using GSS-SPNEGO inside SSL/TLS
    - d/p/0035-Add-support-for-setting-max-ssf-0-to-GSS-SPNEGO-2.patch:
      be more conformant to RFC4752
  * Add some DEP8 tests (LP: #1677781):
    - d/t/{control,saslauthd}: saslauthd tests with multiple mechanisms
    - d/t/{control,gssapi}: test for SASL GSSAPI using OpenLDAP
    - d/t/{control,pluginviewer}: test available mechanisms
    - d/t/{control,shared-secret-mechs}: test shared secret mechanisms

 -- Lena Voytek <email address hidden> Wed, 19 Oct 2022 14:06:40 -0700

The verification of the Stable Release Update for cyrus-sasl2 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.