Leap-release package wants to downgrade after fresh install?

English Install/Boot/Login
1

Hello, I’m very new to OpenSUSE and zypper, so please forgive me if i’m missing something obvious.

I’ve just installed Leap 16.0 and the package Leap-release wants to update from the install was version 16.0-lp160.281.1 to the version 16.0+leap-lp160.263.1.

To me this looks like it will be a downgrade. See screenshots for evidence. As you can see in the last picture from the cdn, the one I have installed was from the beginning of June, while the one it wants to install was from Dec. 2025.

My questions are:

  1. Should i let this “upgrade” occur? What is inside the Leap-release package?
  2. Is this a bug that I should report elsewhere?

zypper list-updates output:

S  | Repository      | Name         | Current Version  | Available Version     | Arch
---+-----------------+--------------+------------------+-----------------------+-------
v  | repo-oss (16.0) | Leap-release | 16.0-lp160.281.1 | 16.0+leap-lp160.263.1 | x86_64

zypper search --details Leap-release output:

S  | Name             | Type    | Version               | Arch   | Repository
---+------------------+---------+-----------------------+--------+----------------
v  | Leap-release     | package | 16.0+leap-lp160.263.1 | x86_64 | repo-oss (16.0)
i+ | Leap-release     | package | 16.0-lp160.281.1      | x86_64 | repo-oss (16.0)
   | Leap-release-ftp | package | 16.0+leap-lp160.263.1 | x86_64 | repo-oss (16.0)
   | Leap-release-ftp | package | 16.0-lp160.281.1      | x86_64 | repo-oss (16.0)

Screenshot of cdn.opensuse.org/distribution/leap/16.0/repos/oss/x86_64/

image
image2314×580 106 KB

2

Hi, welcome

As you may notice the package names are not the same:
16.0-lp160.281.1
16.0+leap-lp160.263.1
My educated guess is that the old one is obsoleted by the newer one, which covers both Leap 16.0 and the upcoming Leap 16.1 . With annual releasing , and each point release having 24 months of support, there will be an overlap between 2 point releases. Covering that in a single packages makes sense IMHO.

3

Hi
Weak removers and product info…

* Tue May 26 2026 Max Lin <mlin@suse.com>
- Removed %%sle_version from the macros.lep (bsc#1238724)
- Added %%is_opensuse to the macros.lep

One wonders if this was pushed since the Leap respin iso was released…

You can download and check the src rpms…
https://download.opensuse.org/source/distribution/leap/16.0/repo/oss/src/

4

Thank you for your relpy!

I did notice the difference in the version names, where the old one (263) includes +leap while the new one (281) omits it.

Clearly the +leap is making zypper think the older package is a higher release version than the new one. At this point I’m thinking of disallowing my system from “updating” to the older version.

5

I would not do that. It is 2 packages, 1 replacing the other. In this case the version doesn’t mean that much, it contains no software.

6

16.0+leap-lp160.263.1 is built from https://src.opensuse.org/openSUSE/Leap/src/branch/leap-16.0/000release-packages

16.0-lp160.281.1 is from https://build.opensuse.org/package/revisions/openSUSE:Leap:16.0:Products/000release-packages
Click ‘Revisions’, there is the comment

cheery-picks fixes, prepare for image respin

Maybe it’s only a one-off package for image building, maintenance happens on the one with +leap suffix?

1 Like