#113 mesa-vdpau-drivers dropped out of multilib for unknown reason
Closed: Fixed 7 years ago Opened 7 years ago by kparal.

mesa-vdpau-drivers.i686 was present in x86_64 repos in Fedora 24, but now in Fedora 25 it's not there. @ajax, the maintainer, doesn't know of any changes in the package that should cause this. So, this is probably a problem in pungi?


@kparal is it just for Fedora 25 or rawhide as well?

@kparal mesa-vdpau-drivers is added to rawhide and f26 multilib but I dont think its needs to be added to f25 since we are not making any composes out of it.

Metadata Update from @mohanboddu:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

7 years ago

What about F25 updates repo? Doesn't pungi configuration decide what goes into updates? Or is that handled by a different tool?

updates repos are made by mash.

And my experience is that you don't really want to make a new release of mash just to fix multilib definitions. So, do we just ignore this until somebody complains too much, and hopefully make mash re-use pungi multilib configuration in the future (or replace mash completely with pungi even for updates)? Or better ideas?

@kparal Currently there are plans on making mash use python-multilib and also replace mash with koji signed repos, we are looking at both the options.

What's the process for getting a package multilibbed in stable releases at the moment? There is a need for libcurl (already multilibbed) to pull in nss-pem (not currently multilibbed), to resolve https://bugzilla.redhat.com/show_bug.cgi?id=1428550

In Rawhide, addition of an arch-specific dependency on nss-pem was enough to get nss-pem.i686 into the x86_64 repo via dependencies of libcurl-devel.

However, the same change made in F-26 currently results in a missing dependency (https://bugzilla.redhat.com/show_bug.cgi?id=1431347), presumably due to the different tooling used to compose the updates repos. What's the correct way to address the multilib issue there? I can't find anything on the wiki about that.

Login to comment on this ticket.

Metadata