Bug 68712

Summary: up2date fails, complains that squid package is corrupt
Product: [Retired] Red Hat Linux Reporter: Brian Brock <bbrock>
Component: squidAssignee: Bill Nottingham <notting>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2CC: rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: alpha   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2002-07-12 18:49:54 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 Brian Brock 2002-07-12 18:49:49 UTC
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):

up2date-2.7.61-6.x.1

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


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 19:06:39 UTC
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.