Unfortunately, it is worse than this: Electrum FTI in F39. A newer
Electrum version would fix that, but F39 still has no new enough protobuf.
Is there any other solution here than saying packaging Electrum for
Fedora 39 is just not possible and remove the package in F39, then
reintroduce it in F40 (that is, if F40 finally gets a newer protobuf)?
--
Jonathan
Am 05.09.23 um 04:13 schrieb Ben Beasley:
Interested parties have been grappling with the problem of getting protobuf updated to v4 (22.x, 23.x, etc.), but the number of impacted packages is tremendous and there are not enough people with time to work on it, so progress has been slow. The following PR represents the state of that work[1]. Note that I’m not a co-maintainer of protobuf, but I’ve been collaborating on it because it is an important dependency for grpc, and I can’t update grpc any more (including for security fixes) until we have protobuf v4.
There was some sentiment that we should focus on working toward the protobuf v4 transition rather than on updating to newer 3.x branches during the F39 development cycle. However, I’m not sure if everyone really understood the full scope of that transition.
At this point, and given the amount of work remaining to make protobuf v4 possible, it’s probably a good idea for protobuf to be updated to a current v3 release, ideally 3.24.2. Given the number of potentially impacted packages, and the huge list of packages that need to be rebuilt (minor version updates break ABI), it’s probably too late to land that in F39, but it should be possible for F40, and it would be a good hedge against the possibility that the v4 work drags on for another release cycle (or more?!).
Input is welcome. Even more welcome is assistance working through unresolved protobuf v4 incompatibilities in dependent packages.
[1] https://src.fedoraproject.org/rpms/protobuf/pull-request/25
On Mon, Sep 4, 2023, at 2:39 PM, Jonathan Schleifer wrote:
Am 04.09.23 um 17:10 schrieb Miro Hrončok:
electrum js, orphan 0
weeks ago
Electrum isn't orphaned, but cannot be updated because protobuf is not
being updated. Newer versions require at least protobuf 3.20. I
contacted the protobuf maintainer on 2023-06-04 and never got a reply.
--
Jonathan
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
