Strange happening with an update file(zypper up stuff in post)

English Applications
1

strange error forbids complete update.

The following 44 packages are going to be upgraded:
  avahi avahi-lang glib2-lang glib2-tools ImageMagick ImageMagick-config-7-SUSE joe kpartx libavahi-client3 libavahi-common3
  libavahi-core7 libavahi-glib1 libgio-2_0-0 libgirepository-2_0-0 libglib-2_0-0 libgmodule-2_0-0 libgobject-2_0-0
  libMagickCore-7_Q16HDRI10 libMagickWand-7_Q16HDRI10 libmariadb3 libmpath0 libpackagekit-glib2-18 libzypp multipath-tools net-tools
  net-tools-lang PackageKit PackageKit-backend-zypp PackageKit-gstreamer-plugin PackageKit-gtk3-module PackageKit-lang perl perl-base
  perl-HTTP-Date pesign pesign-systemd python313-urllib3 shim typelib-1_0-Gio-2_0 typelib-1_0-GLib-2_0 typelib-1_0-GModule-2_0
  typelib-1_0-GObject-2_0 typelib-1_0-PackageKitGlib-1_0 wpa_supplicant

44 packages to upgrade.

Package download size:
              |      29.4 MiB  overall package size
   144.8 KiB  |  -   29.2 MiB  already in cache

Package install size change:
              |     105.2 MiB  required by packages that will be installed
    62.4 KiB  |  -  105.2 MiB  released by packages that will be removed

Backend:  classic_rpmtrans
Continue? [y/n/v/...? shows all options] (y): 
Preloading: pesign-116-160000.3.1.x86_64.rpm [done]
Preload finished. [success (12.7 KiB/s) ] .........................................................................................[done]
In cache ImageMagick-config-7-SUSE-7.1.2.0-160000.13.1.noarch.rpm                                                   (1/44), 178.6 KiB    
In cache joe-4.6-160000.4.1.x86_64.rpm                                                                              (2/44), 558.6 KiB    
In cache kpartx-0.12.3~1+272+suse.c377867-160000.1.1.x86_64.rpm                                                     (3/44), 153.2 KiB    
In cache libavahi-common3-0.8-160000.6.1.x86_64.rpm                                                                 (4/44),  72.2 KiB    
In cache libglib-2_0-0-2.84.4-160000.4.1.x86_64.rpm                                                                 (5/44), 983.2 KiB    
In cache libmariadb3-3.4.9-160000.1.1.x86_64.rpm                                                                    (6/44), 160.0 KiB    
In cache net-tools-2.10-160000.4.1.x86_64.rpm                                                                       (7/44),  73.0 KiB    
In cache perl-base-5.42.0-160000.3.1.x86_64.rpm                                                                     (8/44),   1.7 MiB    
Retrieving: pesign-116-160000.3.1.x86_64 (repo-oss (16.0))                                                          (9/44), 144.8 KiB    
Retrieving: pesign-116-160000.3.1.x86_64.rpm .................................................................................[not found]
Retrieving: pesign-116-160000.3.1.x86_64.rpm .................................................................................[not found]
Retrieving: pesign-116-160000.3.1.x86_64.rpm .................................................................................[not found]
Retrieving: pesign-116-160000.3.1.x86_64.rpm .........................................................................[done (32.5 KiB/s)]

Warning: Digest verification failed for file 'pesign-116-160000.3.1.x86_64.rpm'
[/var/tmp/zypp.tmp/AP_0xA0hGJM/x86_64/pesign-116-160000.3.1.x86_64.rpm]

  expected 4663c10a09dceed915da826598cab99a0613b48a6c7084eaa565fd61865646c1604f4e5f0f32d2b05c56e93135e7295934a5b8c22772731f2f47e1489681b77a
  but got  551f70bf6e76995d216ded024747445504a286351ff220c7c69ae2229242405d39fdaef016abfcce9e810e3ef39ad7e279702eddb36f6c8f33d6f827045d2a99

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 '551f..' 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? [551f/...? shows all options] (discard): 
Package pesign-116-160000.3.1.x86_64 (repo-oss (16.0)) seems to be corrupted during transfer. Do you want to retry retrieval?
Abort, retry, ignore? [a/r/i] (a): i
In cache pesign-systemd-116-160000.3.1.noarch.rpm                                                                  (10/44),  23.9 KiB    
In cache python313-urllib3-2.5.0-160000.7.1.noarch.rpm                                                             (11/44), 320.0 KiB    
In cache shim-16.1-160000.2.1.x86_64.rpm                                                                           (12/44), 554.9 KiB    
In cache wpa_supplicant-2.11-160000.4.1.x86_64.rpm                                                                 (13/44),   1.9 MiB    
In cache libmpath0-0.12.3~1+272+suse.c377867-160000.1.1.x86_64.rpm                                                 (14/44), 370.4 KiB    
In cache multipath-tools-0.12.3~1+272+suse.c377867-160000.1.1.x86_64.rpm                                           (15/44), 273.5 KiB    
In cache libavahi-core7-0.8-160000.6.1.x86_64.rpm                                                                  (16/44), 135.9 KiB    
In cache libavahi-client3-0.8-160000.6.1.x86_64.rpm                                                                (17/44),  75.5 KiB    
In cache libzypp-17.38.14-160000.1.1.x86_64.rpm                                                                    (18/44),   3.0 MiB    
In cache libgobject-2_0-0-2.84.4-160000.4.1.x86_64.rpm                                                             (19/44), 450.2 KiB    
In cache libgmodule-2_0-0-2.84.4-160000.4.1.x86_64.rpm                                                             (20/44), 319.2 KiB    
In cache libavahi-glib1-0.8-160000.6.1.x86_64.rpm                                                                  (21/44),  57.0 KiB    
In cache glib2-lang-2.84.4-160000.4.1.noarch.rpm                                                                   (22/44),   1.5 MiB    
In cache net-tools-lang-2.10-160000.4.1.noarch.rpm                                                                 (23/44),  80.5 KiB    
In cache perl-5.42.0-160000.3.1.x86_64.rpm                                                                         (24/44),   8.3 MiB    
In cache avahi-0.8-160000.6.1.x86_64.rpm                                                                           (25/44), 165.0 KiB    
In cache typelib-1_0-GLib-2_0-2.84.4-160000.4.1.x86_64.rpm                                                         (26/44), 365.2 KiB    
In cache libMagickCore-7_Q16HDRI10-7.1.2.0-160000.13.1.x86_64.rpm                                                  (27/44),   2.1 MiB    
In cache libMagickWand-7_Q16HDRI10-7.1.2.0-160000.13.1.x86_64.rpm                                                  (28/44), 506.5 KiB    
In cache ImageMagick-7.1.2.0-160000.13.1.x86_64.rpm                                                                (29/44), 273.5 KiB    
In cache libgirepository-2_0-0-2.84.4-160000.4.1.x86_64.rpm                                                        (30/44), 395.8 KiB    
In cache libgio-2_0-0-2.84.4-160000.4.1.x86_64.rpm                                                                 (31/44), 964.4 KiB    
In cache glib2-tools-2.84.4-160000.4.1.x86_64.rpm                                                                  (32/44), 424.6 KiB    
In cache perl-HTTP-Date-6.06-160000.3.1.noarch.rpm                                                                 (33/44),  29.1 KiB    
In cache avahi-lang-0.8-160000.6.1.noarch.rpm                                                                      (34/44), 151.0 KiB    
In cache typelib-1_0-GObject-2_0-2.84.4-160000.4.1.x86_64.rpm                                                      (35/44), 320.9 KiB    
In cache typelib-1_0-GModule-2_0-2.84.4-160000.4.1.x86_64.rpm                                                      (36/44), 305.4 KiB    
In cache libpackagekit-glib2-18-1.2.8-160000.5.1.x86_64.rpm                                                        (37/44), 278.7 KiB    
In cache PackageKit-backend-zypp-1.2.8-160000.5.1.x86_64.rpm                                                       (38/44), 256.0 KiB    
In cache PackageKit-1.2.8-160000.5.1.x86_64.rpm                                                                    (39/44), 478.3 KiB    
In cache typelib-1_0-Gio-2_0-2.84.4-160000.4.1.x86_64.rpm                                                          (40/44), 393.1 KiB    
In cache PackageKit-lang-1.2.8-160000.5.1.noarch.rpm                                                               (41/44), 390.4 KiB    
In cache PackageKit-gtk3-module-1.2.8-160000.5.1.x86_64.rpm                                                        (42/44), 162.7 KiB    
In cache PackageKit-gstreamer-plugin-1.2.8-160000.5.1.x86_64.rpm                                                   (43/44), 163.8 KiB    
In cache typelib-1_0-PackageKitGlib-1_0-1.2.8-160000.5.1.x86_64.rpm                                                (44/44), 179.2 KiB    
Installation has completed with error.
1 Like
2

I’ve occasionally had similar errors. You were probably downloading from a mirror that was not fully synchronized.

Try again tomorrow.

1 Like
3

'K Thanks. will try again.
But I just don’t know about those 3 ‘NOT FOUND’ pesign-116 things

4

This is how that looks with some spacing removed.

What is happening here is that a package can not be found on the first selected mirror, then a second is tried, also not found, the a third also not found and finally the fourth has it but when verifying it’s signature it is not good.

Like @nrickert wrote, just try later so the mirrors can sync up.

5

same happened to me. will try again tomorrow :slight_smile:

6

seems i got the good mirrors this time, worked out fine now.

7

I’m getting essentially the same message via the GUI updater. Waited a day, but still the same issue. Might try updating via the command line instead.

1 Like
8

Hello and welcome the openSUSE forums.

Please do not assume other people have the same workflow and/or way to do things as you have. Call things by name and not this generic term. Was it Myrlyn? Something else?

1 Like
9

It appears that the US mirror is still out of date. I selected another mirror and got a file with the correct checksum:
https://download.opensuse.org/distribution/leap/16.0/repo/oss/x86_64/pesign-116-160000.3.1.x86_64.rpm.mirrorlist

1 Like
10

got everthing in EXCEPT the ‘pesign’ files. Still blasting me an error for 2 files.
@oliviercalle, how did you find and select that mirror that worked for you?

11

Never mind my brain fog! I found it and used Discover to install it. Will see if other problems show up. THANKS ALL!

12

OK, no zypper failures, but a ‘zypper up’ indicates a patch is available, but it doesn’t show up in myrlyn.

localhost:~ # zypper up
Refreshing service 'openSUSE'.
Loading repository data...
Reading installed packages...

The following item is locked and will not be changed by any action:
 Available:
  patch:openSUSE-Leap-16.0-408
Nothing to do.
13

It is locked, why should Myrlyn bother you with it?

14

Don’t understand. How is it locked?

15

Well, I was informed this thread is marked Solved, but … it can be Locked for any number of reasons. (it’s usually the user that locks a package(s) ).

Might want to run the zypper with more feedback, such as:

# zypper -vvv up

See if that reveals anything. Might check Myrlyn and click around.

16

In myrlyn, try going to View > Patches and change the Show Patch Category to All Patches. Then find the Security update for protobuf and check if it’s marked as Taboo.

17

Okay, just double-checked the documentation … packages are locked by the user | Admin … no automagical locking is done by the system | zypper | Myrlyn.

18

that patch was part of the ‘strange happenings’ is wht I put it here. Sorry my bad.
to put it to an end, ;‘zypper ll’ showed it as a locked patch. I unlocked it. Did a ‘zypper patch (name of patch)’ and it came back as alreasy installed! STRANGE??

So, a moderater can lock this thread, or let it die a long death.

19

No this is not strange, man zypper can tell you:

Package Locks Management
Package locks serve the purpose of preventing changes to the set of installed packages on the system. Locks are stored as queries in /etc/zypp/locks file (see also locks(5)). Packages matching a query are then forbidden to change their installed status; an installed package can’t be removed or upgraded, not installed package can’t be installed. When requesting to install, upgrade or remove such locked package, you will get a dependency problem dialog.

So AFAIK you can only lock a package that is installed.

20

In your quote is:

So you can lock a package to prevent it from installing (e.g. because it is otherwise “recommended”).

boven:~ # zypper se plymouth
Loading repository data...
Reading installed packages...

I have e.g.

S  | Name                          | Summary                                                            | Type
---+-------------------------------+--------------------------------------------------------------------+--------
   | blog-plymouth                 | Replaces plymouth by blogd                                         | package
 l | plymouth                      | Graphical Boot Animation and Logger                                | package
 l | plymouth-branding-openSUSE    | openSUSE Leap 16.0 branding for Plymouth bootsplash                | package
 l | plymouth-branding-upstream    | Default configuration file and branding from the Plymouth upstream | package
 l | plymouth-devel                | Libraries and headers for writing Plymouth splash plugins          | package
...
...

Plymout his not installed and locked.