Bug 386221

Summary:	netpbm packaging affects updates
Product:	[Fedora] Fedora	Reporter:	Michal Jaegermann <michal>
Component:	netpbm	Assignee:	Jindrich Novy <jnovy>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	8	CC:	pknirsch
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-11-16 13:22:57 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 Michal Jaegermann 2007-11-16 03:27:11 UTC

Description of problem:

Fedora 8 comes with the following packages:

netpbm-10.35-17.fc8
netpbm-devel-10.35-17.fc8
netpbm-progs-10.35-17.fc8

but if one tries to update a current FC6 installation then
packages present are

netpbm-10.35.32-1.fc6
netpbm-devel-10.35.32-1.fc6
netpbm-progs-10.35.32-1.fc6

and the care coming up as "newer" (as an epoch obviously was
not bumped up).  To replace them with F8 packages one has to
use 'rpm --oldpackage -Uvh netpbm*f8*.rpm'.

One is left with "orphans" does not matter if an update was
run with a help of anaconda or with 'yum update'.

Comment 1 Michal Jaegermann 2007-11-16 03:27:54 UTC

Oh, I believe that updating from F7 gets into the same predicament.

Comment 2 Jindrich Novy 2007-11-16 13:22:57 UTC

Yes, the update to f8 was not yet pushed. It will be pushed shortly. Thanks for
noticing.