Bug 583722 - eel2 upgrade errors, apparently for no good reason
Summary: eel2 upgrade errors, apparently for no good reason
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: nautilus
Version: 13
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-19 14:33 UTC by Mads Kiilerich
Modified: 2015-03-03 22:47 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-06-27 15:44:24 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Mads Kiilerich 2010-04-19 14:33:23 UTC
Description of problem:

On f12, trying to upgrade to f13 (sections without any references to eel2 removed):

# yum -v upgrade
Not loading "blacklist" plugin, as it is disabled
Loading "dellsysidplugin2" plugin
Loading "fastestmirror" plugin
Loading "merge-conf" plugin
Loading "presto" plugin
Loading "refresh-packagekit" plugin
Not loading "whiteout" plugin, as it is disabled
Config time: 0.508
Yum Version: 3.2.27
... 
[3 times:]
Checking deps for eel2.i686 0:2.26.0-2.fc12 - None
eel2-devel-2.26.0-2.fc12.i686 requires: libeel-2.so.2
--> Processing Dependency: libeel-2.so.2 for package: eel2-devel-2.26.0-2.fc12.i686
Needed Require is not a package name. Looking up: libeel-2.so.2
Potential Provider: eel2.i686 0:2.26.0-2.fc12
Mode is u for provider of libeel-2.so.2: eel2.i686 0:2.26.0-2.fc12
Mode for pkg providing libeel-2.so.2: u
Cannot find an update path for dep for: libeel-2.so.2
Searching pkgSack for dep: libeel-2.so.2
eel2-devel-2.26.0-2.fc12.i686 requires: eel2 = 2.26.0-2.fc12
--> Processing Dependency: eel2 = 2.26.0-2.fc12 for package: eel2-devel-2.26.0-2.fc12.i686
Potential Provider: eel2.i686 0:2.26.0-2.fc12
Mode is u for provider of eel2 = 2.26.0-2.fc12: eel2.i686 0:2.26.0-2.fc12
Mode for pkg providing eel2 = 2.26.0-2.fc12: u
Cannot find an update path for dep for: eel2 = 2.26.0-2.fc12
Searching pkgSack for dep: eel2
---> Package gstreamer-rtsp.i686 0:0.10.5-1.fc13 set to be updated
[end of 3 times]
...
--> Finished Dependency Resolution
Dependency Process ending
Depsolve time: 36.794
Error: Package: eel2-devel-2.26.0-2.fc12.i686 (@fedora/12)
           Requires: libeel-2.so.2
           Removing: eel2-2.26.0-2.fc12.i686 (@fedora-12/11)
Error: Package: eel2-devel-2.26.0-2.fc12.i686 (@fedora/12)
           Requires: eel2 = 2.26.0-2.fc12
           Removing: eel2-2.26.0-2.fc12.i686 (@fedora-12/11)
           Available: nautilus-2.30.0-1.fc13.i686 (fedora)
           Installing: nautilus-2.30.0-2.fc13.i686 (updates-testing)
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest


There is no eel2 in f13, so I would expect these packages to be left as orphans.

The "Error"s above are correct observations, but shouldn't be problems preventing the update.


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

yum-3.2.27-3.fc12.noarch
yum-presto-0.6.2-1.fc12.noarch
yum-plugin-fastestmirror-1.1.26-1.fc12.noarch
yum-utils-1.1.26-1.fc12.noarch
yum-plugin-merge-conf-1.1.26-1.fc12.noarch
yum-metadata-parser-1.1.2-14.fc12.i686
eel2-2.26.0-2.fc12.i686
eel2-devel-2.26.0-2.fc12.i686

Comment 1 James Antill 2010-04-19 15:54:29 UTC
> There is no eel2 in f13, so I would expect these packages to be left as
> orphans.

 It would be apart from:

% sudo repoquery --releasever=13 --obsoletes nautilus 
eel2 < eel2-2.26.0-3
[...]

...at a guess nautilus-devel should also be obsoleting eel2-devel.

Comment 2 Mads Kiilerich 2010-04-19 16:06:39 UTC
@yum-developers: Please consider adding a message that indicates that an obsoletion is part of the conflict.

Comment 3 Fedora Update System 2010-04-24 05:50:35 UTC
nautilus-2.30.0-3.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/nautilus-2.30.0-3.fc13

Comment 4 Fedora Update System 2010-04-25 13:46:16 UTC
nautilus-2.30.0-3.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 nautilus'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/nautilus-2.30.0-3.fc13

Comment 5 Bug Zapper 2011-06-02 15:05:57 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: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 6 Bug Zapper 2011-06-27 15:44:24 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.