Is there a table/description of which targets (15.2, 15.3, etc) are binary compatible? Something that would help one to select which things might work?

And I guess one would need multiple point release versions of a repository defined so as to able able to pick up the packages that are scattered across the various target repos, So on a, say, 15.5 install, you would need to add the repos for 15.1, 15.2, 15.3, 15.4, and 15.5 so that you can find the one that actually got built.

On Fri, Aug 25, 2023 at 9:17 AM Roger Oberholtzer <roger.oberholtzer@gmail.com> wrote:

I get this point. But when searching for packages for a version of leap like 15.4, these will not show up. If they are truly compatible, then perhaps this should be accounted for.

Also, if they are compatible, why does OBS even bother with a 15.x target and instead simply define only, say, 15. Then the wasted builds and all would be avoided and the users of these packages would perhaps better understand what they are for. Maybe that's a goal already defined? It doesn't mean that the point release targets can't also exist. But a non-point-release-common target would perhaps make intentions more clear. One could choose the 15 target to make it clear that your package is not specific to a point release.

JM2CW

On Wed, Aug 24, 2022 at 10:43 AM Fridrich Strba <fstrba@suse.com> wrote:
Hello,

On 24/08/2022 10:13, Roger Oberholtzer wrote:
> I quite often find that packages are enabled for only 15.2, or only
> Tumblwweed. But it is quite common that the packages are not enabled
> for all current openSUSE/SUSE releases.

For packages that are inherited in SLE15-SP4 from SLE15-SP2, I normally
don't enable other leap then 15.2, since they are supposed to work with
newer versions as they are. So, why to waste resources.

Cheers

F.

--
Roger Oberholtzer