Bug 2225331 - In brltty-6.6-1.fc39 , internal dependencies cannot be satisfied (python3-brlapi requires brlapi = 0.8.5, but brlapi is versioned 6.6)
Summary: In brltty-6.6-1.fc39 , internal dependencies cannot be satisfied (python3-brl...
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: brltty
Version: rawhide
Hardware: Unspecified
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Gwyn Ciesla
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: openqa
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-25 00:26 UTC by Adam Williamson
Modified: 2023-07-25 13:59 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-07-25 13:59:31 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Adam Williamson 2023-07-25 00:26:37 UTC
In the update to brltty 6.6, the versioning seems to have gone sideways. python3-brlapi still requires "brlapi%{?_isa} = %{api_version}-%{release}" - which works out to "brlapi(x86-64) = 0.8.5-1" - but brlapi's version is 6.6-1. So python3-brlapi is uninstallable.

The spec has pkg_version and api_version macros which were bumped to the right numbers (6.6 and 0.8.5 respectively), but a lot of subpackages had their Version changed to not use either macro, just be hardcoded as 6.6, including brlapi, which was previous "Version: %{api_version}".

This is breaking openQA tests of unrelated packages because it prevents system update from working.

Reproducible: Always

Steps to Reproduce:
1. Have python3-brlapi-0.8.4-19.fc39 installed
2. Try and update from a repo with the new brltty packages in it

Actual Results:  
The update process fails due to unresolvable dependency issues

Expected Results:  
The update should work

Comment 1 Adam Williamson 2023-07-25 01:43:21 UTC
Just for info, we have untagged the broken build from Rawhide - https://pagure.io/releng/issue/11566 - to unblock openQA tests and other processes for now.

Comment 2 Gwyn Ciesla 2023-07-25 13:59:31 UTC
Thank you, I've submitted a corrected build.


Note You need to log in before you can comment on or make changes to this bug.