Relatively new to Tumbleweed. I have been using Discovery to update for some time now and up until a couple of weeks ago it has worked fine. I am getting “Internal Error : Installation has been aborted as directed”. It also said to try later which I did with the same error. I now have 2997 updates. I did some searching and found a suggestion to clear cache which I did with zypper but still got the same error. I then tried zypper update and got the following error messages.
In cache libcanberra-gtk3-0-0.30+2-3.4.x86_64.rpm (1818/3004), 16.1 KiB
In cache libcanberra-gtk-module-common-0.30+2-3.4.x86_64.rpm (1819/3004), 14.6 KiB
In cache libao4-1.2.2+git20180114.d522165-3.8.x86_64.rpm (1820/3004), 35.3 KiB
In cache ghc-time-1.14-1.2.x86_64.rpm (1821/3004), 300.3 KiB
In cache ghc-th-compat-0.1.7-1.2.x86_64.rpm (1822/3004), 19.7 KiB
In cache ghc-tagged-0.8.10-2.2.x86_64.rpm (1823/3004), 40.5 KiB
In cache ghc-primitive-0.9.1.0-2.2.x86_64.rpm (1824/3004), 137.6 KiB
In cache ghc-exceptions-0.10.12-1.2.x86_64.rpm (1825/3004), 74.7 KiB
Retrieving: ghc-containers-0.7-1.2.x86_64 (Main Repository (OSS)) (1826/3004), 636.2 KiB
Retrieving: ghc-containers-0.7-1.2.x86_64.rpm …[not found]
Retrieving: ghc-containers-0.7-1.2.x86_64.rpm …[not found]
Retrieving: ghc-containers-0.7-1.2.x86_64.rpm …[not found]
Retrieving: ghc-containers-0.7-1.2.x86_64.rpm …[not found]
Retrieving: ghc-containers-0.7-1.2.x86_64.rpm …[error (327.8 KiB/s)]
Failed to provide Package ghc-containers-0.7-1.2.x86_64 (Main Repository (OSS)). Do you want to retry retrieva
l?
Discover works fine for updating the system, firmware, and flatpaks, because Discover doesn’t actually update anything on it’s own.
I’m not entirely certain how many times this has to be said, but at least once more, apparently.
Discover does updates based on the backends installed.
[sfalken@mustang ~]$ zypper se discover6-backend
Loading repository data...
Reading installed packages...
S | Name | Summary | Type
---+----------------------------------------+------------------------------------------------------------+--------
i | discover6-backend-flatpak | Flatpak Backend for Discover | package
| discover6-backend-flatpak-debuginfo | Debug information for package discover6-backend-flatpak | package
i | discover6-backend-fwupd | fwupd Backend for Discover | package
| discover6-backend-fwupd-debuginfo | Debug information for package discover6-backend-fwupd | package
| discover6-backend-packagekit | PackageKit Backend for Discover | package
| discover6-backend-packagekit-debuginfo | Debug information for package discover6-backend-packagekit | package
discover6-backend-flatpak handles the management and update of flatpaks discover6-backend-fwupd handles the update of firmware from the LVFS discover6-backend-packagekit handles the installation, removal, and updating of RPM packages via PackageKit (which in turn is using zypper up on leap, and zypper dup on tumbleweed)
The thing discover/discover6-backend-packagekitcannot do, is resolve conflicts, that is going to just fail silently. (e.g. most often run into with the packman repositories enabled).
If you’re using discover and you feel that you’ve not gotten updates in a while (or are just curious), it is worth running a manual zypper dup in a terminal from time to time, especially if you have third-party repositories enabled, or frankly any repositories other than oss, non-oss, update, and openh264 .
Thank you. I did not see those other issues. Will have to do some reading and investigation as I am not sure what they mean, still trying to get a handle on things.
