Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1902449 - [s390x] qt5-qtbase-devel/vulkan-loader cannot be installed due to missing mesa-vulkan-drivers
Summary: [s390x] qt5-qtbase-devel/vulkan-loader cannot be installed due to missing mes...
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: qt5-qtbase
Version: rawhide
Hardware: s390x
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1902448
Blocks: 1900623
TreeView+ depends on / blocked
 
Reported: 2020-11-29 04:44 UTC by Mamoru TASAKA
Modified: 2020-12-16 17:19 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-29 07:15:42 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Mamoru TASAKA 2020-11-29 04:44:03 UTC 
Description of problem:
This scratch build:
https://koji.fedoraproject.org/koji/taskinfo?taskID=56388820
fails only on s390x.

Looking at:
https://kojipkgs.fedoraproject.org//work/tasks/8833/56388833/root.log

DEBUG util.py:634:   Problem 6: package qt5-qtbase-devel-5.15.2-3.fc34.s390x requires pkgconfig(vulkan), but none of the providers can be installed
DEBUG util.py:634:    - package qtsingleapplication-qt5-devel-2.6.1-40.fc33.s390x requires qt5-qtbase-devel, but none of the providers can be installed
DEBUG util.py:634:    - package vulkan-loader-devel-1.2.154.1-1.fc34.s390x requires vulkan-loader(s390-64) = 1.2.154.1-1.fc34, but none of the providers can be installed
DEBUG util.py:634:    - package vulkan-loader-devel-1.2.154.1-1.fc34.s390x requires libvulkan.so.1()(64bit), but none of the providers can be installed
DEBUG util.py:634:    - conflicting requests
DEBUG util.py:634:    - nothing provides mesa-vulkan-drivers(s390-64) needed by vulkan-loader-1.2.154.1-1.fc34.s390x

Currently mesa-20.2.3-2.fc34 does not build mesa-vulkan-drivers on s390x, so vulkan-loader dependency cannot be satisfied, which makes qt5-qtbase-devel uninstallable.

https://koji.fedoraproject.org/koji/buildinfo?buildID=1646494

Version-Release number of selected component (if applicable):
vulkan-loader-devel-1.2.154.1-1.fc34.s390x
mesa-20.2.3-2.fc34
qt5-qtbase-devel-5.15.2-3.fc34.s390x
Comment 1 Rex Dieter 2020-11-29 07:06:57 UTC 
There's something more seriously broken with s390 rawhide buildroots, I don't think this is specific to qt5-qtbase
Comment 2 Rex Dieter 2020-11-29 07:09:24 UTC 
Triaging this to vulkan-loader for now, that is what really is uninstallable.
Comment 3 Rex Dieter 2020-11-29 07:10:01 UTC 
nevermind, looks like the vulkan-loader bug was already filed,
bug #1902448
moving back
Comment 4 Rex Dieter 2020-11-29 07:15:42 UTC 
drop vulkan support on s390x :
https://src.fedoraproject.org/rpms/qt5-qtbase/c/c3b686ca071ae149d5d2ecd4d7f383eca793b03e?branch=master
Comment 5 Marek Blaha 2020-12-14 12:00:15 UTC 
Any chance to get this backported also to f33?
Comment 6 Rex Dieter 2020-12-14 23:29:15 UTC 
This problem was only ever present in rawhide, f33 was not affected.
Comment 7 Alexander Ploumistos 2020-12-15 20:13:50 UTC 
(In reply to Rex Dieter from comment #6)
> This problem was only ever present in rawhide, f33 was not affected.

Then what's wrong in f33?
I've had the same error when building molsketch and so did Vitaly:

https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/YKK2POVXKMTHTJF2NVF5EFYWKEATDHPX/  (last couple of messages)
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/V5EMTS5D4YARVX5HWX2LUQLYPEPIJXH4/
Comment 8 Rex Dieter 2020-12-16 17:19:19 UTC 
https://bodhi.fedoraproject.org/updates/FEDORA-2020-9cbc7b3d68

should fix it by the looks of it
Note You need to log in before you can comment on or make changes to this bug.