Bug 68712 - up2date fails, complains that squid package is corrupt
Summary: up2date fails, complains that squid package is corrupt
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: squid
Version: 6.2
Hardware: alpha
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-07-12 18:49 UTC by Brian Brock
Modified: 2014-03-17 02:28 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2002-07-12 18:49:54 UTC
Embargoed:


Attachments (Terms of Use)

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.


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