2.3.18 came out in Feb as anticipated, and I've taken a look at it.

Locally, it builds ok for me, but there's one autopkgtest failure:

buffer_replace() ..................................................... : ok
test-buffer-istream.c:54: Assert failed: buffer_append_full_file(result, 
TEST_FILENAME, SIZE_MAX, &error) == BUFFER_APPEND_READ_ERROR
test-buffer-istream.c:56: Assert failed: error != NULL && *error != '\0'
buffer_append_full_file .............................................. : FAILED
buffer_append_full_istream ........................................... : ok

This seems different than the crash found earlier.

Additionally, building in PPA results in another test failure in dcrypt-
openssl.c, although the line numbers are different than the test failure
I saw with .17 so this might not be the same issue:

test_get_info_pw_encrypted ........................................... : ok
test-crypto.c:827: Assert failed: ret == TRUE
Panic: file dcrypt-openssl.c: line 2639 (dcrypt_openssl_private_to_public_key): 
assertion failed: (priv_key != NULL && pub_key_r != NULL)
Error: Raw backtrace: #0 fatal_handler_real[0x55bdb62b4820] -> #1 
default_fatal_handler[0x55bdb62b48f0] -> #2 i_panic[0x55bdb62a25f6] -> #3 
dcrypt_openssl_private_to_public_key.cold[0x7f299c256b39] -> #4 
test_password_change[0x55bdb62aced0] -> #5 test_run_funcs[0x55bdb62b0690] -> #6 
test_run[0x55bdb62b1270] -> #7 main[0x55bdb62a6be0] -> #8 
__libc_init_first[0x7f299c2bcd10] -> #9 __libc_start_main[0x7f299c2bcdc0] -> 
#10 _start[0x55bdb62a6d40]
/bin/bash: line 1: 83276 Aborted                 (core dumped) ./$bin
make[4]: *** [Makefile:1136: check-local] Error 1
make[4]: Leaving directory '/<<PKGBUILDDIR>>/src/lib-dcrypt'
make[3]: *** [Makefile:983: check-am] Error 2

Given that the 2.3.16 we already have in jammy does not have test/build
issues, and that I'm not aware of anything compelling us to need the
newer versions, I think we should stick with the stable 2.3.16 release
for jammy.  Individual fixes can be cherrypicked in as needed, and we'll
work on getting 2.3.18's issues figured out for Ubuntu 22.10.


** Changed in: dovecot (Ubuntu)
       Status: Incomplete => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959624

Title:
  Re-merge dovecot for jammy (v2.3.18?)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1959624/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to