Bug 49409

Summary:	Can't tell what "rpm --freshen *.rpm" will do
Product:	[Retired] Red Hat Linux	Reporter:	Karl O. Pinc <kop>
Component:	rpm	Assignee:	Jeff Johnson <jbj>
Status:	CLOSED WORKSFORME	QA Contact:	David Lawrence <dkl>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.1	Keywords:	FutureFeature
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2001-07-20 00:02:35 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 Karl O. Pinc 2001-07-19 07:34:18 UTC

Description of Problem:

There is no way to test for which packages will be upgraded by --freshen. 
This greatly reduces the utility of --freshen because you can't tell if
you're going to get into something complicated, as when a complex config
file is upgraded and you need to be sure your config and the new software
are in sync, or something dangerous, like a upgrade to the kernel.  This is
especially significant when trying to apply the updates from RedHat, as
lots of update rpms wind up in one directory.

I'd like some combination of -v --freshen and --test to provide clues as to
what's going to happen.  Or at least what packages are going to be
freshened.

Comment 1 Jeff Johnson 2001-07-19 21:16:46 UTC

Try
	rpm -Fvv --test --noscripts --notriggers ...
The output is copious, but complete. (And, AFAIK, --noscripts
and --notriggers are implied by --test, but Just In Case ...)

Comment 2 Karl O. Pinc 2001-07-20 00:02:30 UTC

I'll grant that -Fvv is acceptable if you'll commit to a particular script,
like:

rpm -Fvv --test --noscripts --notriggers *.rpm 2>&1 | grep '^D: package: ' | cut
-d ' ' -f 3

which will _allways_ produce the list of new packages to be installed.  If you
won't commit, I stick by my claim that "There is no way to test for which
packages will be upgraded by --freshen."

(I wouldn't take the bait if I were you...  :-)

Comment 3 Jeff Johnson 2001-07-24 17:12:26 UTC

I'll commit to a relatively simple, deterministic way of identifying
what packages are gonna be installed, but I reserve the right to
change the "D: package:" string if I need to. How's that? :-)