I just wanted to upgrade a machine from 42.2 to 42.3. However, the 42.3 update repositories seem to be broken. The command “zypper ref” leads to the results listed below. I noticed that according to file timestamps of “16-Dec-2017 10:17”, i.e. about 3 hours ago, something has been done at http://download.opensuse.org/update/leap/42.3/oss/. Perhaps the error has been introduced by then?
What can I do now? Or when?
Repository ‘openSUSE Leap 42.3 Distribution Non-OSS’ is up to date.
Repository ‘openSUSE Leap 42.3 Distribution OSS’ is up to date.
Retrieving repository ‘openSUSE Leap 42.3 Update Non-OSS’ metadata …[error]
Repository ‘openSUSE Leap 42.3 Update Non-OSS’ is invalid.
[repo-42.3-update-non-oss|http://download.opensuse.org/update/leap/42.3/repo/non-oss/] Valid metadata not found at specified URL
Please check if the URIs defined for this repository are pointing to a valid repository.
Skipping repository ‘openSUSE Leap 42.3 Update Non-OSS’ because of the above error.
Retrieving repository ‘openSUSE Leap 42.3 Update OSS’ metadata …[error]
Repository ‘openSUSE Leap 42.3 Update OSS’ is invalid.
[repo-42.3-update-oss|http://download.opensuse.org/update/leap/42.3/repo/oss/] Valid metadata not found at specified URL
Please check if the URIs defined for this repository are pointing to a valid repository.
Skipping repository ‘openSUSE Leap 42.3 Update OSS’ because of the above error.
Some of the repositories have not been refreshed because of an error.
Please post the list of repositories as you hav them now, so we can check if they are correct:
zypper lr -d
Btw, I see this is your first post here: Welcome to the openSUSE forums.
Please not there is an important, but not easy to find feature on the forums:
Please in the future use CODE tags around copied/pasted computer text in a post. It is the # button in the tool bar of the post editor. When applicable copy/paste complete, that is including the prompt, the command, the output and the next prompt.
Sorry for not having used the CODE tag! Here’s the listing once again, and this time the URLs are hopefully kept intact:
machine:~ # LANG= zypper ref
Repository 'openSUSE Leap 42.3 Distribution Non-OSS' is up to date.
Repository 'openSUSE Leap 42.3 Distribution OSS' is up to date.
Retrieving repository 'openSUSE Leap 42.3 Update Non-OSS' metadata ..............................................................................................................................................................................................[error]
Repository 'openSUSE Leap 42.3 Update Non-OSS' is invalid.
[repo-42.3-update-non-oss|http://download.opensuse.org/update/leap/42.3/repo/non-oss/] Valid metadata not found at specified URL
Please check if the URIs defined for this repository are pointing to a valid repository.
Skipping repository 'openSUSE Leap 42.3 Update Non-OSS' because of the above error.
Retrieving repository 'openSUSE Leap 42.3 Update OSS' metadata ..................................................................................................................................................................................................[error]
Repository 'openSUSE Leap 42.3 Update OSS' is invalid.
[repo-42.3-update-oss|http://download.opensuse.org/update/leap/42.3/repo/oss/] Valid metadata not found at specified URL
Please check if the URIs defined for this repository are pointing to a valid repository.
Skipping repository 'openSUSE Leap 42.3 Update OSS' because of the above error.
Some of the repositories have not been refreshed because of an error.
machine:~ #
On multiple machines that have 42.3 already, “zypper ref” runs as expected, and when I upgraded these machines from 42.2 to 42.3 months ago, everything went like a charm.
Could it be the zypper software stack on 42.2 is broken, at least on my to-be-upgraded machine?
Could I run “zypper dup” without the update repositories, enable them after the upgrade, and only then update the packages?
I am using exactly the same URLs as for my machines that are already running 42.3 and updating from these repos regularly. In fact, I copied the URL to add the update repos from my browser’s URL field, just to make sure no error creeps in.
Currently the upgrade from 42.2 to 42.3 is running, with the update repos disabled. Well, we’ll see what the outcome will be …
Umph, you are right of course – I stand corrected.
Seems I copied the “distribution” URL and exchanged “distribution” by “update” and “oss” by “non-oss” to get the various permutations. Obviously the “/repo” escaped me, even when looking hard.
Anyway, the machine is upgraded now. Sorry for bothering you and thanks for you patience!