Unlocking ibus makes no difference so it’s not the cause. Also zypper dup does nothing
**white-angel:~ #** zypper dup
Loading repository data...
Reading installed packages...
Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more informat
ion about this command.
Computing distribution upgrade...
The following item is locked and will not be changed by any action:
Available:
ibus
Nothing to do.
When you want to tell us what your repos are, we need the URLs, not only names and aliases, because these are local to your system (and can be anything).
Hm, does not look bad to me. The only thing that wonders me is that the Packman URL has no mentioning of 15.3.
BTW, next time you show command and output here, precede the command with LANG=C. That will make it better understandable in the English section here. Example:
I’m pretty sure that’s a mistake (but not your mistake). Perhaps a bug report is warranted. Apart from that, I would not worry about it.
Running “zypper -v up” (for verbose output), I get (among other things):
The following product update will NOT be installed:
openSUSE Leap 15.3 15.3-2
Yesterday, they released an updated install iso for Leap 15.3. As a test, I downloaded that iso, and did a test install (to a virtual machine).
The newly installed system describes itself as 15.3-2. I think that’s what your message is coming from.
On the newly installed system, I tried running “Yast online update”. And that gave me some conflicts.
Problem: the installed product:Leap-15.3-2.x86_64 requires 'product(Leap) = 15.3-2', but this requirement cannot be provided
Solution 1: Following actions will be done:
do not install patch:openSUSE-2021-820-1.noarch
do not install patch:openSUSE-2021-863-1.noarch
Solution 2: downgrade of product:Leap-15.3-2.x86_64 to product:Leap-15.3-1.x86_64
Solution 3: break product:Leap-15.3-2.x86_64 by ignoring some of its dependencies
I’m pretty sure that is complaining about the same problem, but from the other direction.
Somebody goofed, but it doesn’t seem very important.
Good explanation. But as that remastering of Leap will take place on a regular base in the future, I think it is better to make a bug report. Else it will stay as it is and we will have questions abut in the forums in the future.
zypper -v doesn’t show anything interesting… however, running install for the product shows the following:
# zypper in product:Leap-15.3-2.x86_64
Loading repository data...
Reading installed packages...
Resolving package dependencies...
The following product is going to be upgraded:
openSUSE Leap 15.3 15.3-1 -> 15.3-2
The following package is going to be downgraded:
openSUSE-release
1 package to downgrade.
Overall download size: 598.2 KiB. Already cached: 0 B. After the operation, additional 626.0 B will be used.
**Continue? [y/n/v/...? shows all options] (y): **
What’s wrong with openSUSE-release?
[FONT=monospace]# zypper search -iv openSUSE-release
Loading repository data...
Reading installed packages...
S | Name | Type | Version | Arch | ...
---+-----------------------------------+---------+------------------+--------+-...
i+ | openSUSE-release | package | 15.3-lp153.149.1 | x86_64 | ...
i | openSUSE-release-appliance-custom | package | 15.3-lp153.149.1 | x86_64 | ...
The system is pretty new so I wonder how I got the distribution broken so fast
Product update actually updates openSUSE-release package. The openSUSE-release in main repository defines product version 15.3-2, while openSUSE-release packages in update repositories define product version 15.3-1. So zypper sees “newer” product version, but because openSUSE-release package version in main repository is lower, it will not install it.
bor@leap15:~> zypper se -sx openSUSE-release
Loading repository data...
Reading installed packages...
S | Name | Type | Version | Arch | Repository
---+------------------+------------+------------------+--------+-----------------------
i+ | openSUSE-release | package | 15.3-lp153.149.1 | x86_64 | Main Update Repository
v | openSUSE-release | package | 15.3-lp153.146.1 | x86_64 | Main Update Repository
v | openSUSE-release | package | 15.3-lp153.143.2 | x86_64 | Main Update Repository
v | openSUSE-release | package | 15.3-lp153.143.1 | x86_64 | Main Update Repository
v | openSUSE-release | package | 15.3-lp153.16.2 | x86_64 | Main Repository (OSS)
bor@leap15:~> rpm -q --provides openSUSE-release | grep 'product(Leap)'
product(Leap) = **15.3-1**
bor@leap15:~>
And if you look at package in Main Repository (OSS), it provides product(Leap) = 15.3-2
bor@leap15:~> sudo zypper --no-refresh -vvv up
...
The following product update will NOT be installed:
openSUSE Leap 15.3 **15.3-2 ** x86_64 **Main Repository (OSS) ** openSUSE
Nothing to do.
bor@leap15:~>
