Pavel Raiskup
Pavel Raiskup
> To anticipate any future builds I suggest using: > @spot/texlive.*/.*/texlive* There are no powerful ppc64le builders, though. No builder would be found for such a task, and that's why...
The same happens with vim v9.1.906 on Fedora 41.
I think this issue is solvable via the yum_cache plugin; instead of sharing one directory across multiple mock builds we want to create a tmpfs mountpoint per each mock call....
Can you re-try? It seems this problem no longer exists (I at least tried to initialize a 15.5 chroot with mock locally, and it worked fine).
Seems resolved, closing.
The thing is that I'm not entirely sure what to do, after the discussion in https://github.com/rpm-software-management/mock/issues/1427 and related. While it is easy to map epel10.0 to Copr's `epel-10-*` chroots now,...
The `latest_*` fields are very confusing in my opinion, shall we just hide those by default? Otherwise @nikromen is right, you need to use the corresponding `--with-latest*` option to have...
We are afraid that our production servers might get affected soon (we should at least check if this is a container-only thing, and perhaps freeze the version if python3-deamon is...
Nice, what an attractive topic! > The project just reached another milestone (replacing subprocess calls with librpm / libdnf native calls). Mock moves towards the future shape where RPM/DNF is...
The infrastructure perspective. It is trivial to get a container to run Mock (well, hopefully we can get user-namespaced containers "everywhere" soon). It is relatively easy to get a short-lived...