http://bugzilla.opensuse.org/show_bug.cgi?id=1042877 http://bugzilla.opensuse.org/show_bug.cgi?id=1042877#c1 Andreas Stieger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |astieger@suse.com Component|Other |3rd party software Version|Leap 42.2 |unspecified Assignee|bnc-team-screening@forge.pr |ledest@gmail.com |ovo.novell.com | Product|openSUSE Distribution |openSUSE.org QA Contact|qa-bugs@suse.de |opensuse-communityscreening | |@forge.provo.novell.com --- Comment #1 from Andreas Stieger --- zypper is doing what it is supposed to be doing: Comparing expected checksums against calculated ones. The repository may be temporarily inconsistent, but this will self-correct when it is next published. Assigning to project maintainer. --- Comment #2 from John Vandenberg --- Note the same problem occurs for Tumbleweed https://gitlab.com/jayvdb/package_manager/builds/17984915 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1042877 http://bugzilla.opensuse.org/show_bug.cgi?id=1042877#c4 --- Comment #4 from John Vandenberg --- This has been fixed. (p.s. it is a docker, so it is already very clean ;-)) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1042877 http://bugzilla.opensuse.org/show_bug.cgi?id=1042877#c6 John Vandenberg changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- --- Comment #6 from John Vandenberg --- Occurring again Retrieving: go-1.8.3-1.1.x86_64.rpm [..................done (2.5 MiB/s)] Warning: Digest verification failed for file 'go-1.8.3-1.1.x86_64.rpm' [/var/cache/zypp/packages/home_Ledest_devel/x86_64/go-1.8.3-1.1.x86_64.rpm] expected c1e8d1f208dffd36b318c8829a076c21b6f94231cfbc6e35894e3c54561bc90f but got 581afdd0aeeeadad31b8f7a040900e7b30b32b6a161d3cd2d5975473884c6d8c 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 '581a..' 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? [581a/...? shows all options] (discard): discard Package go-1.8.3-1.1.x86_64 (home:Ledest:devel (openSUSE_Leap_42.2)) seems to be corrupted during transfer. Do you want to retry retrieval? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1042877 http://bugzilla.opensuse.org/show_bug.cgi?id=1042877#c8 --- Comment #8 from Andreas Stieger --- Or local broken cache. Either way this is doing that it is supposed to be doing: Refusing to install packages that fail digest verification. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1042877 http://bugzilla.opensuse.org/show_bug.cgi?id=1042877#c10 Andreas Stieger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |containers-bugowner@suse.de Summary|zypper digest verification |openSUSE docker images |failed for file |reference third party |'go-1.8.3-1.1.x86_64.rpm' |repository (zypper digest | |verification failed for | |file | |'go-1.8.3-1.1.x86_64.rpm') Flags| |needinfo?(containers-bugown | |er@suse.de) --- Comment #10 from Andreas Stieger --- Containers team, can you confirm that the openSUSE docker images reference home:Ledest:devel for go? And if so correct the situation? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1042877 http://bugzilla.opensuse.org/show_bug.cgi?id=1042877#c12 --- Comment #12 from Valentin Rothberg --- (In reply to Flavio Castelli from comment #11)

(In reply to Andreas Stieger from comment #10)

...

Containers team, can you confirm that the openSUSE docker images reference home:Ledest:devel for go? And if so correct the situation?

The openSUSE official images for Docker only reference the official openSUSE repositories:

# | Alias | Name | Enabled | GPG Check | Refresh --+----------------+----------------+---------+-----------+-------- 1 | non-oss | NON-OSS | Yes | ( p) Yes | Yes 2 | oss | OSS | Yes | ( p) Yes | Yes 3 | oss-update | OSS Update | Yes | ( p) Yes | Yes 4 | update-non-oss | Update Non-Oss | Yes | ( p) Yes | Yes

The home:Ledest:devel repository has been added by the user. I assume zypper is installing the "go" package from there because 1) go is not installed inside of the image and 2) the user repo has a more recent version of it.

I agree. The output of the gitlab job shows that the repository has been added on-top of the openSUSE images: $ zypper addrepo $REPOS_BASE/$CARGO_REPO/$RELEASE/$CARGO_REPO.repo Adding repository 'home:Ledest:devel (openSUSE_Leap_42.2)' [......done] Repository 'home:Ledest:devel (openSUSE_Leap_42.2)' successfully added

@valentin: could it be something similar with https://github.com/openSUSE/docker-containers/issues/57 ?

They look similar, but issue #57 doesn't add another repository. -- You are receiving this mail because: You are on the CC list for the bug.