Bug 1923414 - libva-v4l2-request: FTBFS in Fedora rawhide/f34
Summary: libva-v4l2-request: FTBFS in Fedora rawhide/f34
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: libva-v4l2-request
Version: 34
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Nicolas Chauvet (kwizart)
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1923415 1987668 (view as bug list)
Depends On:
Blocks: ARMTracker F34FTBFS F35FTBFS F36FTBFS
TreeView+ depends on / blocked
 
Reported: 2021-02-01 16:48 UTC by Fedora Release Engineering
Modified: 2022-01-03 16:14 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-01-03 16:14:10 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github bootlin libva-v4l2-request issues 35 0 None open Fails to build against kernel 5.11.x 2021-05-21 07:57:41 UTC

Description Fedora Release Engineering 2021-02-01 16:48:32 UTC
libva-v4l2-request failed to build from source in Fedora rawhide/f34

https://koji.fedoraproject.org/koji/taskinfo?taskID=60909922


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_34_Mass_Rebuild
Please fix libva-v4l2-request at your earliest convenience and set the bug's status to
ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks,
libva-v4l2-request will be orphaned. Before branching of Fedora 35,
libva-v4l2-request will be retired, if it still fails to build.

For more details on the FTBFS policy, please visit:
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/

Comment 1 Ben Cotton 2021-02-09 15:50:37 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle.
Changing version to 34.

Comment 2 Fedora Release Engineering 2021-02-14 04:24:37 UTC
Dear Maintainer,

your package has an open Fails To Build From Source bug for Fedora 34.
Action is required from you.

If you can fix your package to build, perform a build in koji, and either create
an update in bodhi, or close this bug without creating an update, if updating is
not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to
acknowledge this. If you have already fixed this issue, please close this Bugzilla report.

Following the policy for such packages [2], your package will be orphaned if
this bug remains in NEW state more than 8 weeks (not sooner than 2021-03-29).

A week before the mass branching of Fedora 35 according to the schedule [3],
any packages not successfully rebuilt at least on Fedora 33 will be
retired regardless of the status of this bug.

[1] https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/
[2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
[3] https://fedorapeople.org/groups/schedule/f-35/f-35-key-tasks.html

Comment 3 Miro Hrončok 2021-02-16 15:13:17 UTC
*** Bug 1923415 has been marked as a duplicate of this bug. ***

Comment 4 Jeff Law 2021-02-25 22:05:37 UTC
FWIW, I don't think this is a GCC issue.  I can build the F34 .src.rpm against a F33 buildroot *and* an F33 buildroot with gcc-11.  That would tend to point to a problem with one of the other build dependencies.

Comment 5 Nicolas Chauvet (kwizart) 2021-03-01 08:32:33 UTC
The failure is related to updated kernel-headers.

Seems like there is a need for time to adapt to the new uAPI exposed by v4l2-request recently upstreamed.

Comment 6 Fedora Release Engineering 2021-03-07 04:23:18 UTC
Dear Maintainer,

your package has an open Fails To Build From Source bug for Fedora 34.
Action is required from you.

If you can fix your package to build, perform a build in koji, and either create
an update in bodhi, or close this bug without creating an update, if updating is
not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to
acknowledge this. If you have already fixed this issue, please close this Bugzilla report.

Following the policy for such packages [2], your package will be orphaned if
this bug remains in NEW state more than 8 weeks (not sooner than 2021-03-29).

A week before the mass branching of Fedora 35 according to the schedule [3],
any packages not successfully rebuilt at least on Fedora 33 will be
retired regardless of the status of this bug.

[1] https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/
[2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
[3] https://fedorapeople.org/groups/schedule/f-35/f-35-key-tasks.html

Comment 7 Nicolas Chauvet (kwizart) 2021-03-12 12:31:16 UTC
I will take care of this by f35...

Comment 8 Dominik 'Rathann' Mierzejewski 2021-05-21 07:55:54 UTC
I've just found out this is already packaged, great! I'll see what I can do to help here, I have a Pinebook Pro that would benefit from this driver working correctly. Can you add me to co-maintainers (FAS: rathann)?

Comment 9 Nicolas Chauvet (kwizart) 2021-08-18 06:43:08 UTC
*** Bug 1987668 has been marked as a duplicate of this bug. ***

Comment 10 Nicolas Chauvet (kwizart) 2021-08-18 06:48:42 UTC
Seems like there is a solution been worked on , but still WIP:
https://github.com/bootlin/libva-v4l2-request/pull/38

I will have a look in the next days.

Comment 11 Nicolas Chauvet (kwizart) 2022-01-03 16:14:10 UTC
Fixed in libva-v4l2-request for f34+
See also:
https://bodhi.fedoraproject.org/updates/FEDORA-2022-861d11ac34
https://bodhi.fedoraproject.org/updates/FEDORA-2022-0c98e2fe22


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