On 1/24/24 20:34, Andreas Vetter wrote:

Hi, what is the correct path for Leap 16.0? I used <path project="security:Stunnel" repository="openSUSE_Leap_16.0"/> <arch>x86_64</arch>

This gave a unresolvable libopenssl-devel, because libopenssl and libopenssl- devel were at different versions: 3.1 vs 3.2. Is that to be expected? This problem is gone now, but maybe I have to use a different path.

My advice would be wait, last time I tried atleast not everything was ready yet. In https://build.opensuse.org/project/show/openSUSE:ALP:Experimental:Linarite:B... I am building against SUSE's ALP using <repository name="ALP"> <path project="SUSE:ALP:Source:Standard:Core:1.0:Build" repository="standard"/> <arch>x86_64</arch> </repository> Currently I am only building x11 and a couple of other random packages. At this point the SUSE Product that Leap 16 will be based off hasn't even started being created in SUSE's private build server. Once it is and is being published we will be able to start building Leap 16 on top of it until then in most cases we won't gain alot due to the number of dependencies that don't exist in ALP yet. The main reason I started looking at building X11 this early is that to do so we need to sync versions with some ALP packages such as Mesa etc for things where this isn't the case there probably isn't huge benefit in trying to build yet until SUSE adds more packages to ALP. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B