Bugzilla – Bug 1226025
Tumbleweed cannot get upgraded by 'zypper dup'
Last modified: 2024-06-12 08:03:18 UTC
Created attachment 875350 [details] yast logs Recently I experienced issues with zypper dup or zypper up. Tumbleweed could not get upgraded. Install Tumbleweed on my RPi 4. -- localhost:~ # zypper ref Repository 'Open H.264 Codec (openSUSE Tumbleweed)' is up to date. Repository 'openSUSE-Tumbleweed-Oss' is up to date. Repository 'openSUSE-Tumbleweed-Update' is up to date. All repositories have been refreshed. localhost:~ # cat /etc/os-release NAME="openSUSE Tumbleweed" # VERSION="20240530" ID="opensuse-tumbleweed" ID_LIKE="opensuse suse" VERSION_ID="20240530" PRETTY_NAME="openSUSE Tumbleweed" ANSI_COLOR="0;32" # CPE 2.3 format, boo#1217921 CPE_NAME="cpe:2.3:o:opensuse:tumbleweed:20240530:*:*:*:*:*:*:*" #CPE 2.2 format #CPE_NAME="cpe:/o:opensuse:tumbleweed:20240530" BUG_REPORT_URL="https://bugzilla.opensuse.org" SUPPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org" DOCUMENTATION_URL="https://en.opensuse.org/Portal:Tumbleweed" LOGO="distributor-logo-Tumbleweed" localhost:~ # zypper lr Repository priorities are without effect. All enabled repositories share the same priority. # | Alias | Name | Enabled | GPG Check | Refresh --+---------------+----------------------------------------+---------+-----------+-------- 1 | repo-debug | openSUSE-Tumbleweed-Debug | No | ---- | ---- 2 | repo-openh264 | Open H.264 Codec (openSUSE Tumbleweed) | Yes | (r ) Yes | Yes 3 | repo-oss | openSUSE-Tumbleweed-Oss | Yes | (r ) Yes | Yes 4 | repo-source | openSUSE-Tumbleweed-Source | No | ---- | ---- 5 | repo-update | openSUSE-Tumbleweed-Update | Yes | (r ) Yes | Yes localhost:~ # zypper lr 5 Alias : repo-update Name : openSUSE-Tumbleweed-Update URI : http://download.opensuse.org/ports/aarch64/update/tumbleweed/ Enabled : Yes GPG Check : (r ) Yes Priority : 99 (default priority) Autorefresh : On Keep Packages : Off Type : rpm-md GPG Key URI : Path Prefix : Parent Service : Keywords : --- Repo Info Path : /etc/zypp/repos.d/repo-update.repo MD Cache Path : /var/cache/zypp/raw/repo-update localhost:~ # zypper lu Loading repository data... Reading installed packages... No updates found. localhost:~ # zypper up Loading repository data... Reading installed packages... Nothing to do. localhost:~ # -- There is already newer releases available on openQA, but it doesn't work anymore for upgrade.
On another Tumbleweed I could upgrade and it shows after upgrade version 20240531, but not the latest version which I expected: 20240605 d5-129:~ # cat /etc/os-release NAME="openSUSE Tumbleweed" # VERSION="20240531" ID="opensuse-tumbleweed" ID_LIKE="opensuse suse" VERSION_ID="20240531" PRETTY_NAME="openSUSE Tumbleweed" ANSI_COLOR="0;32" # CPE 2.3 format, boo#1217921 CPE_NAME="cpe:2.3:o:opensuse:tumbleweed:20240531:*:*:*:*:*:*:*" #CPE 2.2 format #CPE_NAME="cpe:/o:opensuse:tumbleweed:20240531" BUG_REPORT_URL="https://bugzilla.opensuse.org" SUPPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org" DOCUMENTATION_URL="https://en.opensuse.org/Portal:Tumbleweed" LOGO="distributor-logo-Tumbleweed"
You will need to wait until the snapshot was actually released, which is the case now.
Please see https://openqa.opensuse.org/tests/4252490#downloads We have already much newer version for Tumbleweed aarch64 RPi I still cannot get any updates for RPi 4, please investigate, thanks!
You noticed that your repolist is incomplete?
(In reply to hui from comment #4) > You noticed that your repolist is incomplete? incomplete? Can you point out what is missing? I have 5 repositories. I've compared with snapshot 20240524 which can upgraded to 20240606. It has the same repositories as on snapshot 20240530.
You are missing the non-OSS repo which is part of every Tumbleweed installation (even for aarch64).
(In reply to hui from comment #6) > You are missing the non-OSS repo which is part of every Tumbleweed > installation (even for aarch64). really? then it is an issue with repositories on Tumbleweed. I didn't remove any repository.
I tested again, this issue has nothing to with non-oss repository. I can now upgrade von 20240606 to 20240610. I assume that new snapshot was not released at that time.