fedora-workstation

#39 Add Intel VA-API backend as 3rd party repository
Closed Opened by kwizart.

Closed
Reopen Issue

Name of application: Intel VA-API Backend
Description of Application:

Type of repository: RPM

URL for repository:
metalink=https://mirrors.rpmfusion.org/metalink?repo=free-fedora-drivers-$releasever&arch=$basearch
There is no appdata file contributed for this package so the repository doesn't yet provide metadata. (also there is a typo for the repository metalink url under fixing the right url can take time to appear)
Primary mirror is located here (don't use this url, but the metalink above)
http://download1.rpmfusion.org/free/fedora/drivers/$releasever/$arch/

The keys are already provided from the distribution-gpg-keys as (of all arches).
/usr/share/distribution-gpg-keys/rpmfusion/RPM-GPG-KEY-rpmfusion-free-fedora-$releasever

License for application submitted: MIT and EPL (FLOSS)

Is packager application owner or developer? No, this is a external repo hosted by a community project.

If not owner or developer do you have permission to package this either through license terms or directly from owner? Yes, Intel are explicitly allowing redistribution as part of the license.

Is there a group of people maintaining this repository? Yes, this repository is maintained by the RPM Fusion community project.
https://lists.rpmfusion.org/archives/list/rpmfusion-developers@lists.rpmfusion.org/

If you are a single person behind repository what are you contingency plan in case you are unavailable or lose interest or have an accident? RPM Fusion is a 10 year old project that already has switched once of primary coordinator. Few people have admins rights to the project and could take-over.
The project also rely on community resources https://rpmfusion.org/Contribute.

How do we contact you in case there are problems? https://bugzilla.rpmfusion.org/enter_bug.cgi?product=Fedora and choose libva-intel-driver as component.

For the infra side: root@rpmfusion.org

As a side note, (newer) VA-API is also a Fedora 28 feature:
https://fedoraproject.org/wiki/Changes/VA-API_1.0.0

The guidance we have from legal is that we should add repositories for individual 3rd party components. While there's only the va-api driver here atm, the name makes it sound like this will be a place where more stuff will spontaneously appear over time...

Hi @kwizart, since this software is FLOSS, can you provide some background for why it is currently in RPMFusion? The third-party repository process is not a way to bypass legal approval. If there are legal problems blocking its inclusion in Fedora, then unfortunately we cannot add it via a third-party repo either, and this ticket should be closed.
Edited by catanzaro

The guidance we have from legal is that we should add repositories for individual 3rd party components. While there's only the va-api driver here atm, the name makes it sound like this will be a place where more stuff will spontaneously appear over time...

Let's proceed on the assumption that it would be split into its own repository. Hopefully @kwizart will be OK with that requirement.

FYI, it was rejected several time already, here is the last attempt after the upstream libva redesign:
https://bugzilla.redhat.com/show_bug.cgi?id=770371#c8
Nothing has change in the current code base that worth to re-submit.

Of course the idea of RPM Fusion is to only keep content that is not allowed in fedora reducing the risk of conflict. But then what is the situation several third party repository can provide the same content ? Each will have a different level of patching and that will lead to conflicts.

This was the situation experienced before the RPM Fusion creation 10 years ago. And there is no way around to fix that situation than to have a team of package maintainers coordinate within the same project.

On a side note, I've contributed an appdata file for the package
https://pkgs.rpmfusion.org/cgit/free/libva-intel-driver.git/commit/?id=a99ef55511459d99fb518e4adf46e07092b91048
So the metadata should comes in a few.

I would also mention that if you want to only keep one package in this repository, fine with me.

Looking over that bug, it seems extremely unlikely that we would be able to get legal approval for this, so I'm going to close this issue.

Metadata Update from @catanzaro:
- Issue status updated to: Closed (was: Open)

This issue has been migrated to Fedora Forge:
https://forge.fedoraproject.org/workstation/tickets/issues/39

Please continue any further discussion there.
Metadata
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.