[packman] Packman Mesa broken

[Stefan Botter]

Hi Justin,

On Thu, 2024-11-21 at 19:24 -0500, Justin Wayland wrote:
> See subject line.
> 
> The 32bit versions of Mesa on Packman is on 24.2.6, while the 64bit version
> is on 24.2.7.  This is preventing people with Steam from updating.

Yesterday evening (around 2024-11-21T17:11:00+0100) the i586 scheduler
stopped, thus building of i586 packages could not proceed.

> I have two questions:
> 1. When will this be fixed?

I have restarted the schedulers, builds are on their way. Please give it
some hours for building and publishing to the mirrors.

> 2. From a thread on the forums, apparently this happens quite
> consistently.  Is there a way to stop this from happening in the future?

I am not really sure, that just the failing schedulers are the only
cause for the eventual inconsistencies, as there are other complaints
about Mesa packages arrived earlier Yesterday.
The stopping schedulers are a nuisance, they happen for a long time and
obviously just with our OBS instance, so I blame lack of available
memory. The log files do not show any evidence, and from monitoring I
just see sudden increase in memory allocation until OOM. PMBS and the
two workers run as a virtual guests on a host I mainly use for private
purposes, and I can only assign more RAM to PMBS if stop provide one of
the workers. So for the time being we have to live with occasional
dropouts of the schedulers, which btw are still not independently run
and monitored by systemd, which could act as a safety net for failing
services. I have yet to create monitoring with event handling for these
cases, but am continually short of time for automating these rather rare
occurrences.

If there are inconsistencies in dependencies to packages from openSUSE's
OBS, this is typically just a question of build and publishing time.
Only when packages from parent OBS are published, PMBS can pick up and
build our versions, and publish them. There is a time gap of probably 6
to 12 hours. This is not wanted, but by design of the separate build
system.
There is nothing we can do about that.

Greetings,

Stefan