You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# dnf info fluent-package
Last metadata expiration check: 0:00:04 ago on Tue Apr 22 00:02:42 2025.
Installed Packages
Name : fluent-package
Version : 5.0.6
Release : 1.el9
Architecture : x86_64
Size : 66 M
Source : fluent-package-5.0.6-1.el9.src.rpm
Repository : @System
From repo : fluent-package-lts
Summary : All in one package of Fluentd
URL : https://docs.fluentd.org/
License : ASL 2.0
Description : The stable distribution of Fluentd, formerly known as td-agent.
# rpm -q --qf '%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH} => GPG: %{SIGGPG:pgpsig}\n' fluent-package
fluent-package-5.0.6-1.el9.x86_64 => GPG: (none)
The package is not signed at all.
GPG key at https://packages.treasuredata.com/GPG-KEY-fluent-package (0x43FA320E) is already installed
The GPG keys listed for the "fluentd" repository are already installed but they are not correct for this package.
Check that the correct key URLs are configured for this repository.. Failing package is: fluent-package-5.0.6-1.el9.x86_64
GPG Keys are configured as: https://packages.treasuredata.com/GPG-KEY-fluent-package
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'.
Error: GPG check FAILED
# ls
fluent-package-5.0.6-1.el9.x86_64.rpm
Describe the bug
Hello, the rpm is not signed.
Is it normal ?
To Reproduce
I installed the fluentd package using the repo
[fluent-package-lts]
name=Fluentd Project
baseurl=https://packages.treasuredata.com/lts/5/redhat/$releasever/$basearch
enabled=1
gpgcheck=1
gpgkey=https://packages.treasuredata.com/GPG-KEY-td-agent
https://packages.treasuredata.com/GPG-KEY-fluent-package
But after install
Expected behavior
The package should be signed.
Your Environment
Your Configuration
Rocky linux 9
Your Error Log
Additional context
No response
The text was updated successfully, but these errors were encountered: