I use SDB:KDE repositories - openSUSE Wiki . From
OK. To answer your questions. Yes, you have to replace the currently installed version with version from the repository. No, zypper does not try to switch to the different repository. Both versions come from the same project KDE:Unstable:Extra and...
i+ | libKasten4 | package | 0.26.60git396~eb176bb-ku.134.1 | x86_64 | (System Packages)
v | libKasten4 | package | 0.26.60git377~e9f5faa-ku.143.1 | x86_64 | KDE:Unstable:Extra
OK. To answer your questions. Yes, you have to replace the currently installed version with version from the repository. No, zypper does not try to switch to the different repository. Both versions come from the same project KDE:Unstable:Extra and even though the installed version looks higher, it is in effect lower. So, there is no downgrade.
This is the packaging bug. The number after the git string is the count of commits since the most recent tag in upstream source repository. But the package version format hides this tag making comparison useless. To illustrate:
andrei@leap154:~/src/okteta> git describe --tags eb176bb
v0.26.12-396-geb176bbd6
andrei@leap154:~/src/okteta> git describe --tags e9f5faa
v0.26.13-377-ge9f5faa1f
andrei@leap154:~/src/okteta>
Here you see the numbers 396 and 377. Yes, the number 396 is higher, but it counts commits since the (version) tag v0.26.12 which itself is lower than v0.26.13. Commits count is reset after the new tag, so comparison of unqualified 396 and 377 makes no sense. The version v0.26.12-396-geb176bbd6 is lower than v0.26.13-377-ge9f5faa1f when compared in full.
Either this package needs to use the real version string instead of hardcoded 0.26.60 or it has to count commits since some fixed point which stays the same every time this package is rebuilt.
Does anyone object to me reporting this at Log in to KDE Bugtracking System ?
Duha
August 24, 2023, 6:12pm
2
Are you sure this is a kde issue and not a opensuse packageing issue?
If yes, why not ask the opensuse devs to open a bug report
Did you read the explanation? It seems to me like it must be, since the packages are served by KDE, to my knowledge.
The program is provided by KDE, but the packages are provided by the distro package maintainers.
The way to go from here is to report a bug in the openSUSE bugzilla using what ardj mentioned. The place I used to report those was under the Product openSUSE Tumbleweed, Component KDE Workspace (Plasma), with the bug report prefixed as [Krypton].
1 Like
Herzenschein:
The way to go from here is to report a bug in the openSUSE bugzilla using what ardj mentioned. The place I used to report those was under the Product openSUSE Tumbleweed, Component KDE Workspace (Plasma), with the bug report prefixed as [Krypton].
Any idea, @Herzenschein , of which option in Log in to Bugzilla to report this to? Usually, I choose Log in to Bugzilla , but this doesn’t seem like it should go there since it’s a separate repository.
As I said, openSUSE Tumbleweed.
There is no separate product for Argon or Krypton. Since you’re using Krypton, and it can only be used in Tumbleweed, you can report it for Tumbleweed just fine. If you search for issues containing the keyword “krypton” you’ll find the majority being reported to the openSUSE Tumbleweed product.
1 Like
I’ll do so. Thanks. @Herzenschein , could you direct me to somewhere that explains what Krypton is? I’d not heard of it until KDE:Unstable OpenSUSE TW repository needs to version packages differently - #4 by Herzenschein