Bug#1069603: [Pkg-openssl-devel] Bug#1069603: openssl breaks libcrypt-smime-perl autopkgtest: Crypt::SMIME#setPublicKeyStore: failed to store the public cert

2024-04-21 Thread Paul Gevers

Hi

On 21-04-2024 5:56 p.m., Sebastian Andrzej Siewior wrote:

The problem is that libcrypt-smime-perl < 0.29 fails with openssl >= 3.2.0.
This was solved by the Perl team with their 0.29 upload. This and 0.30
didn't migrate to testing and in the meantime we got OpenSSL into
unstable which relies on that fix.
The migration was delayed by the time_t transition.


Ack. I figured that out too.


Could britney be hinted to migrate both at the same time? This should
solve the issue you pointed out.


There is no "please test together" knob if that's what you mean (is that 
what you mean?). I have triggered the test manually, so for now the 
lights are green. Because those expire, I have added a hint to ignore 
the failure of the old version in testing.


Paul


OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1069603: [Pkg-openssl-devel] Bug#1069603: openssl breaks libcrypt-smime-perl autopkgtest: Crypt::SMIME#setPublicKeyStore: failed to store the public cert

2024-04-21 Thread Sebastian Andrzej Siewior
On 2024-04-21 13:42:03 [+0200], Paul Gevers wrote:

> opensslfrom testing3.2.1-3
> libcrypt-smime-perlfrom testing0.28-1
> all others from testingfrom testing
> 
> I copied some of the output at the bottom of this report.
> 
> Currently this regression is blocking the migration of openssl to testing
> [1]. Due to the nature of this issue, I filed this bug report against both
> packages. Can you please investigate the situation and reassign the bug to
> the right package?

The problem is that libcrypt-smime-perl < 0.29 fails with openssl >= 3.2.0. 
This was solved by the Perl team with their 0.29 upload. This and 0.30
didn't migrate to testing and in the meantime we got OpenSSL into
unstable which relies on that fix.
The migration was delayed by the time_t transition.

Could britney be hinted to migrate both at the same time? This should
solve the issue you pointed out.

Sebastian