Bug 452683 - libxcb upgrade path blocker
libxcb upgrade path blocker
Status: CLOSED CURRENTRELEASE
Product: Fedora
Classification: Fedora
Component: libxcb (Show other bugs)
8
All Linux
medium Severity high
: ---
: ---
Assigned To: Adam Jackson
Fedora Extras Quality Assurance
: EasyFix
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-06-24 09:58 EDT by Dmitry Butskoy
Modified: 2008-08-13 09:05 EDT (History)
2 users (show)

See Also:
Fixed In Version: 1.1-1.1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-08-13 09:05:17 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Dmitry Butskoy 2008-06-24 09:58:11 EDT
The latest libxcb in Fedora 8 is libxcb-1.0-4.fc8, whereas the latest version in
the previous release, Fedora 7, already was libxcb-1.1

This prevents normal upgrade form (already EOF'ed) Fedora 7 to Fedora 8

(Note, that some people, especialy in production environments, do not prefer to
upgrade to the Fedora 9, they prefer to upgrade to Fedora 8, as more stable
distro. Please, do not promote the idea to use Fedora 9 instead of fixing this
bug ;) )
Comment 1 Fedora Update System 2008-07-21 14:57:10 EDT
libxcb-1.1-1.fc8 has been submitted as an update for Fedora 8
Comment 2 Fedora Update System 2008-07-23 03:09:54 EDT
libxcb-1.1-1.fc8 has been pushed to the Fedora 8 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update libxcb'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F8/FEDORA-2008-6609
Comment 3 Tom Davidson 2008-07-26 19:43:57 EDT
1.1-1 reintroduces the locking issue at bug 390261 to F8. 

Perhaps the equivalent to fc9's 1.1-4 can be provided instead?
Comment 4 Tom Davidson 2008-08-01 01:12:32 EDT
The latest locking issue has been fixed by 1.1-1.1 (cf. bug 456824) -- Thanks Adam

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