Bug 585912 - f13 upgrade error due to missing gio-querymodules-32
Summary: f13 upgrade error due to missing gio-querymodules-32
Alias: None
Product: Fedora
Classification: Fedora
Component: gvfs
Version: 13
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
: 592889 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2010-04-26 11:57 UTC by Mads Kiilerich
Modified: 2015-03-03 22:47 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2011-06-27 15:53:07 UTC
Type: ---

Attachments (Terms of Use)

Description Mads Kiilerich 2010-04-26 11:57:01 UTC
When upgrading from f12 to f13 I got 

  Updating       : gvfs-1.6.0-1.fc13.i686                     49/423 
Non-fatal POSTIN scriptlet failure in rpm package gvfs-1.6.0-1.fc13.i686
/var/tmp/rpm-tmp.MnyZ8l: line 11: /usr/bin/gio-querymodules-32: No such file or directory
warning: %post(gvfs-1.6.0-1.fc13.i686) scriptlet failed, exit status 127

gvfs-1.6.0-1.fc13.i686 requires libglib-2.0.so.0 and %post runs /usr/bin/gio-querymodules-32.

glib2-2.24.0-1.fc13.i686 contains /lib/libglib-2.0.so.0 and /usr/bin/gio-querymodules-32.

glib2-2.22.5-1.fc12.i686 do however not contain gio-querymodules-32.

AFAICS gvfs-1.6.0 should require(post) glib2 >= 2.24.0 to get the packages installed in the right order.

Comment 1 Tomáš Bžatek 2010-04-26 14:19:22 UTC
From what I see in the gvfs spec file:

BuildRequires: glib2-devel >= 2.23.2

I would expect rpmbuild to come up with better require list. There's a lot of unversioned .so.0 libraries, to be on the safe side we would need to explicitly require certain version of our dependencies.

With glib2 < 2.23.4 things (gvfs) can't work properly.

Comment 2 Fedora Update System 2010-04-26 16:07:52 UTC
gvfs-1.6.1-2.fc13 has been submitted as an update for Fedora 13.

Comment 3 Fedora Update System 2010-04-27 05:50:26 UTC
gvfs-1.6.1-2.fc13 has been pushed to the Fedora 13 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 gvfs'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/gvfs-1.6.1-2.fc13

Comment 4 Tomáš Bžatek 2010-05-17 14:33:34 UTC
*** Bug 592889 has been marked as a duplicate of this bug. ***

Comment 5 Bug Zapper 2011-06-02 14:51:21 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 

Comment 6 Bug Zapper 2011-06-27 15:53:07 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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