So I’ve been trying to run Updates from Discover. For the System Upgrade, I’ve been getting:
GPG failure:
For
repo /var/tmp/zypp.tmp/AP_0xNPAHX7/noarch/
lensfun-data-0.3.4-bp160.2.12.noarch.rpm
c867bfd03b9676cbe945141421171ab173a583d3f5fd3c19662b4ef40e95c7b4174b00d997cc
7074a6176252e591522a98854a48ac82844c8641ed39f0bc5011 is requested but
cb3ce646fb9c022ce668e31108163efbab86b09b850967d860b7ef723a3a2e3a0e07184944
db7259783f3d24f1db7cfe3e8efbfe2a15bc8e6b3b882eadd06117 was found!
tharpa:
I asked Google Gemini to comment on this and I offer it for your consideration, but this is strictly a use at your own risk category.
I asked Gemini:
can you make heads or tails of this message?
So I’ve been trying to run Updates from Discover. For the System Upgrade, I’ve been getting:
GPG failure:
For
repo /var/tmp/zypp.tmp/AP_0xNPAHX7/noarch/
lensfun-data-0.3.4-bp160.2.12.noarch.rpm
c867bfd03b9676cbe945141421171ab173a583d3f5fd3c19662b4ef40e95c7b4174b00d997cc
7074a6176252e591522a98854a48ac82844c8641ed39f0bc5011 is requested but
cb3ce646fb9c022ce668e31108163efbab86b09b850967d860b7ef723a3a2e3a0e07184944
db7259783f3d24f1db7cfe3e8efbfe2a15bc8e6b3b882eadd06117 was found!
Yep, this is a classic case of a **checksum mismatch** (packaged inside a GPG failure warning) during an openSUSE system upgrade.
Here is exactly what's happening and how to fix it.
## The Breakdown
When openSUSE downloads a package, it checks a security manifest to see what the file *should* look like.
* **What it wanted:** A file matching the hash starting with `c867bf...`
* **What it actually got:** A file matching the hash starting with `cb3ce6...`
Because the hashes don't match, your system safely refuses to install it, fearing the package might be corrupted or tampered with.
### Why did this happen?
99% of the time, this isn't a hacker attack. It's usually one of two things:
1. **Outdated Repository Metadata:** The mirror you are downloading from updated the package, but your local system is still looking at an older list (or vice versa).
2. **A Bad Mirror:** The specific download server your system hit has a corrupted cache.
## How to Fix It
Discover (the graphical software center) can sometimes get stuck in a loop with these errors. The most reliable way to clear this up is to force a refresh using the terminal (`zypper`).
Open your terminal and run the following commands:
### 1. Clean and Refresh the Repositories
This forces your system to dump its old package lists and grab fresh, matching manifests from the servers.
`Bashsudo zypper clean -a
sudo zypper ref`
### 2. Run the Upgrade via Terminal
Instead of using Discover, try running the distribution upgrade directly in the terminal. It handles these conflicts much more gracefully and will give you clear prompts if something goes wrong.
`Bashsudo zypper dup`
### What to do if it fails again:
If `zypper` still complains about `lensfun-data`, it means the server you are hitting is genuinely broken at the moment. You have two choices:
* **Wait a few hours:** The mirror will usually sync up and fix itself.
* **Temporarily ignore it:** When `zypper dup` asks you if you want to (i)gnore, (r)etry, or (a)bort, typing `i` for ignore will skip this specific data package for now and let the rest of your system upgrade smoothly.
Did forcing the refresh with `zypper` get the upgrade moving for you?
I believe that some helpful information is here. Sooner or later all of us are going to have to recognize that AI is here to stay, whether or not we like it. The hard part is sifting out the good advice from AI, versus the misleading fluff. All I can say is that let experience be your guide.
- Randall
No AI needed for such standard messages.
And the AI output is plain wrong. You don‘t use zypper dup on Leap but zypper up.
I wonder where that package is coming from, here I see
S | Name | Type | Version | Arch | Repository
---+--------------+---------+-----------------+--------+----------------
| lensfun-data | package | 0.3.4-bp160.1.1 | noarch | repo-oss (16.0)
Please post zypper se -s lensfun-data and zypper lr -d
There is such a version for SLE16 in the Backports:/SLE-16.0 repo and the package itself is fine:
bruno@LT-B:~/Downloads> rpmkeys -v --checksig lensfun-data-0.3.4-bp160.2.12.noarch.rpm
lensfun-data-0.3.4-bp160.2.12.noarch.rpm:
Header V3 RSA/SHA512 Signature, key ID 287a0027: OK
Header SHA256 digest: OK
Header SHA1 digest: OK
Payload SHA256 digest: OK
V3 RSA/SHA512 Signature, key ID 287a0027: OK
MD5 digest: OK
bruno@LT-B:~/Downloads>
So bad mirror, or flaky internet or???
Anyway there is no reason to install that version on Leap 16.0.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.