Bug 22804 - up2date doesn't give reasons to update packages
Summary: up2date doesn't give reasons to update packages
Keywords:
Status: CLOSED DUPLICATE of bug 15647
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: up2date
Version: 7.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Preston Brown
QA Contact: Aaron Brown
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-12-24 09:55 UTC by David Woodhouse
Modified: 2007-04-18 16:30 UTC (History)
0 users

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2000-12-24 09:55:36 UTC
Embargoed:


Attachments (Terms of Use)

Description David Woodhouse 2000-12-24 09:55:34 UTC
up2date offered me a large number of errata this morning. No clue _why_
most of the packages have been updated, though. The RHAT web site didn't
even seem to have them listed yet.

It would be useful for up2date to be able to display the erratum release
notes for each package which it makes available for selection.

Perhaps up2date should also know that it shouldn't upgrade from a package
which isn't the original version shipped by Red Hat? If I install a custom
version of a package (e.g. OpenSSL uncrippled, or Helix GNOME) it should be
in up2date's Skip list by default unless I explicitly request it to be
updated.

Comment 1 Preston Brown 2000-12-27 21:56:59 UTC

*** This bug has been marked as a duplicate of 15647 ***


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