Dependency error when trying to update apache

9 posts / 0 new
Last post
#1 Fri, 05/17/2013 - 08:03
bamazy@yahoo.com

Dependency error when trying to update apache

Dear all,

As usual, I used the Virtualmin Dashboard to update "httpd, httpd-devel, httpd-tools and mod_ssl" packages when the Dashboard showed there was an update for the packages. However, this time it gives me the below error:

========== Setting up Install Process Resolving Dependencies --> Running transaction check ---> Package httpd.x86_64 1:2.2.15-15.el6.vm.1 will be updated --> Processing Dependency: httpd = 1:2.2.15-15.el6.vm.1 for package: 1:httpd-devel-2.2.15-15.el6.vm.1.x86_64 --> Processing Dependency: httpd = 1:2.2.15-15.el6.vm.1 for package: 2:mod_ssl-2.2.15-15.el6.vm.1.x86_64 ---> Package httpd.x86_64 1:2.2.15-28.el6.vm.1 will be an update --> Processing Dependency: httpd-tools = 1:2.2.15-28.el6.vm.1 for package: 1:httpd-2.2.15-28.el6.vm.1.x86_64 --> Running transaction check ---> Package httpd-devel.x86_64 1:2.2.15-15.el6.vm.1 will be updated ---> Package httpd-devel.x86_64 1:2.2.15-28.el6.vm.1 will be an update --> Processing Dependency: /usr/local/bin/perl for package: 1:httpd-devel-2.2.15-28.el6.vm.1.x86_64 ---> Package httpd-tools.x86_64 1:2.2.15-15.el6.vm.1 will be updated ---> Package httpd-tools.x86_64 1:2.2.15-28.el6.vm.1 will be an update ---> Package mod_ssl.x86_64 2:2.2.15-15.el6.vm.1 will be updated ---> Package mod_ssl.x86_64 2:2.2.15-28.el6.vm.1 will be an update --> Processing Dependency: /usr/local/bin/perl for package: 1:httpd-devel-2.2.15-28.el6.vm.1.x86_64 --> Finished Dependency Resolution Error: Package: 1:httpd-devel-2.2.15-28.el6.vm.1.x86_64 (virtualmin) Requires: /usr/local/bin/perl You could try using --skip-broken to work around the problem

You could try running: rpm -Va --nofiles --nodigest

Running "which perl" gave me "/usr/bin/perl" so I created a symlink in order to solve the problem but it still gives the same error. And "which perl" command now returns "/usr/local/bin/perl".

I would appreciate any help which might lead to the solution of the error.

Fri, 05/17/2013 - 14:54
raedwald

I can confirm that I'm getting the same error and have followed the same steps highlighted by bamazy. Help would also be appreciated.

Fri, 05/17/2013 - 15:35
eddieb

Problem already reported here:

http://www.virtualmin.com/node/27361

Fri, 05/17/2013 - 23:24
andreychek

Yeah, sorry for the delay, Joe should have a fix for that pushed out soon though.

In the meantime, you can perform the Apache update by removing the httpd-devel package, if you're not using that (most folks don't need that package).

-Eric

Sat, 05/18/2013 - 05:13 (Reply to #4)
tcadmin

Im trying to install httpd-devel on a fresh CentOS 6.4 / Virtualmin install so I can build mod_rpaf.

Anything I can do until the fix?

The only thing I can think of is try to search for mod_rpaf in an rpm somewhere.. Im new at this, but really like Virtualmin / Webin after a year or so using it.

Thanks..

Sat, 05/18/2013 - 04:48
bamazy@yahoo.com

Eric, removing httpd-devel solved the problem. Thanks for the help.

Sat, 05/18/2013 - 05:10 (Reply to #6)
tcadmin

Im trying to install httpd-devel on a fresh CentOS 6.4 / Virtualmin install so I can build mod_rpaf.

Anything I can do until the fix?

The only thing I can think of is try to search for mod_rpaf in an rpm somewhere.. Im new at this, but really like Virtualmin / Webin after a year or so using it.

Thanks..

(Edit: Sorry bamazy, meant to reply to someone else and didn't see a way to remove this reply..)

Sat, 05/18/2013 - 09:56
andreychek

Well, you could always install the previous version of Apache from the Virtualmin repos in the meantime.

I'll make sure Joe knows you're waiting though :-)

-Eric

Thu, 05/30/2013 - 17:26 (Reply to #8)
tcadmin

I sat down with a cup of tea a day or two later to figure out how to downgrade my Apache on a fresh install and thought I would try to install httpd-devel to see if the problem was still there.

To my surprise and relief the developer package installed without any problems!

Many thanks to whoever fixed it!

Topic locked