When attempting to upgrade to leap 16.0 beta I encountered the errors shown below.
The repoindex.xml linked to opensuse-leap-repoindex.xml is from openSUSE-repos-Leap-20250303.
Why is this happening?
USS-Liberty:~ # zypper dup
Refreshing service 'openSUSE'.
Retrieving repository 'repo-non-oss ()' metadata ..............................................................................................................................................................................................[error]
Repository 'repo-non-oss ()' is invalid.
[openSUSE:repo-non-oss|http://cdn.opensuse.org/distribution/leap//repo/non-oss?mediahandler=curl2] Failed to retrieve new repository metadata.
History:
- [openSUSE:repo-non-oss|http://cdn.opensuse.org/distribution/leap//repo/non-oss?mediahandler=curl2] Repository type can't be determined.
Please check if the URIs defined for this repository are pointing to a valid repository.
Warning: Skipping repository 'repo-non-oss ()' because of the above error.
Retrieving repository 'repo-oss ()' metadata ..................................................................................................................................................................................................[error]
Repository 'repo-oss ()' is invalid.
[openSUSE:repo-oss|http://cdn.opensuse.org/distribution/leap//repo/oss?mediahandler=curl2] Failed to retrieve new repository metadata.
History:
- [openSUSE:repo-oss|http://cdn.opensuse.org/distribution/leap//repo/oss?mediahandler=curl2] Repository type can't be determined.
Please check if the URIs defined for this repository are pointing to a valid repository.
Warning: Skipping repository 'repo-oss ()' because of the above error.
Retrieving repository 'update-backports ()' metadata ..........................................................................................................................................................................................[error]
Repository 'update-backports ()' is invalid.
[openSUSE:update-backports|http://cdn.opensuse.org/update/leap//backports?mediahandler=curl2] Failed to retrieve new repository metadata.
History:
- [openSUSE:update-backports|http://cdn.opensuse.org/update/leap//backports?mediahandler=curl2] Repository type can't be determined.
Please check if the URIs defined for this repository are pointing to a valid repository.
Warning: Skipping repository 'update-backports ()' because of the above error.
Retrieving repository 'update-non-oss ()' metadata ............................................................................................................................................................................................[error]
Repository 'update-non-oss ()' is invalid.
[openSUSE:update-non-oss|http://cdn.opensuse.org/update/leap//non-oss?mediahandler=curl2] Failed to retrieve new repository metadata.
History:
- [openSUSE:update-non-oss|http://cdn.opensuse.org/update/leap//non-oss?mediahandler=curl2] Repository type can't be determined.
Please check if the URIs defined for this repository are pointing to a valid repository.
Warning: Skipping repository 'update-non-oss ()' because of the above error.
Retrieving repository 'update-oss ()' metadata ................................................................................................................................................................................................[error]
Repository 'update-oss ()' is invalid.
[openSUSE:update-oss|http://cdn.opensuse.org/update/leap//oss?mediahandler=curl2] Failed to retrieve new repository metadata.
History:
- [openSUSE:update-oss|http://cdn.opensuse.org/update/leap//oss?mediahandler=curl2] Repository type can't be determined.
Please check if the URIs defined for this repository are pointing to a valid repository.
Warning: Skipping repository 'update-oss ()' because of the above error.
Retrieving repository 'update-sle ()' metadata ................................................................................................................................................................................................[error]
Repository 'update-sle ()' is invalid.
[openSUSE:update-sle|http://cdn.opensuse.org/update/leap//sle?mediahandler=curl2] Failed to retrieve new repository metadata.
History:
- [openSUSE:update-sle|http://cdn.opensuse.org/update/leap//sle?mediahandler=curl2] Repository type can't be determined.
Please check if the URIs defined for this repository are pointing to a valid repository.
Warning: Skipping repository 'update-sle ()' because of the above error.
Some of the repositories have not been refreshed because of an error.
dist-upgrade: Due to the treatment of orphaned packages dist-upgrade depends on a proper
repository setup more than any other command. It must not continue if enabled repositories fail
to refresh. This may severely damage the system. If a failing repository is actually not needed,
it must be disabled. See 'man zypper' for more information about this command.
USS-Liberty:~ #
I am not using Leap 16 in any form, but I would expect that the URLs of the standard repos would mention “16” somewhere. I do not see that in your code above.
Maybe better start is to check/post your repo list (including URLs)?
Sorry if my post is confusing. I haven’t gotten that far. I just figured someone else might have encountered the problem while attempting the upgrade. This is a problem with 15.6.
Also, you just show a zypper dup command without explaining what it is supposed to do. Depending on the way you try to upgrade to 16.0 (which you also did not communicate to us) this may be an incorrect command (e.g. for on-line upgrade you need a --releasever 16.0 global option, or you need manual updated repo URLs).
The result is the same for zipper refresh. YaST also gives errors. It might be from trying to migrate to slowroll. I gave up when I had close to 5000 conflicts to resolve by hand.
That’s what I started with. But now the configuration is fubar. For some reason zipper lost track of the releasever setting it uses by default. When I try to change the repositories I get
“Repository ‘repo-oss ()’ is managed by service ‘openOUSE’. Your manual changes might be reset by the next service refresh!”