I'm guessing this has been solved, since the binaries in the release
pocket are linked against libssl3 :)
** Changed in: ovn (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Marking as Confirmed as the FTBFS has actually hit the version currently
in the archive.
** Changed in: ovn (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for ovn (Ubuntu) because there has been no activity for 60
days.]
** Changed in: ovn (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946014
... and I can't reproduce the build failure, even when not enabling
-proposed (test on canonistack, s390x, adding the PPA to APT sources).
This is vexing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
So, the builds failed again. I'm looking into building it with -proposed
+ OpenSSL 3.0 on s390x.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946014
Title:
ovn: Fail to build against OpenSSL 3.0
My guess is that the issue was with a build-dep of ovn that has been
fixed in jammy somehow, and that as you suspect we're now just seeing
transient build failures. Retried both s390x and ppc64el, I'll keep you
informed :)
--
You received this bug notification because you are a member of Ubuntu
Thank you for raising this issue!
I am unfortunately not able to reproduce this when building against
OpenSSL 3.0 locally and running the test suite. I have tried both on
amd64 and on s390x to rule out any architecture specific issue.
Looking at the latest Jammy PPA rebuild [0] amd64, arm64 and
