Bug 912012 - depsolve errors after upgrade fc17 -> fc18
Summary: depsolve errors after upgrade fc17 -> fc18
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: yum
Version: 18
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Packaging Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 912039 912324 912360 912527 912692 912716 912999 913224 913397 913488 914813 914982 916376 917298 922526 923937 929369 946876 947077 947548 948061 948462 949300 950790 950791 953697 976496 978275 986946 998114 1001328 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-17 08:35 UTC by ramindeh
Modified: 2013-08-27 06:46 UTC (History)
34 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-02-19 07:18:32 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description ramindeh 2013-02-17 08:35:15 UTC
Description of problem:
When I do `yum update` after upgrade, I get the following depsolve errors:
Running Transaction Check
ERROR with transaction check vs depsolve:
httpd-mmn = 20051115-x86-64 is needed by (installed) mod_line_edit-1.0.0-8.fc17.x86_64
httpd-mmn = 20051115 is needed by (installed) mod_auth_pgsql-2.0.3-11.fc15.x86_64
httpd-mmn = 20051115 is needed by (installed) mod_cband-0.9.7.5-6.fc15.x86_64
httpd-mmn = 20051115-x86-64 is needed by (installed) mod_extract_forwarded-2.0.2-8.fc17.x86_64
httpd-mmn = 20051115-x86-64 is needed by (installed) mod_auth_mysql-1:3.0.0-18.fc15.x86_64
httpd-mmn = 20051115-x86-64 is needed by (installed) mod_pubcookie-3.3.4a-7.fc17.x86_64
httpd-mmn = 20051115-x86-64 is needed by (installed) mod_python-3.3.1-18.fc17.x86_64
Please report this error in https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=rawhide&component=yum


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

# yum --version
3.4.3
  Installed: rpm-4.10.3.1-1.fc18.x86_64 at 2013-02-16 15:55
  Built    : Fedora Project at 2013-02-06 09:54
  Committed: Panu Matilainen <pmatilai> at 2013-02-06

  Installed: yum-3.4.3-49.fc18.noarch at 2013-02-16 16:00
  Built    : Fedora Project at 2013-02-06 10:06
  Committed: Zdenek Pavlas <zpavlas> at 2013-02-06

  Installed: yum-plugin-aliases-1.1.31-9.fc18.noarch at 2013-02-16 16:54
  Built    : Fedora Project at 2013-02-08 09:05
  Committed: Zdenek Pavlas <zpavlas> at 2013-02-08

  Installed: yum-plugin-fastestmirror-1.1.31-9.fc18.noarch at 2013-02-16 16:54
  Built    : Fedora Project at 2013-02-08 09:05
  Committed: Zdenek Pavlas <zpavlas> at 2013-02-08


(or look above)

How reproducible:

Call `yum update` after upgrade from FC17 to FC18

Steps to Reproduce:
1. Call `yum update` after upgrade from FC17 to FC18
2.
3.
  
Actual results:
Several components render depsolve errors which must be corrected by hand (if at all possible) because of apparently stale dependencies.

Expected results:
No components of the distro should render a depsolve error after an upgrade.

Additional info:
I have  been noticing this since many upgrades back, i.e. there are always some components in the distro which are not upgraded correctly and then must be upgraded by hand. I am not complaining about components outside of the distro, but about software in the distro which have dependencies which seem to not be regarded in the scope of the distro or which are stale.

Thank you.

Comment 1 Jan Zeleny 2013-02-18 07:29:25 UTC
*** Bug 912039 has been marked as a duplicate of this bug. ***

Comment 2 Jan Zeleny 2013-02-18 07:59:16 UTC
Could you please run "rpm -Va --nofiles" and send us the output to check that your system is in consistent state in terms of dependencies? These issues are usually meaning that system is in inconsistent state prior to running the transaction therefore I'm leaning towards closing the bug.

Comment 3 ramindeh 2013-02-18 12:31:18 UTC
Per request of Jan Zeleny (Comment #2 above)

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
# rpm -Va --nofiles
Unsatisfied dependencies for grass-libs-6.4.2-4.fc18.x86_64:
        libgeos-3.3.2.so()(64bit) is needed by (installed) grass-libs-6.4.2-4.fc18.x86_64
Unsatisfied dependencies for osiv-2.0.0-0.9.beta.fc15.x86_64:
        libtiff.so.3()(64bit) is needed by (installed) osiv-2.0.0-0.9.beta.fc15.x86_64
Unsatisfied dependencies for grass-6.4.2-4.fc18.x86_64:
        libgeos-3.3.2.so()(64bit) is needed by (installed) grass-6.4.2-4.fc18.x86_64
Unsatisfied dependencies for plexus-runtime-builder-0:1.0-0.6.a9.fc15.noarch:
        xmlrpc is needed by (installed) plexus-runtime-builder-0:1.0-0.6.a9.fc15.noarch
Unsatisfied dependencies for plexus-appserver-0:1.0-0.7.a5.fc15.noarch:
        xmlrpc is needed by (installed) plexus-appserver-0:1.0-0.7.a5.fc15.noarch
Unsatisfied dependencies for plexus-xmlrpc-0:1.0-0.7.b4.3.fc16.noarch:
        xmlrpc is needed by (installed) plexus-xmlrpc-0:1.0-0.7.b4.3.fc16.noarch
Unsatisfied dependencies for maven-one-plugin-1.2-8.fc17.noarch:
        maven-shared-model-converter is needed by (installed) maven-one-plugin-1.2-8.fc17.noarch
Unsatisfied dependencies for assimp-2.0.863-8.20110824svn.fc18.x86_64:
        libIrrXML.so.1()(64bit) is needed by (installed) assimp-2.0.863-8.20110824svn.fc18.x86_64
Unsatisfied dependencies for postgresql91-plperl-9.1.8-2PGDG.f17.x86_64:
        perl(:MODULE_COMPAT_5.14.3) is needed by (installed) postgresql91-plperl-9.1.8-2PGDG.f17.x86_64
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Please note that I already removed some of the components which had stale dependencies dating from FC15 .. FC17.

Perhaps instead of asking me to report an error the installer should tell me that there are stale dependencies to take care of?

Thanks.

Comment 4 Jan Zeleny 2013-02-19 07:18:32 UTC
Thanks for the response. The output you posted suggests what are the issues you need to take care of prior to running yum. I'm closing this as NOTABUG, feel free to reopen if the issue persists after you fix the existing problems.

We will definitely work on improving the error message but we can't delete it altogether. Even though it is false positive in vast majority of cases, it still might really indicate an issue in depsolver in some cases.

Comment 5 Jan Zeleny 2013-02-19 07:19:06 UTC
*** Bug 912324 has been marked as a duplicate of this bug. ***

Comment 6 Jan Zeleny 2013-02-19 07:19:47 UTC
*** Bug 912360 has been marked as a duplicate of this bug. ***

Comment 7 Jan Zeleny 2013-02-19 07:21:38 UTC
*** Bug 912527 has been marked as a duplicate of this bug. ***

Comment 8 Jan Zeleny 2013-02-19 12:45:20 UTC
*** Bug 912692 has been marked as a duplicate of this bug. ***

Comment 9 Jan Zeleny 2013-02-20 07:01:55 UTC
*** Bug 912716 has been marked as a duplicate of this bug. ***

Comment 10 Jan Zeleny 2013-02-20 12:44:18 UTC
*** Bug 912999 has been marked as a duplicate of this bug. ***

Comment 11 Jan Zeleny 2013-02-20 16:52:04 UTC
*** Bug 913224 has been marked as a duplicate of this bug. ***

Comment 12 Jan Zeleny 2013-02-21 15:50:30 UTC
*** Bug 913488 has been marked as a duplicate of this bug. ***

Comment 13 Jan Zeleny 2013-02-21 15:52:19 UTC
*** Bug 913397 has been marked as a duplicate of this bug. ***

Comment 14 Jan Zeleny 2013-02-25 07:42:24 UTC
*** Bug 914813 has been marked as a duplicate of this bug. ***

Comment 15 Jan Zeleny 2013-02-25 07:44:07 UTC
*** Bug 914982 has been marked as a duplicate of this bug. ***

Comment 16 Jan Zeleny 2013-03-01 07:28:49 UTC
*** Bug 916376 has been marked as a duplicate of this bug. ***

Comment 17 Jan Zeleny 2013-03-04 07:20:58 UTC
*** Bug 917298 has been marked as a duplicate of this bug. ***

Comment 18 Jan Zeleny 2013-03-18 08:28:36 UTC
*** Bug 922526 has been marked as a duplicate of this bug. ***

Comment 19 Jan Zeleny 2013-03-21 14:51:26 UTC
*** Bug 923937 has been marked as a duplicate of this bug. ***

Comment 20 Jan Zeleny 2013-04-02 07:17:30 UTC
*** Bug 946876 has been marked as a duplicate of this bug. ***

Comment 21 Jan Zeleny 2013-04-02 08:51:56 UTC
*** Bug 929369 has been marked as a duplicate of this bug. ***

Comment 22 Jan Zeleny 2013-04-02 08:58:13 UTC
*** Bug 947077 has been marked as a duplicate of this bug. ***

Comment 23 Jan Zeleny 2013-04-03 07:42:02 UTC
*** Bug 947548 has been marked as a duplicate of this bug. ***

Comment 24 Jonathan Ryshpan 2013-04-03 09:04:23 UTC
I'm still confused.  Here's output from the command you recommend:

rpm -Va --nofiles
Unsatisfied dependencies for mod_python-3.3.1-18.fc17.x86_64:
        httpd-mmn = 20051115-x86-64 is needed by (installed) mod_python-3.3.1-18.fc17.x86_64

What is httpd-mmn?  An RPM?  A file?  I surmise that 20051115-x86-64 is some kind of a version identifier, but what?  How can I fix the error?

A simple minded attempt to fix the problem (following) is not successful.

# yum shell
Loaded plugins: langpacks, presto, refresh-packagekit
> info httpd-mmn
> install httpd-mmn
> ts

==================================================================================================================================================
 Package                         Arch                             Version                                 Repository                         Size
==================================================================================================================================================
Updating:
 httpd                           x86_64                           2.4.4-2.fc18                            updates                           1.1 M

Transaction Summary
==================================================================================================================================================
Upgrade  1 Package

> ts run
--> Running transaction check
---> Package httpd.x86_64 0:2.4.3-15.fc18 will be updated
--> Processing Dependency: httpd = 2.4.3-15.fc18 for package: httpd-manual-2.4.3-15.fc18.noarch
--> Processing Dependency: httpd = 2.4.3-15.fc18 for package: 1:mod_ssl-2.4.3-15.fc18.x86_64
---> Package httpd.x86_64 0:2.4.4-2.fc18 will be an update
--> Processing Dependency: httpd-tools = 2.4.4-2.fc18 for package: httpd-2.4.4-2.fc18.x86_64
--> Running transaction check
---> Package httpd-manual.noarch 0:2.4.3-15.fc18 will be updated
---> Package httpd-manual.noarch 0:2.4.4-2.fc18 will be an update
---> Package httpd-tools.x86_64 0:2.4.3-15.fc18 will be updated
---> Package httpd-tools.x86_64 0:2.4.4-2.fc18 will be an update
---> Package mod_ssl.x86_64 1:2.4.3-15.fc18 will be updated
---> Package mod_ssl.x86_64 1:2.4.4-2.fc18 will be an update
--> Finished Dependency Resolution

==================================================================================================================================================
 Package                              Arch                           Version                                Repository                       Size
==================================================================================================================================================
Updating:
 httpd                                x86_64                         2.4.4-2.fc18                           updates                         1.1 M
Updating for dependencies:
 httpd-manual                         noarch                         2.4.4-2.fc18                           updates                         1.3 M
 httpd-tools                          x86_64                         2.4.4-2.fc18                           updates                          80 k
 mod_ssl                              x86_64                         1:2.4.4-2.fc18                         updates                          94 k

Transaction Summary
==================================================================================================================================================
Upgrade  1 Package (+3 Dependent packages)

Total size: 2.6 M
Is this ok [y/N]: y
Downloading Packages:
Running Transaction Check
ERROR with transaction check vs depsolve:
httpd-mmn = 20051115-x86-64 is needed by (installed) mod_python-3.3.1-18.fc17.x86_64
Transaction encountered a serious error.

Comment 25 Jan Zeleny 2013-04-04 06:29:03 UTC
(In reply to comment #24)
> I'm still confused.  Here's output from the command you recommend:
> 
> rpm -Va --nofiles
> Unsatisfied dependencies for mod_python-3.3.1-18.fc17.x86_64:
>         httpd-mmn = 20051115-x86-64 is needed by (installed)
> mod_python-3.3.1-18.fc17.x86_64

There you go, that's the pre-existing problem on your system.

> What is httpd-mmn?  An RPM?  A file?  I surmise that 20051115-x86-64 is some
> kind of a version identifier, but what?  How can I fix the error?

httpd-mmn is a package provide of some sort. Not sure if it's a physical package, a file or just a virtual provide. Seems like the last one but it really doesn't matter at this point. The solution is to uninstall mod_python, as it is blocking update of httpd.

Comment 26 Jan Zeleny 2013-04-04 06:38:48 UTC
*** Bug 948061 has been marked as a duplicate of this bug. ***

Comment 27 Jan Zeleny 2013-04-05 06:17:16 UTC
*** Bug 948462 has been marked as a duplicate of this bug. ***

Comment 28 Jan Zeleny 2013-04-08 06:48:15 UTC
*** Bug 949300 has been marked as a duplicate of this bug. ***

Comment 29 Jan Zeleny 2013-04-11 07:33:26 UTC
*** Bug 950790 has been marked as a duplicate of this bug. ***

Comment 30 Jan Zeleny 2013-04-11 07:33:34 UTC
*** Bug 950791 has been marked as a duplicate of this bug. ***

Comment 31 Jan Zeleny 2013-04-19 06:47:40 UTC
*** Bug 953697 has been marked as a duplicate of this bug. ***

Comment 32 Jan Zeleny 2013-06-21 06:21:49 UTC
*** Bug 976496 has been marked as a duplicate of this bug. ***

Comment 33 Jan Zeleny 2013-06-26 10:02:49 UTC
*** Bug 978275 has been marked as a duplicate of this bug. ***

Comment 34 Jan Zeleny 2013-07-22 13:49:39 UTC
*** Bug 986946 has been marked as a duplicate of this bug. ***

Comment 35 Christopher Meng 2013-08-12 01:32:10 UTC
Rawhide:

** Found 1 pre-existing rpmdb problem(s), 'yum check' output follows:
cronie-1.4.11-3.fc20.i686 is a duplicate with cronie-1.4.11-1.fc20.i686

======
rpm -Va --nofiles returns none.

Comment 36 Michael Schwendt 2013-08-12 09:20:45 UTC
> cronie-1.4.11-3.fc20.i686 is a duplicate with cronie-1.4.11-1.fc20.i686

rpm -q cronie
package-cleanup --cleandupes

Comment 37 Christopher Meng 2013-08-12 09:25:44 UTC
(In reply to Michael Schwendt from comment #36)
> > cronie-1.4.11-3.fc20.i686 is a duplicate with cronie-1.4.11-1.fc20.i686
> 
> rpm -q cronie
> package-cleanup --cleandupes

Thanks, I've fixes it long time ago. 

Just found this bug and left the comment, not sure what caused this.

Comment 38 Jan Zeleny 2013-08-19 07:42:25 UTC
*** Bug 998114 has been marked as a duplicate of this bug. ***

Comment 39 Jan Zeleny 2013-08-27 06:46:38 UTC
*** Bug 1001328 has been marked as a duplicate of this bug. ***


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