# Digest verification errors for Package Hub on system install **URL:** \ **Category:** SLED Configure-Administer\ **Created:** [July 23, 2018, 4:37am UTC](https://forums.suse.com/t/digest-verification-errors-for-package-hub-on-system-install/32714 "2018-07-23T04:37:47Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![fusion809](https://avatars.discourse-cdn.com/v4/letter/f/e95f7d/32.png) [@fusion809](https://forums.suse.com/u/fusion809)\ **Post date:** [July 23, 2018, 4:37am UTC](https://forums.suse.com/t/digest-verification-errors-for-package-hub-on-system-install/32714/1 "2018-07-23T04:37:47Z")
Hi, During SLED 15 installation my ethernet cable popped out for a minute and I didn’t realize this after I had skipped the installation of a few packages (as it gave the usual error message when it couldn’t download the package it wanted and I kept selecting “Skip”) as they couldn’t be downloaded. The installation of SLED 15 otherwise went without issue. Since the installation whenever I run: ```auto zypper dup ``` I get: ```auto Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Refreshing service 'Basesystem_Module_15_x86_64'. Refreshing service 'Desktop_Applications_Module_15_x86_64'. Refreshing service 'Development_Tools_Module_15_x86_64'. Refreshing service 'SUSE_Linux_Enterprise_Desktop_15_x86_64'. Refreshing service 'SUSE_Linux_Enterprise_Workstation_Extension_15_x86_64'. Refreshing service 'SUSE_Package_Hub_15_x86_64'. Loading repository data... Reading installed packages... Computing distribution upgrade... The following 2 packages are going to be upgraded: vim vim-data The following 12 packages are going to be reinstalled: gnome-icon-theme-extras gnome-icon-theme-symbolic nautilus-sendto-lang notification-daemon-lang parallel-printer-support poppler-data python-cloudfiles python3-ndg-httpsclient seahorse-nautilus-lang sushi-lang urlscan xorg-scripts The following 2 packages are going to change vendor: vim SUSE LLC -> obs://build.opensuse.org/home:fusion809 vim-data SUSE LLC -> obs://build.opensuse.org/home:fusion809 The following 14 packages have no support information from their vendor: gnome-icon-theme-extras gnome-icon-theme-symbolic nautilus-sendto-lang notification-daemon-lang parallel-printer-support poppler-data python-cloudfiles python3-ndg-httpsclient seahorse-nautilus-lang sushi-lang urlscan vim vim-data xorg-scripts 2 packages to upgrade, 12 to reinstall, 2 to change vendor. Overall download size: 10.1 MiB. Already cached: 0 B. After the operation, additional 1.4 MiB will be used. Continue? [y/n/...? shows all options] (y): y Retrieving package gnome-icon-theme-extras-3.12.0-1.1.noarch (1/14), 847.2 KiB (917.7 KiB unpacked) Retrieving: gnome-icon-theme-extras-3.12.0-1.1.noarch.rpm ......................................................................................................................................................................................................[done] Warning: Digest verification failed for file 'gnome-icon-theme-extras-3.12.0-1.1.noarch.rpm' [/var/cache/zypp/packages/SUSE_Package_Hub_15_x86_64:SUSE-PackageHub-15/noarch_SP0/gnome-icon-theme-extras-3.12.0-1.1.noarch.rpm] expected 30d89d6bde938786238110692ab977cdca7390117b54ce0a528786707ba5568a but got aa295a602c1fe64a140d324134211c64fb47447294472b448396753862856580 Accepting packages with wrong checksums can lead to a corrupted system and in extreme cases even to a system compromise. However if you made certain that the file with checksum 'aa29..' is secure, correct and should be used within this operation, enter the first 4 characters of the checksum to unblock using this file on your own risk. Empty input will discard the file. Unblock or discard? [aa29/...? shows all options] (discard): ``` (where the vim package upgrades were only with the last time I ran this command and they’re due to me adding my own OBS repo, other times it was just like this, but without the Vim vendor change). Note how digest verification errors occur. If I choose to unblock each package and install them they’re installed, but then the next time I run zypper dup I get the exact same result, it asks me to reinstall these packages with digest verification errors. This is getting irritating, please tell me there’s a way to fix this permanently. Thanks for your time and patience, Brenton ---
**Author:** ![malcolmlewis](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/malcolmlewis/32/11375_2.png) [@malcolmlewis](https://forums.suse.com/u/malcolmlewis)\ **Post date:** [July 23, 2018, 5:25am UTC](https://forums.suse.com/t/digest-verification-errors-for-package-hub-on-system-install/32714/2 "2018-07-23T05:25:28Z")
> [@](#): > > On Mon 23 Jul 2018 01:44:02 AM CDT, fusion809 wrote: > > Hi, > > During SLED 15 installation my ethernet cable popped out for a minute > and I didn’t realize this after I had skipped the installation of a few > packages (as it gave the usual error message when it couldn’t download > the package it wanted and I kept selecting “Skip”) as they couldn’t be > downloaded. The installation of SLED 15 otherwise went without issue. > Since the installation whenever I run: > > ## Code: > > zypper dup > > * * * > > I get: > > ## Code: > > Warning: You are about to do a distribution upgrade with all enabled > repositories. Make sure these repositories are compatible before you > continue. See ‘man zypper’ for more information about this command. > Refreshing service ‘Basesystem\_Module\_15\_x86\_64’. Refreshing service > ‘Desktop\_Applications\_Module\_15\_x86\_64’. Refreshing service > ‘Development\_Tools\_Module\_15\_x86\_64’. Refreshing service > ‘SUSE\_Linux\_Enterprise\_Desktop\_15\_x86\_64’. Refreshing service > ‘SUSE\_Linux\_Enterprise\_Workstation\_Extension\_15\_x86\_64’. Refreshing > service ‘SUSE\_Package\_Hub\_15\_x86\_64’. Loading repository data… > Reading installed packages… Computing distribution upgrade… > > The following 2 packages are going to be upgraded: > vim vim-data > > The following 12 packages are going to be reinstalled: > gnome-icon-theme-extras gnome-icon-theme-symbolic > nautilus-sendto-lang notification-daemon-lang parallel-printer-support > poppler-data python-cloudfiles python3-ndg-httpsclient > seahorse-nautilus-lang sushi-lang urlscan xorg-scripts The following 2 > packages are going to change vendor: vim SUSE LLC > [https://www.suse.com/](https://www.suse.com/) → obs://build.opensuse.org/home:fusion809 > vim-data SUSE LLC [https://www.suse.com/](https://www.suse.com/) → > obs://build.opensuse.org/home:fusion809 The following 14 packages have > no support information from their vendor: gnome-icon-theme-extras > gnome-icon-theme-symbolic nautilus-sendto-lang notification-daemon-lang > parallel-printer-support poppler-data python-cloudfiles > python3-ndg-httpsclient seahorse-nautilus-lang sushi-lang urlscan vim > vim-data xorg-scripts 2 packages to upgrade, 12 to reinstall, 2 to > change vendor. Overall download size: 10.1 MiB. Already cached: 0 B. > After the operation, additional 1.4 MiB will be used. Continue? > [y/n/…? shows all options] (y): y Retrieving package > gnome-icon-theme-extras-3.12.0-1.1.noarch > (1/14), 847.2 KiB (917.7 KiB unpacked) Retrieving: > gnome-icon-theme-extras-3.12.0-1.1.noarch.rpm …[done] > Warning: Digest verification failed for file > ‘gnome-icon-theme-extras-3.12.0-1.1.noarch.rpm’ [/var/cache/zypp/packages/SUSE\_Package\_Hub\_15\_x86\_64:SUSE-PackageHub-15/noarch\_SP0/gnome-icon-theme-extras-3.12.0-1.1.noarch.rpm] > expected > 30d89d6bde938786238110692ab977cdca7390117b54ce0a528786707ba5568a but > got aa295a602c1fe64a140d324134211c64fb47447294472b448396753862856580 > Accepting packages with wrong checksums can lead to a corrupted system > and in extreme cases even to a system compromise. However if you made > certain that the file with checksum ‘aa29…’ is secure, correct and > should be used within this operation, enter the first 4 characters of > the checksum to unblock using this file on your own risk. Empty input > will discard the file. Unblock or discard? [aa29/…? shows all > options] (discard): -------------------- > > (where the vim package upgrades were only with the last time I ran this > command and they’re due to me adding my own OBS repo, other times it was > just like this, but without the Vim vendor change). Note how digest > verification errors occur. If I choose to unblock each package and > install them they’re installed, but then the next time I run zypper dup > I get the exact same result, it asks me to reinstall these packages with > digest verification errors. This is getting irritating, please tell me > there’s a way to fix this permanently. > > Thanks for your time and patience, > Brenton Hi There is no need to run dup (for service pack upgrade we use zypper migration), just use up… dup to switch repos. I would remove package hub/re-add or re-import the key… Also sometimes there can be a delay in packages getting mirrored out, wait a we while and try again. – Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890) SLES 15 | GNOME Shell 3.26.2 | 4.12.14-23-default If you find this post helpful and are logged into the web interface, please show your appreciation and click on the star below… Thanks! ---
**Author:** ![fusion809](https://avatars.discourse-cdn.com/v4/letter/f/e95f7d/32.png) [@fusion809](https://forums.suse.com/u/fusion809)\ **Post date:** [July 23, 2018, 5:40am UTC](https://forums.suse.com/t/digest-verification-errors-for-package-hub-on-system-install/32714/3 "2018-07-23T05:40:22Z")
How do I do that, re-adding Package Hub, that is? I removed the three Package Hub repos with zypper. Then I looked up Package Hub repo in the hope I’d have a nice zypper ar … command but I found [https://packagehub.suse.com/](https://packagehub.suse.com/). I followed the “More…” link to [https://packagehub.suse.com/how-to-use/](https://packagehub.suse.com/how-to-use/) and I went for the only command-line option I saw, “Enabling with SUSEConnect”, so I ran: ```auto SUSEConnect -p PackageHub/15.0/x86_64 ``` and it seems I’m back to where I was before with these packages with digest verification errors. ---
**Author:** ![malcolmlewis](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/malcolmlewis/32/11375_2.png) [@malcolmlewis](https://forums.suse.com/u/malcolmlewis)\ **Post date:** [July 23, 2018, 6:21am UTC](https://forums.suse.com/t/digest-verification-errors-for-package-hub-on-system-install/32714/4 "2018-07-23T06:21:55Z")
> [@](#): > > On Mon 23 Jul 2018 02:44:01 AM CDT, fusion809 wrote: > > How do I do that, re-adding Package Hub, that is? I removed the three > Package Hub repos with zypper. Then I looked up Package Hub repo in the > hope I’d have a nice zypper ar … command but I found > [https://packagehub.suse.com/](https://packagehub.suse.com/). It followed the “More…” link to > [https://packagehub.suse.com/how-to-use/](https://packagehub.suse.com/how-to-use/) and I went for the only > command-line option I saw, “Enabling with SUSEConnect”, so I ran: > > ## Code: > > SUSEConnect -p PackageHub/15.0/x86\_64 > > * * * > > and it seems I’m back to where I was before with these packages with > digest verification errors. Hi Yes, it would appear something is out of sync, could be a rebuild happening, see how it is tomorrow and if keeps happening will ping my SUSE contacts to see what may be up with PackageHub. – Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890) SLES 15 | GNOME Shell 3.26.2 | 4.12.14-23-default If you find this post helpful and are logged into the web interface, please show your appreciation and click on the star below… Thanks! ---
**Author:** ![christianm](https://avatars.discourse-cdn.com/v4/letter/c/2acd7d/32.png) [@christianm](https://forums.suse.com/u/christianm)\ **Post date:** [July 23, 2018, 3:32pm UTC](https://forums.suse.com/t/digest-verification-errors-for-package-hub-on-system-install/32714/5 "2018-07-23T15:32:04Z")
Hi! The problem persists. I tried two fresh server setups in the last few hours. Both failed with digest verification errors. Christian ---
**Author:** ![cisaksen](https://avatars.discourse-cdn.com/v4/letter/c/49beb7/32.png) [@cisaksen](https://forums.suse.com/u/cisaksen)\ **Post date:** [July 24, 2018, 5:11pm UTC](https://forums.suse.com/t/digest-verification-errors-for-package-hub-on-system-install/32714/6 "2018-07-24T17:11:58Z")
Getting the same errors on multiple packages on a fresh CD - Repo Install. Trying to install the X-sever version rather than the minimal install that the CD alone provides. Wish they would they would create a DVD with everything in it as before. That and make the install work with SUSE Manager as the registration server. ---
**Author:** ![malcolmlewis](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/malcolmlewis/32/11375_2.png) [@malcolmlewis](https://forums.suse.com/u/malcolmlewis)\ **Post date:** [July 25, 2018, 6:53pm UTC](https://forums.suse.com/t/digest-verification-errors-for-package-hub-on-system-install/32714/7 "2018-07-25T18:53:49Z")
Hi All Should be all fixed now… enjoy 😉 – Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890) SLES 15 | GNOME Shell 3.26.2 | 4.12.14-23-default If you find this post helpful and are logged into the web interface, please show your appreciation and click on the star below… Thanks! ---
**Author:** ![Ismail](https://avatars.discourse-cdn.com/v4/letter/i/779978/32.png) [@Ismail](https://forums.suse.com/u/Ismail)\ **Post date:** [July 26, 2018, 2:17pm UTC](https://forums.suse.com/t/digest-verification-errors-for-package-hub-on-system-install/32714/8 "2018-07-26T14:17:58Z")
Hi all, Package Hub developer here. We have a problem with noarch packages which we are still figuring out on fixing, but for now it’s perfectly safe to ignore the checksum errors. Thanks, Ismail Dönmez ---
**Author:** ![Ismail](https://avatars.discourse-cdn.com/v4/letter/i/779978/32.png) [@Ismail](https://forums.suse.com/u/Ismail)\ **Post date:** [August 2, 2018, 11:14pm UTC](https://forums.suse.com/t/digest-verification-errors-for-package-hub-on-system-install/32714/9 "2018-08-02T23:14:32Z")
This is now fixed, thanks for your patience!