On Mon, 22 Aug 2022 16:27:20 +0200, Ben Greiner wrote:

Am 22.08.22 um 16:16 schrieb Takashi Iwai:

...

On Mon, 22 Aug 2022 15:44:34 +0200, Ben Greiner wrote:

...

Am 22.08.22 um 13:11 schrieb Takashi Iwai:

...

- openSUSE_Leap_15.3 seems already having some hanging users, and the coexistence with 15.3 seems more or less admitted. We may leave this for now until EOL of Leap 15.3. You could set up the duplicate name as non-building and inheriting from a path to the other one in order to save some computing resource usage. Something like:

<project name="multimedia:libs">   ...   <build>     <disable repository="openSUSE_Leap_15.3"/>   </build>   <repository name="15.3">     <path project="openSUSE:Leap:15.3:Update" repository="standard"/>     <arch>x86_64</arch>     <arch>i586</arch>     <arch>aarch64</arch>   </repository>   <repository name="openSUSE_Leap_15.3">     <path project="multimedia:libs" repository="15.3"/>     <arch>x86_64</arch>     <arch>i586</arch>     <arch>aarch64</arch>   </repository> </project>

This will only produce duplicate builds on newly branched projects, which branch both repositories. It's an interesting idea. But, with this setup, openSUSE_Leap_15.3 repo will keep only the old built binaries?

Yes, you will have to wipe the old binaries from openSUSE_Leap_15.3. There is a button in the web-interface or do `osc wipebinaries -r openSUSE_Leap_15.3 multimedia:libs`. Then any binary requested from a repository which has  '<path project="multimedia:libs" repository="openSUSE_Leap_15.3"/>'  will get its packages from whatever it can find up the chain starting at multimedia:libs/15.3 through openSUSE:Leap:15.3:Update/standard and continuing to whatever is defined as link or path there (Leap/Backports/SLE with :Checks/:Update/:GA standard/pool).

I understand it'll work for building a package based on this project, but what's about users who are using this project and openSUSE_Leap_15.3 repo already? I'm not sure whether this will keep working. I quickly tested a similar set up with my home project, and this didn't seem working. Once after the wipe, openSUSE_Leap_15.3 becomes empty, and zypper doesn't take the packages from 15.3. thanks, Takashi