Mailinglist Archive: opensuse-bugs (4297 mails)

< Previous Next >
[Bug 1040616] New: Printing/ghostscript-fonts: Bug "Digest verification failed" ... wrong pkg chksums
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Wed, 24 May 2017 14:29:20 +0000
  • Message-id: <bug-1040616-21960@http.bugzilla.opensuse.org/>
http://bugzilla.opensuse.org/show_bug.cgi?id=1040616


Bug ID: 1040616
Summary: Printing/ghostscript-fonts: Bug "Digest verification
failed" ... wrong pkg chksums
Classification: openSUSE
Product: openSUSE.org
Version: unspecified
Hardware: All
OS: openSUSE 42.2
Status: NEW
Severity: Major
Priority: P5 - None
Component: 3rd party software
Assignee: jsmeix@xxxxxxxx
Reporter: pgnet.dev@xxxxxxxxx
QA Contact: opensuse-communityscreening@xxxxxxxxxxxxxxxxxxxxxx
CC: tchvatal@xxxxxxxx, werner@xxxxxxxx
Found By: ---
Blocker: ---

fyi, just in case this is NOT a transient repo issue,

zypper updating this morning,

...
Warning: Digest verification failed for file
'ghostscript-fonts-9.06-20.30.noarch.rpm'

[/var/cache/zypp/packages/Printing/noarch/ghostscript-fonts-9.06-20.30.noarch.rpm]

expected 3f38f6d3b38e26e8e23b6377ed8aeab2a29e17d07b99e551b7ae78f850127468
but got f3fe8674ad8f391eb3a27fabdf62d80c3c58110e0009918073afe224ac00179f

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 'f3fe..' 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? [f3fe/...? shows all options] (discard):
Package ghostscript-fonts-9.06-20.30.noarch (Printing) seems to be
corrupted during transfer. Do you want to retry retrieval?
Abort, retry, ignore? [a/r/i] (a):
...


True for all ghostscript-* pkgs from "Printing" repo.

Not currently cured by a

zypper clean --all; zypper ref

... which _usually_ takes cares of it. Hence, the rpt.

--
You are receiving this mail because:
You are on the CC list for the bug.
< Previous Next >
This Thread
  • No further messages