#8827 Unretire opentegra
Opened 2 months ago by kwizart. Modified 2 months ago

  • Name of the package? xorg-x11-drv-opentegra

  • FAS username of the new maintainer? kwizart

  • Branches that you need it to be unretired for? all
    but f31+

  • Package re-review BZ URL? None

  • Any extra information?
    As mentioned at https://bugzilla.redhat.com/show_bug.cgi?id=1737007

Still assigned to the task. Having the package blocked from f31 is appropriate, but opentegra DDX is still relevant for the long run.
The situation will evolve once the Tegra kernel DRM API will be reworked (not before 5.5).
Right now, the current source of opentegra relies on a downstream libdrm fork (but it can work with an upstream kernel)
Having the libdrm fork bundled can be a workaround.


@kwizart I am not really getting what you want here:

Branches that you need it to be unretired for? all
but f31+

Its retired in F32/master, unretired in F30, so you need a branch for just F31?

Yep, I don't get what I meant either.

Basically I want it to be un-retired for all branches.
So I need to have a f31 branch created also.

I expect I meant that the package can be removed from repositories if not done already (so for f31+). I will re-introduce the package post f31 GA.

Thx

Yep, I don't get what I meant either.
Basically I want it to be un-retired for all branches.
So I need to have a f31 branch created also.
I expect I meant that the package can be removed from repositories if not done already (so for f31+). I will re-introduce the package post f31 GA.
Thx

@kwizart Still not getting it, you said you want it to be unretired for all branches and then you are saying you will re-introduce it post f31 GA?

For creating f31 branch, you need to use fedpkg request-branch to request the f31 branch.

And coming to f32/master branch, do you want it to be unretired now or post GA?

Login to comment on this ticket.

Metadata