Bug 103253 - compat-gcc-g77 update to 7.3-2.96.121 is missing
Summary: compat-gcc-g77 update to 7.3-2.96.121 is missing
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: compat-gcc (Show other bugs)
(Show other bugs)
Version: 3.0
Hardware: All Linux
medium
medium
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact:
URL:
Whiteboard:
Keywords:
: 103574 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-08-28 07:12 UTC by Bernd Bartmann
Modified: 2007-11-30 22:06 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-08-28 18:37:36 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Bernd Bartmann 2003-08-28 07:12:45 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624

Description of problem:
When running up2date this morning I was presented with a lot of compat-gcc-*
updates. I selected all to be installed and got this message from up2date:

There was a package dependency problem. The message was:

Unresovable chain of dependencies:
compat-gcc-g77-7.3-2.96.119 requires compat-gcc = 7.3-2.96.119

Please modify your package selections and try again.


So to me this looks like there is simply the update to compat-g77-7.3-2.96.121
missing.

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


How reproducible:
Always

Steps to Reproduce:
1. use up2date to update to the latest compat-gcc-* packages
2.
3.
    

Additional info:

Comment 1 Bill Nottingham 2003-08-28 18:37:36 UTC
compat-gcc-g77 was erroneously included before. You'll need to remove it to
upgrade to current packages.

Comment 2 Bill Nottingham 2003-09-02 18:05:46 UTC
*** Bug 103574 has been marked as a duplicate of this bug. ***


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