Bug 71150
Summary: | ftp-0.17-12.1.i386.rpm has no GPG signature | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 2.1 | Reporter: | Nick Strugnell <nstrug> |
Component: | ftp | Assignee: | wdovlrrw <brosenkr> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Ben Levenson <benl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 2.1 | CC: | bero, crunge, mihai.ibanescu, shillman |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-10-20 16:14:51 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Nick Strugnell
2002-08-09 12:00:48 UTC
Assigning to someone with access to the GPG key Wasn't the solution to rebuild this and go back through the errata process? This is still not fixed - I just had another customer on the phone saying that his up2date failed. This appears to have been fixed since the last comment in this bug, over a year ago. The ftp package in the most recent errata is version ftp-0.17-12.1.1, which does have a gpg signature: [shillman@firefly i386]$ rpm --checksig ftp-0.17-12.1.1.i386.rpm ftp-0.17-12.1.1.i386.rpm: sha1 md5 gpg OK |