system was not updated to KDE 5.20

Hi there,

I am running tumbleweed 20201012 from 2020-10-02 which I updated yesterday (Oct 19).

**kimera:/home/miguel #** tumbleweed target
20201012

Surprisingly, it did not updated to KDE 5.20.

**kimera:/home/miguel #** rpm -qa | grep -i plasma5
**plasma5**-addons-5.19.5-1.1.x86_64
**plasma5**-desktop-5.19.5-1.1.x86_64
**plasma5**-pa-5.19.5-1.1.x86_64
**plasma5**-pk-updates-0.3.2-10.3.x86_64
**plasma5**-addons-lang-5.19.5-1.1.noarch
**plasma5**-pa-lang-5.19.5-1.1.noarch
**plasma5**-applet-suse-prime-1.1-1.4.noarch
**plasma5**-theme-openSUSE-84.87~git20190606T185118~3d37a0c-23.3.noarch
**plasma5**-session-5.19.5-3.1.noarch
libKF5**Plasma5**-5.75.0-1.1.x86_64
**plasma5**-workspace-5.19.5-3.1.x86_64
**plasma5**-workspace-branding-openSUSE-84.87~git20190606T185118~3d37a0c-23.3.noarch
**plasma5**-desktop-emojier-5.19.5-1.1.x86_64
**plasma5**-thunderbolt-5.19.5-1.1.x86_64
**plasma5**-workspace-libs-5.19.5-3.1.x86_64
**plasma5**-pk-updates-lang-0.3.2-10.3.noarch
**plasma5**-integration-plugin-5.19.5-1.2.x86_64
**plasma5**-defaults-openSUSE-84.87~git20190606T185118~3d37a0c-23.3.noarch
**plasma5**-workspace-lang-5.19.5-3.1.noarch
**plasma5**-session-wayland-5.19.5-3.1.noarch
**plasma5**-integration-plugin-lang-5.19.5-1.2.noarch
**kimera:/home/miguel #**

It was a surprise since I’ve a second computer (a laptop) which did updated to KDE 5.20, both are running tumbleweed 20201012, both moved from 2020-10-02 to 20201012 on the same day, by the same method: twups to switch to 20201012 followed by the update provided by twups;

**kimera:/home/miguel #** zypper ref
Repository 'Google-Chrome' is up to date.
Repository 'NVIDIA' is up to date.
Repository 'Tumbleweed OSS' is up to date.
Repository 'Tumbleweed non-OSS' is up to date.
Repository 'Tumbleweed update' is up to date.
Repository 'google-chrome-beta' is up to date.
Repository 'Java-related packages (openSUSE_Tumbleweed)' is up to date.
Repository 'libdvdcss repository' is up to date.
Repository 'nvidia-tumbleweed' is up to date.
Repository 'packman' is up to date.
Repository 'snappy' is up to date.
Repository 'vscode' is up to date.
All repositories have been refreshed.
**kimera:/home/miguel #** zypper dist-upgrade
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 information about this command.
Computing distribution upgrade...

The following item is locked and will not be changed by any action:
 Available:
  Mesa-dri-nouveau

Nothing to do.

Addicionally, to be sure I am with the correct repositories, I remove the previous one and added it again using the URLS provided at https://en.opensuse.org/Package_repositories:

zypper ar http://download.opensuse.org/tumbleweed/repo/oss/ "Tumbleweed OSS"
zypper ar http://download.opensuse.org/tumbleweed/repo/non-oss/ "Tumbleweed non-OSS"
zypper ar http://download.opensuse.org/update/tumbleweed/ "Tumbleweed update"

So, the complete repository set is:

**kimera:/home/miguel #** zypper lr -Pu
#  | Alias                            | Name                                        | Enabled | GPG Check | Refresh | Priority | URI
---+----------------------------------+---------------------------------------------+---------+-----------+---------+----------+--------------------------------------------------------------------------------------
10 | packman                          | packman                                     | Yes     | (r ) Yes  | Yes     |    1     | http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Tumbleweed/
 1 | Google-Chrome                    | Google-Chrome                               | Yes     | (r ) Yes  | No      |   99     | http://dl.google.com/linux/chrome/rpm/stable/x86_64
 2 | NVIDIA                           | NVIDIA                                      | Yes     | (r ) Yes  | Yes     |   99     | https://download.nvidia.com/opensuse/leap/15.0
 3 | Tumbleweed OSS                   | Tumbleweed OSS                              | Yes     | (r ) Yes  | No      |   99     | http://download.opensuse.org/history/20201012/tumbleweed/repo/oss/
 4 | Tumbleweed non-OSS               | Tumbleweed non-OSS                          | Yes     | (r ) Yes  | No      |   99     | http://download.opensuse.org/history/20201012/tumbleweed/repo/non-oss/
 5 | Tumbleweed update                | Tumbleweed update                           | Yes     | (r ) Yes  | No      |   99     | http://download.opensuse.org/update/tumbleweed/
 6 | google-chrome-beta               | google-chrome-beta                          | Yes     | (r ) Yes  | Yes     |   99     | http://dl.google.com/linux/chrome/rpm/stable/x86_64
 7 | home_concyclic_java              | Java-related packages (openSUSE_Tumbleweed) | Yes     | (r ) Yes  | No      |   99     | https://download.opensuse.org/repositories/home:/concyclic:/java/openSUSE_Tumbleweed/
 8 | http-opensuse-guide.org-14eff5d5 | libdvdcss repository                        | Yes     | (r ) Yes  | Yes     |   99     | http://opensuse-guide.org/repo/openSUSE_Tumbleweed/
 9 | nvidia-tumbleweed                | nvidia-tumbleweed                           | Yes     | (r ) Yes  | No      |   99     | https://download.nvidia.com/opensuse/tumbleweed
11 | repo-debug                       | openSUSE-Tumbleweed-Debug                   | No      | ----      | ----    |   99     | http://download.opensuse.org/debug/tumbleweed/repo/oss/
12 | repo-source                      | openSUSE-Tumbleweed-Source                  | No      | ----      | ----    |   99     | http://download.opensuse.org/source/tumbleweed/repo/oss/
13 | snappy                           | snappy                                      | Yes     | (r ) Yes  | Yes     |   99     | https://download.opensuse.org/repositories/system:/snappy/openSUSE_Tumbleweed
14 | vscode                           | vscode                                      | Yes     | (r ) Yes  | No      |   99     | https://packages.microsoft.com/yumrepos/vscode

Why my system is not updating to KDE 5.20 as the laptop did ?

Kinfocenter says:

Operating System: openSUSE Tumbleweed 20201012
KDE Plasma Version: 5.19.5
KDE Frameworks Version: 5.75.0
Qt Version: 5.15.1
Kernel Version: 5.8.14-1-default
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz
Memory: 14.6 GiB of RAM
Graphics Processor: GeForce GTX 970/PCIe/SSE2

The other machine has the same versions for Framework, Qt and kernel, the only differ in Plasma version, 5.19.5 versus 5.20.0

What is wrong with my system ?
How can I force update KDE to 5.20 ?

Hi
Are the repositories exactly the same on both systems?

This needs fixing, repository number 2;


https://download.nvidia.com/opensuse/leap/15.0

Repository 7 also has system packages and there are links to old (Leap 15.1) packages…

If you updated yesterday, then you didn’t update to the latest Tumbleweed release… it’s at 20201014, so something is borked from those third party repositories…

You also want to remove the two “history” repositories: #3 & #4

… and I don’t see these (correct) ones you added:

http://download.opensuse.org/tumbleweed/repo/oss/ “Tumbleweed OSS”
http://download.opensuse.org/tumbleweed/repo/non-oss/ “Tumbleweed non-OSS”

The URI you specify for your repos allows the repository network’s Mirrorbrain to make your connection to the best performing actual repository and apparently you updated your machines in a fairly small window when KDE 5.20 is being pushed out to the repos, which means that some repos will be ready to serve the new files and others not quite.

If you run your upgrade again, I’d guess by now all your Tumbleweed machines should pull down KDE 5.20.

If your situation demands that all your machines update the same and not by fastest responding repo, you can re-configure the repos in every machine to point to the same repo (An address that points to a single server, not an address that allows Mirrorbrain to choose for you). Or, deploy your own mirror.

TSU

I think it was replaced by "tumbleweed-cli init " by “http://download.opensuse.org/history/20201012/tumbleweed/repo/oss/” .

Well… whilst you have OSS and Non-OSS coming from: http://download.opensuse.org/history/20201012/tumbleweed/* you wont update to a newer version… :wink:

How it needed to be fixed, exactly ?

So, should I remove “home_concyclic_java” ? And replace it by what ?

No, I don’t want to update to the latest Tumbleweed release. I want to stay with 20201012 (which have a rate of 99 according to https://review.tumbleweed.boombatower.com/) , so this is why I am using tumbleweed cli.

but, how come the other machine did ? As I told, both systems are using the same release 20201012 and same repos. One was updated to 5.20 and this one, not. Why ?
I repeat myself: I am using tumbleweed cli:


**kimera:/home/miguel #** tumbleweed status
latest   : 20201014
target   : 20201012
installed: 20201012
**kimera:/home/miguel #

**

You have only posted one repo list from one system. How do you think we can check if they are equal or not?

No, running zypper ref; zypper distro-upgrade right now, leads to “Nothing to do.” message.
And both points to the same repo. This is why the whole situation is so awkward !

Hi
Up to you, but seems that home repository is linked to old versions on the couple of packages I looked at, so if the likes of Plasma use ffmpeg then it could create an issue. Up to you to review what is packaged up from there.

Probably can’t offer anything more since not using Plasma or tumbleweed-cli.

Sure ! Sorry, I should have post it from begging just to better explain the case.
The laptop has hostname=tinybit and the desktop hostname is kimera as you can see by the bash prompt.


miguel  ~  sudo -s
[sudo] senha para root: 
tinybit:/home/miguel # tumbleweed status
latest   : 20201014
target   : 20201012
installed: 20201012
tinybit:/home/miguel # zypper lr -pU
#  | Alias                               | Name                                        | Enabled | GPG Check | Refresh | Priority | URI
---+-------------------------------------+---------------------------------------------+---------+-----------+---------+----------+--------------------------------------------------------------------------------------
 8 | openSUSE-20200422-0                 | openSUSE-20200422-0                         | No      | ----      | ----    |   99     | hd:/?device=/dev/disk/by-id/scsi-1SanDiskCruzer_Blade-part2
 1 | google-chrome-beta                  | google-chrome-beta                          | Yes     | (r ) Yes  | Yes     |   99     | http://dl.google.com/linux/chrome/rpm/stable/x86_64
10 | repo-debug                          | openSUSE-Tumbleweed-Debug                   | No      | ----      | ----    |   99     | http://download.opensuse.org/debug/tumbleweed/repo/oss/
11 | repo-non-oss                        | openSUSE-Tumbleweed-Non-Oss (20201012)      | Yes     | (r ) Yes  | Yes     |   99     | http://download.opensuse.org/history/20201012/tumbleweed/repo/non-oss/
12 | repo-oss                            | openSUSE-Tumbleweed-Oss (20201012)          | Yes     | (r ) Yes  | Yes     |   99     | http://download.opensuse.org/history/20201012/tumbleweed/repo/oss/
 5 | http-download.opensuse.org-908a4321 | devel:languages:go                          | Yes     | (r ) Yes  | Yes     |   99     | http://download.opensuse.org/repositories/devel:/languages:/go/openSUSE_Factory/
 6 | http-download.opensuse.org-bf9f87c0 | home:Dead_Mozay                             | Yes     | (r ) Yes  | Yes     |   99     | http://download.opensuse.org/repositories/home:/Dead_Mozay/openSUSE_Tumbleweed/
 3 | http-download.opensuse.org-047e2426 | openSUSE:Factory                            | Yes     | (r ) Yes  | Yes     |   99     | http://download.opensuse.org/repositories/openSUSE:/Factory/snapshot/
 7 | http-download.opensuse.org-c2015628 | openSUSE:Tumbleweed                         | Yes     | (r ) Yes  | Yes     |   99     | http://download.opensuse.org/repositories/openSUSE:/Tumbleweed/standard/
 4 | http-download.opensuse.org-521cdb75 | utilities                                   | Yes     | (r ) Yes  | Yes     |   99     | http://download.opensuse.org/repositories/utilities/openSUSE_Factory/
13 | repo-source                         | openSUSE-Tumbleweed-Source                  | No      | ----      | ----    |   99     | http://download.opensuse.org/source/tumbleweed/repo/oss/
14 | repo-update                         | openSUSE-Tumbleweed-Update                  | Yes     | (r ) Yes  | Yes     |   99     | http://download.opensuse.org/update/tumbleweed/
 9 | packman                             | packman                                     | Yes     | (r ) Yes  | Yes     |   90     | http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Tumbleweed/
15 | teamviewer                          | TeamViewer - x86_64                         | Yes     | (r ) Yes  | No      |   99     | http://linux.teamviewer.com/yum/stable/main/binary-x86_64/
 2 | home_concyclic_java                 | Java-related packages (openSUSE_Tumbleweed) | Yes     | (r ) Yes  | No      |   99     | https://download.opensuse.org/repositories/home:/concyclic:/java/openSUSE_Tumbleweed/
tinybit:/home/miguel # 

And here the output of KDEinfo on laptop:


Operating System: openSUSE Tumbleweed 20201012
KDE Plasma Version: 5.20.0
KDE Frameworks Version: 5.75.0
Qt Version: 5.15.1
Kernel Version: 5.8.14-1-default
OS Type: 64-bit
Processors: 4 × Intel® Core™ i3-2350M CPU @ 2.30GHz
Memory: 7.7 GiB of RAM
Graphics Processor: Mesa DRI Intel® HD Graphics 3000

Hi
To probably clarify;

Home repo X builds against Tumbleweed 20201014 for package Y and has dependency ABD, in release 20201012 is dependency ABC, so you will not get an update to package Y and so on and so on. The only way for it to work is for packages to build against the history repositories, what happens if there is a package in the Tumbleweed update repository, again it builds against 20201014, you won’t get that update… and so the dependency hell continues… :wink:

The real fix is for you to ask the Home repository maintainer to push to a development repository and maintain, then push to factory for inclusion in the release…
https://en.opensuse.org/openSUSE:How_to_contribute_to_Factory

Hi
Oh, plasma5-workspace 5.20 is only in snapshot 20201014…

https://review.tumbleweed.boombatower.com/2020/10/14/release.html

Likely your other system that updated is on 20201014 and not 20201012… check both systems with;


cat /etc/os-release

20201012 only has 5.19;
http://download.opensuse.org/history/20201012/tumbleweed/repo/oss/x86_64/plasma5-workspace-5.19.5-3.1.x86_64.rpm.mirrorlist

The laptop that updated has both(!):

http://download.opensuse.org/repositories/openSUSE:/Factory/snapshot/
http://download.opensuse.org/repositories/openSUSE:/Tumbleweed/standard/

… so I guess that’s where 5.20 came from.

Both your repository listings are somewhat asking for trouble perhaps…

Ok, thank you all that very kindly proposed hints and that contribute to this post.

Looks like the problem is on the laptop (tinybit) that it is running KDE 5.20 but it is still shows a repo as source for updates as http://download.opensuse.org/history/20201012/tumbleweed/repo/oss/ and tumbleweed cli shows target 20201012.
After running “tumbleweed uninit”, removing the package tumbleweed-cli-0.3.3-1.3.noarch and “zypper ref” followed by a “zypper dist-upgrade” it showed the message “Nothing to do.” what means the system already was in the current release 20201014.

In fact, after that, reinistalling tumbleweed cli (and initializing it) it shows now:

**tinybit:/home/miguel #** tumbleweed status
latest   : 20201019
target   : 20201012
installed: 20201014 
tinybit**:/home/miguel #**

which is compatible with the findings of the fellows @tannington and @malcolmlewis. Thanks guys !

As https://review.tumbleweed.boombatower.com/ reports that [FONT=monospace]20201019 has a rate of 97 I will update my desktop to that release too.

Ouch !

[/FONT]

Personally I wouldn’t get too hung up on boombatower ratings…

Just use the normal TW repositories, follow the factory mailing list: https://lists.opensuse.org/opensuse-factory/ for release announcements, such as this for 20201019 https://lists.opensuse.org/opensuse-factory/2020-10/msg00198.html - they contain a link for “Please check the known defects of this snapshot before upgrading” You can then decide on the basis of that if you want to perform a “zypper dup” or hold off until the next snapshot.

That’s been my strategy for the last five years or so, no real problems yet encountered… Tumbleweed continues to tumble along quite nicely…

I would like to give some personal adivise that goes in the same direction as @tannington’s.

Next time, better do not assume that people here know what the tumbleweed cli is and certainly do not assume that they have any experience with it. AFAIK it does not really belong to the distribution and many (most?) Tumbleweed users will not have it installed.

So e.g., when people, who try to help you, ask you to post

cat /etc/os-release

then please do not answer with output where you think it will provide the same or better information by using a non standard tool. The helpful person may not be glad at all with that at all.

Ah, ok. I got it !
Sorry, when I switched from ubuntu to tumbleweed a few monts ago, I learned about tumbleweed cli and I thought it was the standard way to deal with the almost daily releases of tumbleweed.

thanks !

Thanks for the tip. I only have knowledge of boombatower rates. Good to know another way.
Added the link to my bookmark;