Recently updated via YaST, zypper reports
Warning: Repository 'openSUSE:Backports:SLE-15-SP4' appears to be outdated. Consider using a different mirror o
r server.
Is there another mirror/server?
It’s likely that repo was added at some point as part of a 1-click install. The “Backports” repository as defined in package “openSUSE-release” is:
https://download.opensuse.org/update/leap/$releasever/backports/
(or if you prefer explicit version numbers: https://download.opensuse.org/update/leap/15.4/backports/ )
You may want to consider changing the URL.
**6700K:~ #** wget https://download.opensuse.org/repositories/openSUSE:Backports:SLE-15-SP4
--2022-09-09 13:41:37-- https://download.opensuse.org/repositories/openSUSE:Backports:SLE-15-SP4
Resolving download.opensuse.org (download.opensuse.org)... 2001:67c:2178:8::13, 195.135.221.134
Connecting to download.opensuse.org (download.opensuse.org)|2001:67c:2178:8::13|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2022-09-09 13:41:37 ERROR 404: Not Found.
**6700K:~ #**
Yes I would expect a 404, you’re missing a few “/” (“https://download.opensuse.org/repositories/openSUSE:/Backports:/SLE-15-SP4/”)
paul@HP255G7:~> wget https://download.opensuse.org/repositories/openSUSE:/Backports:/SLE-15-SP4/
--2022-09-09 13:17:24-- https://download.opensuse.org/repositories/openSUSE:/Backports:/SLE-15-SP4/
Resolving download.opensuse.org (download.opensuse.org)... 195.135.221.134, 2001:67c:2178:8::13
Connecting to download.opensuse.org (download.opensuse.org)|195.135.221.134|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: ‘index.html’
index.html <=> ] 8.91K --.-KB/s in 0s
2022-09-09 13:17:24 (59.3 MB/s) - ‘index.html’ saved [9126]
paul@HP255G7:~>
Nonetheless, I’d still replace that with the “official” Leap 15.4 backports URL
Yep. The original post is very terse about the repo:
**erlangen:~ #** zypper lr openSUSE_Backports_SLE-15-SP4_Update
Alias : openSUSE_Backports_SLE-15-SP4_Update
Name : Online updates for openSUSE:Backports:SLE-15-SP4 (standard)
URI : http://download.opensuse.org/update/leap/15.4/backports/
Enabled : Yes
GPG Check : ( p) Yes
Priority : 99 (default priority)
Autorefresh : On
Keep Packages : Off
Type : NONE
GPG Key URI : http://download.opensuse.org/update/leap/15.4/backports/repodata/repomd.xml.key
Path Prefix :
Parent Service :
Keywords : ---
Repo Info Path : /etc/zypp/repos.d/openSUSE_Backports_SLE-15-SP4_Update.repo
MD Cache Path : /var/cache/zypp/raw/openSUSE_Backports_SLE-15-SP4_Update
**erlangen:~ #**
**erlangen:~ #** zypper refresh openSUSE_Backports_SLE-15-SP4_Update
Retrieving repository 'Online updates for openSUSE:Backports:SLE-15-SP4 (standard)' metadata ...........................................................................................................................................[done]
Building repository 'Online updates for openSUSE:Backports:SLE-15-SP4 (standard)' cache ................................................................................................................................................[done]
Specified repositories have been refreshed.
**erlangen:~ #**
Interesting… I note you also have the name and alias as SLE-15-SP4 - Yet the package that initially defines those, openSUSE-release, has:
[repo-backports-update]
name=Update repository of openSUSE Backports
enabled=1
autorefresh=1
baseurl=http://download.opensuse.org/update/leap/$releasever/backports/
path=/
type=rpm-md
keeppackages=0
Maybe the names changed at some point after the initial (or pre) release of 15.4 - I only updated to 15.4 a few days ago.
I found many of the names used to long (gives un managable listings with e.g. zypper lr -d). Also Aliases IMHO should be short, but still meaningful, words to use in commands. First thing is of course to remove the string “repo” from all of them Superfluous (what else are we handling here). in short:
henk@boven:~> cat /etc/zypp/repos.d/backports-update.repo
[backports-update]
name=Updates from openSUSE Backports
enabled=1
autorefresh=1
baseurl=http://download.opensuse.org/update/leap/$releasever/backports/
path=/
type=rpm-md
keeppackages=0
henk@boven:~>
Now I’m really confused.
Yes, we went more and more off-topic (I am also guilty).
I booted host 6700K into Leap. The canonical upgrade resulted in the following list:
**Leap-15-4:~ #** zypper lr -E
# | Alias | Enabled | GPG Check | Priority | URI
---+-----------------------+---------+-----------+----------+-------------------------------------------------------------------------
4 | packman | Yes | (r ) Yes | 90 | https://ftp.fau.de/packman/suse/openSUSE_Leap_15.4/
6 | repo-backports-update | Yes | (r ) Yes | 99 | https://mirrorcache-eu.opensuse.org/update/leap/15.4/backports/
11 | repo-non-oss | Yes | (r ) Yes | 99 | https://mirrorcache-eu.opensuse.org/distribution/leap/15.4/repo/non-oss/
12 | repo-oss | Yes | (r ) Yes | 99 | https://mirrorcache-eu.opensuse.org/distribution/leap/15.4/repo/oss/
14 | repo-sle-update | Yes | (r ) Yes | 99 | https://mirrorcache-eu.opensuse.org/update/leap/15.4/sle/
16 | repo-update | Yes | (r ) Yes | 99 | https://mirrorcache-eu.opensuse.org/update/leap/15.4/oss
17 | repo-update-non-oss | Yes | (r ) Yes | 99 | https://mirrorcache-eu.opensuse.org/update/leap/15.4/non-oss/
**Leap-15-4:~ #**
Yes, I can relate to that… confusing myself I think :\
could you post the output from:
zypper lr -d
The alias and name of that repository may well have lead me to the wrong conclusion.
As requested…
**localhost:/home/ion #** zypper lr -d
# | Alias | Name | Enab
led | GPG Check | Refresh | Priority | Type | URI
| Service
---+--------------------------------------+--------------------------------------------------------------+-----
----+-----------+---------+----------+--------+----------------------------------------------------------------
------------------------------+--------
1 | brave-browser | brave-browser | Yes
| (r ) Yes | Yes | 99 | rpm-md | https://brave-browser-rpm-release.s3.brave.com/x86_64/
|
2 | http-download.opensuse.org-e4fc5f5a | openSUSE:Leap:15.4:Update | Yes
| (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/leap/15.4/oss/
|
3 | https-download.opensuse.org-23bea7fa | multimedia:apps | Yes
| (r ) Yes | Yes | 99 | rpm-md | https://download.opensuse.org/repositories/multimedia:/apps/15.
4/ |
4 | https-download.opensuse.org-40184fdd | multimedia:libs | Yes
| (r ) Yes | Yes | 99 | rpm-md | https://download.opensuse.org/repositories/multimedia:/libs/15.
4/ |
5 | https-download.opensuse.org-71479346 | openSUSE:Backports:SLE-15-SP4 | Yes
| (r ) Yes | Yes | 99 | rpm-md | https://download.opensuse.org/repositories/openSUSE:/Backports:
/SLE-15-SP4/standard/ |
6 | https-download.opensuse.org-f727009d | openSUSE:Backports:SLE-15-SP4:Checks | Yes
| (r ) Yes | Yes | 99 | rpm-md | https://download.opensuse.org/repositories/openSUSE:/Backports:
/SLE-15-SP4:/Checks/standard/ |
7 | nordvpn | nordvpn | Yes
| (r ) Yes | Yes | 99 | rpm-md | https://repo.nordvpn.com//yum/nordvpn/centos/x86_64
|
8 | openSUSE-Leap-15.4-1 | openSUSE-Leap-15.4-1 | Yes
| (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/distribution/leap/15.4/repo/oss/
|
9 | repo-backports-update | Update repository of openSUSE Backports | Yes
| (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/leap/15.4/backports/
|
10 | repo-non-oss | Non-OSS Repository | Yes
| (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/distribution/leap/15.4/repo/non-os
s/ |
11 | repo-oss | Main Repository | Yes
| (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/distribution/leap/15.4/repo/oss/
|
12 | repo-sle-update | Update repository with updates from SUSE Linux Enterprise 15 | Yes
| (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/leap/15.4/sle/
|
13 | repo-update | Main Update Repository | Yes
| (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/leap/15.4/oss
|
14 | repo-update-non-oss | Update Repository (Non-Oss) | Yes
| (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/leap/15.4/non-oss/
|
15 | vivaldi | vivaldi | Yes
| (r ) Yes | Yes | 99 | rpm-md | https://repo.vivaldi.com/archive/rpm/x86_64
|
**localhost:/home/ion #**
You’ve some duplicated/redundant repositories there, partly as I thought.
The repositories with an alias that ends with an 8 character hex number have been added by 1-click, some of which are redundant.
I would initially clean up as follows:
Remove #2 - provided by #13
Remove #5 & #6 - provided by #9
Remove #8 - provided by #11
Thank you. Life is simpler again. And I will stop installing via 1-click.
Yes, 1-click seems seriously broken at the moment, often installing many unneeded repositories, and duplicating others.
If you do use it, check very carefully what has been added.
One last thought…
You might want to check what’s been installed from:
https-download.opensuse.org-23bea7fa | multimedia:apps
and
https-download.opensuse.org-40184fdd | multimedia:libs
You may find the package(s) from there are in the standard OSS repos, although as they are multimedia that is perhaps less likely.
I am receiving the same message from the 15.3 repository for last two days.
It began with
Update Error
There is no update candidate for kernel-default-devel-5.3.18-150300.59.90.1.x86_64
The following day I received an update for package libzypp (listed as the only available update). After installing that I received
a message You have 40 new updates. Attempting to install those, I still get:
Update Error
There is no update candidate for kernel-default-devel-5.3.18-150300.59.90.1.x86_64
Running zypper up from CLI I see:
Warning: Repository ‘Main Update Repository’ appears to be outdated. Consider using a different mirror or server.
Reading installed packages…
I am pointed at the main SuSE repositories.
No idea why it is even messing with kernel-devel, I only use the default.
The fact that you get on a zypper up/patch (or equivalent with YaST > Software) first an update for libzypp and after that alarger set of updates is logical. An update to libzypp has to be done first and on it’s own, because you are using libzypp for the update itself. So a new start of libzypp must be done asap after it’s update is done (like a reboot after a new kernel, or a stop/start of Firefox when it was running during it is updated). Only then the new libzypp will be used for the rest of the updates that are available.
I know this does not help wihj the other message, but you should not confuse normal behaviour with the problem.
First take a look at:
https://forums.opensuse.org/showthread.php/573320-Outdated-Main-Repository?p=3156397#post3156397
and
https://forums.opensuse.org/showthread.php/573320-Outdated-Main-Repository?p=3156649#post3156649
It may be useful also to post your repository list:
zypper lr -u
I’ve one machine still on 15.3 and a “zypper up” completed OK on that a few minutes ago.