Bug 1216152

Summary:	Warning: Digest verification failed for file 'libplacebo264-5.264.1-1.3.x86_64.rpm'
Product:	[openSUSE] openSUSE Tumbleweed	Reporter:	John Shand <jshand2013>
Component:	Other	Assignee:	llyyr <llyyr.public>
Status:	RESOLVED WORKSFORME	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	jshand2013
Version:	Current
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	y2logs 1 y2logs 2 y2logs 3

Description John Shand 2023-10-11 19:18:16 UTC

Retrieving: libplacebo264-5.264.1-1.3.x86_64 (openSUSE-20230519-0)                                   (3/7), 375.5 KiB    
Retrieving: libplacebo264-5.264.1-1.3.x86_64.rpm ....................................................[done (104.6 KiB/s)]

Warning: Digest verification failed for file 'libplacebo264-5.264.1-1.3.x86_64.rpm'
[/var/tmp/AP_0xczsFOm/x86_64/libplacebo264-5.264.1-1.3.x86_64.rpm]

  expected f2e6aa5c0b41f54ffa2dc7761163812d89fd55bbf5d5c503e4e3b2bb0b0989580dfa3baee6eca2682506645f73a816def1c88024a88127d2bd7616a0feac431d
  but got  dc7054984c9f2754f00dd8cc58e17b180f928b2b11c620bf5601a7ba2f8cce852671f99090446903b43ab00a0fded1039b45a7dbc63fef0a49d6325062a03d8e

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 'dc70..' 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? [dc70/...? shows all options] (discard):

Comment 1 John Shand 2023-10-11 20:26:55 UTC

Created attachment 870108 [details]
y2logs 1

Comment 2 John Shand 2023-10-11 20:27:28 UTC

Created attachment 870109 [details]
y2logs 2

Comment 3 John Shand 2023-10-11 20:28:08 UTC

Created attachment 870110 [details]
y2logs 3

Comment 4 llyyr 2023-10-23 05:02:47 UTC

This is almost certainly an issue with openSUSE mirrors, there's nothing I can do from my end to cause this and the package has never been changed since it was first added. Also works for me.

Comment 5 John Shand 2023-10-23 05:19:27 UTC

this is no longer an issues as the package no longer has this issue even if nothing changed.  the mirror(s) must have self-corrected