Performing verification for openssl on Focal.
An affected user performed the verification, due to c7g instance types
being in "Preview" state on Amazon AWS, and not generally accessible.
The user started a c7g instance, and checked they had openssl
1.1.1f-1ubuntu2.10 from -updates.
They
All autopkgtests for the newly accepted openssl (1.1.1f-1ubuntu2.11) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
python3.8/3.8.10-0ubuntu1~20.04.2 (armhf, amd64)
linux-hwe-5.11/5.11.0-60.60 (amd64)
** Changed in: landscape-client (Ubuntu Bionic)
Assignee: Simon Poirier (simpoir) => (unassigned)
** Changed in: landscape-client (Ubuntu Focal)
Assignee: Simon Poirier (simpoir) => (unassigned)
** Changed in: landscape-client (Ubuntu Groovy)
Assignee: Simon Poirier (simpoir) =>
This was a perfectly researched and written up bug and patch and made
SRU review easy. Thank you!
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1960863
Title:
armv8 paca: poly1305 users
Hello Matthew, or anyone else affected,
Accepted openssl into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openssl/1.1.1f-1ubuntu2.11 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
> However, Focal (which uses klibc 2.0.7) uses dhclient for networking
initialization instead of ipconfig...
If no users in Focal could be affected by the bug then I'm fine with
accepting the fix to Bionic only. But could you please expand on the
above statement? Under what conditions does Focal
6 matches
Mail list logo
