Bug 15647 – up2date should explain reason for update

Bug 15647 - up2date should explain reason for update

Summary:	up2date should explain reason for update

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	up2date (Show other bugs)
Sub Component:
Version:	6.2
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Preston Brown
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:	FutureFeature

Duplicates:	22804 (view as bug list)
Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2000-08-07 11:13 EDT by d-mueth
Modified:	2008-05-01 11:37 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Enhancement
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2001-03-01 15:50:05 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description d-mueth 2000-08-07 11:13:12 EDT

Right now, up2date gives a description of each package which can be
updated.  What is really of interest is why the package was updated - bug
fixes, enhancements, or security
fixes.

I am mainly concerned with just patching security holes, as I imagine many
people are.  It would be very nice if up2date described either:
   1) A description of the reason for the update
and/or,
   2) A symbol designating which updates are security-related.

Dan

Comment 1 Preston Brown 2000-12-27 16:56:56 EST

*** Bug 22804 has been marked as a duplicate of this bug. ***

Comment 2 Preston Brown 2001-03-01 15:50:01 EST

added in CVS.

Comment 3 Preston Brown 2001-04-12 16:55:19 EDT

functionality available in errata due out today.

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