When i run a sudo zypper update i get the below.list of repo errors. is this normal? how can i resolve it?
Thanks
Retrieving repository 'google-chrome' metadata .........................................................[done]
Building repository 'google-chrome' cache ..............................................................[done]
Repository 'Non-OSS Repository' is invalid.
[repo-non-oss|http://download.opensuse.org/distribution/leap/20190829/repo/non-oss/] Repository type can't be determined.
Please check if the URIs defined for this repository are pointing to a valid repository.
Warning: Skipping repository 'Non-OSS Repository' because of the above error.
Repository 'Main Repository' is invalid.
[repo-oss|http://download.opensuse.org/distribution/leap/20190829/repo/oss/] Repository type can't be determined.
Please check if the URIs defined for this repository are pointing to a valid repository.
Warning: Skipping repository 'Main Repository' because of the above error.
Repository 'Main Update Repository' is invalid.
[repo-update|http://download.opensuse.org/update/leap/20190829/oss/] Repository type can't be determined.
Please check if the URIs defined for this repository are pointing to a valid repository.
Warning: Skipping repository 'Main Update Repository' because of the above error.
Repository 'Update Repository (Non-Oss)' is invalid.
[repo-update-non-oss|http://download.opensuse.org/update/leap/20190829/non-oss/] 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 Repository (Non-Oss)' because of the above error.
Some of the repositories have not been refreshed because of an error.
Loading repository data...
Reading installed packages...
Thanks for the quick reply! its not been the smootest of starts the laptop wouldnt connect to the wifi untill i turned off yast which seems to be the thing that everyone uses for most things…
Hi
So if you fire up YaST -> Software Repositories and disable ALL of the repositories with “leap/20190829” in them and the post back the new output from the command;
Hi
It should be there, if not let’s use zypper instead and can come back to that.
zypper mr -d -F 6 7 8 9 10 11 12 13 14 15
So the mr = modify, the -d = disable and the -F = no-refresh, there are a couple of repositories missing, but lets get your system updated (and hopefully YaST will come back to life…)
You need to disable 16 and 17 as well. You now have a mix of Tumbleweed and 2 Leap versions on the system which leads to the results you’re experiencing.
After doing so, you also need to run
sudo zypper dup
and accept the suggested packages to be installed. Then reboot.
So thats all ran, im not longer getting the errors, updates are showing as fully done… Yast is now showing again
Should this be back up and running now? Should i delete any of the repos if there not needed? open yast2 and deleted one of the google chrome repos (When i open app → software i still get an error saying it cant download from the http://dl.google… is that right)?
Well everything seems to be working, ive got everything i wanted installed. the only issue i have is that i cant get virtualbox installed. im following
tried deleting the repo and adding it back again but i get errors:
sudo zypper install VirtualBox-6.0
[sudo] password for root:
Loading repository data...
Reading installed packages...
'VirtualBox-6.0' not found in package names. Trying capabilities.
No provider of 'VirtualBox-6.0' found.
Resolving package dependencies...
A version number is seldom part of a package name.
To find a package, it is most easy to use YaST > Software > Softwa Management. Entering the word “virtual” (without the ") in the search field and clicking Search will give you a list of package names with that string in the name. Easy to scroll through them. IMHO
Yes i tried that to, with one of the other tools i was trying to install i found in search then click accept and it installed it. When i do the same for virtualbox the Yast window closes straight away (no loading bar etc)…
Of course it should. And I gave the correct name of the pcakage in my post. But I tried to coummunicate to the OP how you can find the correct name of a package when you only have a product/program name, but do not know how the package is called exactly (same, with or without upper/lower case charcters, etc.).
The Tecmint instructions are supposed to install Virtualbox from the Oracle website and I do not agree with those instructions because they are more complicated than it has to be.
First,
You should know that openSUSE pre-compiles and provides virtualbox packages that for the most part simply copies the necessary files to your system, avoiding a number of things that have to work without a problem on your machine. Downloading and installing from Oracle instead of openSUSE should still work, but many prefer to simply rely on what openSUSE provides instead… particularly on Tumbleweed
If you want to** install from openSUSE**, Virtualbox 6.x will be installed by default, you simply run the following command if your OSS repository is enabled (and it should always be)
zypper in virtualbox
If you wish instead to download from Oracle, then you should visit the Oracle download page (the following link), download and execute the Linux binary https://www.virtualbox.org/wiki/Downloads
The Linux RPM instructions are generic, we in openSUSE have it much easier. Simply run the following in a console where your RPM is located, accepting any warnings
zypper in VirtualBox-6.0-6.0.10_132072_openSUSE150-1.x86_64.rpm
Hi sorry for the long delay… had the pleasure of a holiday.
So ideally i would love to just use zypper… Is there a good way to get search through all the different repos?
I tried the suggestion and got this though
PackageKit is blocking zypper. This happens if you have an updater applet or
other software management application using PackageKit running.
We can ask PackageKit to interrupt the current action as soon as possible, but
it depends on PackageKit how fast it will respond to this request.
Exactly what it says is happening: The updater applet is still checking the repos and hence blocks access to the package database, hence blocks zypper. Wait for the applet to finish, then retry the zypper command.