Bug 446238 – CUPS version blocks upgrade from F8 to F9

Bug 446238 - CUPS version blocks upgrade from F8 to F9

Summary:	CUPS version blocks upgrade from F8 to F9

Status:	CLOSED CANTFIX

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	cups (Show other bugs)
Sub Component:
Version:	9
Hardware:	All Linux

Priority	low Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	Tim Waugh
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2008-05-13 13:11 EDT by Chris Grau
Modified:	2008-05-14 04:09 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2008-05-14 04:09:28 EDT
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 Chris Grau 2008-05-13 13:11:15 EDT

Description of problem:

The CUPS version/release in F9 appears to be lower than that in F8.  This
prevents a Yum upgrade of the system.

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

In F8: 1:1.3.7-2.fc8
In F9: 1:1.3.7-1.fc9

How reproducible:

Always.

Steps to Reproduce:
1. Update fedora-release-*.noarch.rpm
2. Other steps from http://fedoraproject.org/wiki/YumUpgradeFaq
3. yum upgrade
  
Actual results:

Error: Missing Dependency: libldap-2.3.so.0 is needed by package cups

Additional info:

Removing cups should get the upgrade to work.  However, this also removes
several other packages.

Comment 1 bsquare 2008-05-13 15:07:53 EDT

Same problem with x86_64 architecture.

Comment 2 Tim Waugh 2008-05-14 04:09:28 EDT

Or you could undo the security fix that had to be made (by downgrading to
cups-1.3.7-1.fc8 or the F-8 shipped cups version), which was the reason for the
F-8 release number bump.

This sort of thing is always going to happen sooner or later; it's unfortunate
that a security issue caused this to happen sooner in this case.

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