bilelmoussaoui / bilelmoussaoui/Hardcode-Tray
Error: GPG verification FAILED
- Dominant language
- Python
- Stars
- 890
- Forks
- 59
- PR merge metrics
- No merged PRs in 30d
Description
**Fedora 38**
Good afternoon, I receive an error when validating the key. Can you tell me why this is happening?
I do everything as described in the [repository](https://github.com/bilelmoussaoui/Hardcode-Tray#fedora-30--fedora-rawhide)
```
....
Continue? [y/n]: y
Download packages:
[SKIPPED] librsvg2-tools-2.56.3-1.fc38.x86_64.rpm: Already downloaded
[SKIPPED] hardcode-tray-4.3.r246.g1d52b2c-121.1.noarch.rpm: Already downloaded
Hardcode-Tray (Fedora_38) 4.5 kB/s | 1.1 kB 00:00
Import GPG key 0x6F964FF6:
User ID: "home:SmartFinn OBS Project "
Fingerprint: 1C53 DA14 5523 86F4 E329 7330 B3C0 397E 6F96 4FF6
Source: https://download.opensuse.org/repositories/home:/SmartFinn:/hardcode-tray/Fedora_38/repodata/repomd.xml.key
Continue? [y/n]: y
error: Certificate B3C0397E6F964FF6:
The certificate is expired: The primary key is not live
Key import failure (code 2). Failing package: hardcode-tray-4.3.r246.g1d52b2c-121.1.noarch
GPG keys are configured as: https://download.opensuse.org/repositories/home:/SmartFinn:/hardcode-tray/Fedora_38/repodata/repomd.xml.key
The downloaded packages were stored in cache until the next successful transaction.
You can remove cached packages by running "dnf clean packages".
Error: GPG verification FAILED
[morington@fedora yum.repos.d]$
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the Fedora 38 installation instructions in the linked repository and reproduce the reported transaction using the commands and output in this issue. Check whether the repository key-validation failure is still reproducible on Fedora 38. Done means the cause is identified and the installation either verifies successfully or the limitation is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- operating-systems, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100