Bug 2389712 - qutebrowser FTBFS in Fedora Rawhide and 43
Summary: qutebrowser FTBFS in Fedora Rawhide and 43
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: qutebrowser
Version: 43
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Timothée Floure
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F43FTBFS PYC3.14rc3 F44FTBFS, RAWHIDEFTBFS
TreeView+ depends on / blocked
 
Reported: 2025-08-20 09:39 UTC by Miro Hrončok
Modified: 2025-08-20 10:53 UTC (History)
2 users (show)

Fixed In Version: qutebrowser-3.5.1-3.fc44
Clone Of:
Environment:
Last Closed: 2025-08-20 10:53:16 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Miro Hrončok 2025-08-20 09:39:49 UTC
Due to reasons described in https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/XO5QGOXBWHFG7AOGDQBG23AQDS2MDTWI/ a rebuild of qutebrowser is needed in Fedora Rawhide (44) and Fedora 43.

However, qutebrowser fails to even build the SRPM in Koji:

https://koji.fedoraproject.org/koji/taskinfo?taskID=136127258
https://koji.fedoraproject.org/koji/taskinfo?taskID=136077327

Looks like the sources were not uploaded to the lookaside cache:

[qutebrowser (rawhide)]$ fedpkg sources
Downloading qutebrowser-3.5.1.tar.gz from https://src.fedoraproject.org/repo/pkgs
######################################################################## 100.0%
Remove downloaded invalid file /home/churchyard/rpmbuild/fedora-scm/qutebrowser/qutebrowser-3.5.1.tar.gz
Could not execute sources: Dist-git server returned status code 404


Please fix this and rebuild qutebrowser in Fedora 44 and 43, preferably before the Beta freeze (2025-08-26). Thanks

Comment 1 Ankur Sinha (FranciscoD) 2025-08-20 10:27:32 UTC
Thanks for the bug, weird that the sources aren't available. Looking into it now.

Comment 2 Ankur Sinha (FranciscoD) 2025-08-20 10:53:16 UTC
Fixed now, just had to upload the sources.

F43 build also kicked off.


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