Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 68712 - up2date fails, complains that squid package is corrupt
up2date fails, complains that squid package is corrupt
Product: Red Hat Linux
Classification: Retired
Component: squid (Show other bugs)
alpha Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Depends On:
  Show dependency treegraph
Reported: 2002-07-12 14:49 EDT by Brian Brock
Modified: 2014-03-16 22:28 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-07-12 14:49:54 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Brian Brock 2002-07-12 14:49:49 EDT
Description of Problem:
running `up2date --nox -u` on a 6.2 alpha system, all other errata applied, I
recieve the following error:

Retrieving selected packages...
squid-2.4.STABLE6-6.6.2.alp ########################## Done.                   

************ GPG VERIFICATION ERROR ****************
The package squid-2.4.STABLE6-6.6.2 failed its gpg signature verification. This
means the package is corrupt.

Version-Release number of selected component (if applicable):


squid-2.4.STABLE6-6.6.2 (apparently the rpm db thinks the new squid package is

How Reproducible:
still working, will update this bug in a few moments.

Steps to Reproduce:
1. Install (full) 6.2 on an Alpha machine, up2date everything but the squid packages
2. run `up2date --nox -u` and observe output
[ results I recieved are posted above ]

Expected Results:
successful update.

Additional Information:
sparc and i386 under the closest possible configuration do not report any error,
and successfully update squid.	
Other releases have not yet been tested.
Comment 1 Brian Brock 2002-07-12 15:06:39 EDT
ugh, nevermind, user (me) error.

I had two parallel up2date instances running on the box, and mistakenly thought
that the successful instance was running on another box.

Note You need to log in before you can comment on or make changes to this bug.