Thank you for contributing the fix for this!
The changes look good to me and I'll accept these into jammy-proposed
shortly.
I would like a couple of things thought about with regard to testing
though please:
1) It's a hard requirement that a test be performed to ensure that the
package still works. Things in our build environment can change (eg.
build dependency changes), so it's not sufficient to verify this from
code changes alone. Users not caring about krb5 support would quite
reasonably be upset if we didn't test the update at all before releasing
it. Please add a smoke test (at a minimum) to the Test Plan to ensure
that normal use of the package still works at all. Using a reverse
dependency that exercises the library would be fine. If this is already
covered by automated testing then that's also fine - please point out
where that testing is though then please.
2) We're fixing krb5 support so it'd be nice to actually check that krb5
support fully works before releasing this, rather than find that there
was some other issue later. I recognise that you said:
> * I believe the fix is non-intrusive enough that no further testing
is needed.
...but if there's some other problem with krb5, then that wouldn't show
up.
Given that we're trying to fix krb5 for users, could we please ensure
that krb5 functionality is tested before we release this to jammy-
updates?
It's OK to combine these two requests into one test.
** Changed in: neon27 (Ubuntu)
Status: Confirmed => Fix Released
** Tags added: verification-needed verification-needed-jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2003266
Title:
22.04 package lacks GSSAPI support
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/neon27/+bug/2003266/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
