Summary: | net-im/telegram-desktop-3.0.1 - /.../utils.cpp: error: FIPS_mode_set was not declared in this scope | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | Esteve Varela Colominas <esteve.varela> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | proxy-maint |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 818001 | ||
Bug Blocks: | 797325 | ||
Attachments: |
emerge-info.txt
emerge-history.txt environment etc.portage.tar.bz2 logs.tar.bz2 net-im:telegram-desktop-3.0.1:20210916-164153.log.bz2 temp.tar.bz2 |
Description
Toralf Förster
2021-09-16 17:17:48 UTC
Created attachment 739593 [details]
emerge-info.txt
Created attachment 739596 [details]
emerge-history.txt
Created attachment 739599 [details]
environment
Created attachment 739602 [details]
etc.portage.tar.bz2
Created attachment 739605 [details]
logs.tar.bz2
Created attachment 739608 [details]
net-im:telegram-desktop-3.0.1:20210916-164153.log.bz2
Created attachment 739611 [details]
temp.tar.bz2
Oh fun~, a breaking openssl update. I might drop this one until upstream or a different distro handles it. I expect something like that to happen, anyway. Apparently removing the FIPS_mode_set(0) call is enough to get it to build and work. The only reason this function was called was cleaning up OpenSSL after use, to reduce memory leaks, but I honestly doubt this call in particular is necessary. However, there's a metric ton of deprecation warnings regarding the low-level digest functions (see https://github.com/openssl/openssl/blob/master/doc/man7/migration_guide.pod#deprecated-low-level-digest-functions). I'm not sure how to solve those, as they're wrapped in C++ templates and similar confusing constructs. Is it fine to leave deprecated functions in here, or should I wait for upstream to solve this before marking this package "openssl-3.0.0 compatible"? @toralf: net-im/telegram-desktop-3.1.0 now has a patch that at least allows it to build with openssl-3.0.0 now, even though it has a crapload of deprecation warnings. Is that enough to unblock https://bugs.gentoo.org/797325 ? (In reply to Esteve Varela Colominas from comment #10) > @toralf: > net-im/telegram-desktop-3.1.0 now has a patch that at least allows it to > build with openssl-3.0.0 now, even though it has a crapload of deprecation > warnings. > Is that enough to unblock https://bugs.gentoo.org/797325 ? or remove the ~3.0.1 in favour of ~3.1.0 and close this bug ? If I were to remove the current ~arch version whenever a new ~arch version is released I would never get to stabilize anything... net-im/telegram-desktop-3.0.1-r1 now contains the openssl3 patch as well (it's been tested), and it has been marked stable. I'll close this issue when I remove 2.9.3-r1 from the tree, unless it's ok to close now. The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=341116ec481cbc56deac5eb03162088068a047ba commit 341116ec481cbc56deac5eb03162088068a047ba Author: Esteve Varela Colominas <esteve.varela@gmail.com> AuthorDate: 2021-10-31 22:11:18 +0000 Commit: Georgy Yakovlev <gyakovlev@gentoo.org> CommitDate: 2021-11-01 20:10:06 +0000 net-im/telegram-desktop: Bump to 3.1.11, drop old Closes: https://bugs.gentoo.org/813408 Closes: https://github.com/gentoo/gentoo/pull/22776 Signed-off-by: Esteve Varela Colominas <esteve.varela@gmail.com> Signed-off-by: Georgy Yakovlev <gyakovlev@gentoo.org> net-im/telegram-desktop/Manifest | 2 +- ....3-r1.ebuild => telegram-desktop-3.1.11.ebuild} | 26 +++++++++++----------- 2 files changed, 14 insertions(+), 14 deletions(-) |