There was an upgrade for apache22 (Apache/2.2.15) that added apr-ipv6-devrandom-gdbm-db42-1.4.2.1.3.9_1 Apache Portability Library package to the system by the straight attempt of portupgrade utility I executed without reading /usr/ports/UPDATING (20100518). Bad habit of not reading /usr/ports/UPDATING before performing the upgrade on my FreeBSD box ended up in;
Configuring Apache Portable Runtime library ... checking for APR... configure: error: the --with-apr parameter is incorrect. It must specify an install prefix, a build directory, or an apr-config file. ===> Script "configure" failed unexpectedly. Please report the problem to apache@FreeBSD.org [maintainer] and attach the "/usr/ports/www/apache22/work/httpd-2.2.15/config.log" including the output of the failure of your make command. Also, it might be a good idea to provide an overview of all packages installed on your system (e.g. an `ls /var/db/pkg`). *** Error code 1 Stop in /usr/ports/www/apache22. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portinstall.54022.0 env make ** Fix the problem and try again. ** Listing the failed packages (-:ignored / *:skipped / !:failed) ! www/apache22 (configure error)
So I decided to glance at /usr/ports/UPDATING after struggling quite a while;
20100518: AFFECTS: users of devel/apr0, devel/apr1, www/apache20, www/apache22 devel/apr port has been renamed to devel/apr1. WITH_APR_FROM_PORTS=yes for www/apache22 has been dissolved and may be removed from your configuration files; devel/apr1 is always used now. Please manually delete apache-2.\* if installed _before_ updating using either portmaster or portupgrade: pkg_delete -f apache-2.\* Then, if you use portmaster: portmaster -o devel/apr1 devel/apr If you use portupgrade: portupgrade -f -o devel/apr1 devel/apr Finally, reinstall Apache port if you deleted it earlier and update ports as usual (`XX' below is either 20 or 22): portinstall www/apacheXX
From that moment, uninstalling the apache package and issuing the “portupgrade -f -o devel/apr1 devel/apr” command and reinstalling apache consecutively wouldn’t work because forcing the upgrade of an already installed apr by specifying the origin somehow couldn’t be satisfying apache22.
In the end, uninstalling the apr1 itself solved my problem. Below is the sequence for those portupgraders who has no steady habit of investigating UPDATING file prior to upgrade processes. Of course if you didn’t break another thing when you boiled over apache.
# pkgdb -Fu # portsclean -CD # cd /usr/ports/www/apache22 # make deinstall clean # portupgrade -f -o devel/apr1 devel/apr # cd /usr/ports/devel/apr1 # make deinstall clean # cd /usr/ports/www/apache22 # make install clean
This shall let apache bring apr1 by itself however it likes.







RSS feed for comments on this post.




