Re: Disappearing and re-appearing i686 packages in the x86_64 compose

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, May 07, 2021 at 02:50:29PM +0200, Florian Weimer wrote:
> Historically, we had an issue with i686 packages appearing and
> disappearing from the x86_64 compose.  Particularly problematic is the
> case when packages are in the GA repo, but not in the updates repo.
> 
>   <https://pagure.io/releng/issue/8337>
> 
> Has this issue been fixed?

No, I don't think it will ever be "fixed". 

The base repo compose has almost 100% of packages, so it can do the
multilib dance (does it have a -devel package, does it have a -libs
package, etc) and then pull in any deps for those things. 

The updates compose only has those packages that are in updates. 
It can't pull in dependencies of things that don't have updates. 

Ie, say you have a package foo, and in the base x86_64 repo, bar.i686
pulls in foo.i686, so those are there. In updates until there is an
update for 'bar' pushed out, there's nothing that would pull foo.i686
into the repo, so it's not there. 

> I implemented a workaround in glibc (which encountered frequent update
> failures due to the infrastructure issue).  However, that workaround has
> problems on its own, so I want to revert it.

We have in update pungi config a (IMHO poorly named)
"multilib_whitelist" variable. We can add packages to this and pungi
will pull them in, no matter if something depends on them or not.

We just added pipewire.i686 to the list, so you could look and confirm
it's doing what you would like glibc.i686 to be doing? 

In the pipewire.i686 case, mutter.i686 is pulled into the x86_64 base repo
(gnome-tweaks requires it), but until there is a mutter update, f34
didn't have pipewire.i686 as nothing pulled it in. After adding to the
pungi config it now is there. 

kevin

Attachment: signature.asc
Description: PGP signature

_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux