Upgrade Apache 1.3 mod_ssl to Apache 2.2

[beandip]

FreeBSD 6.3-STABLE AMD64.

I Am wanting to update the Apache to meet some criteria of a developer who will be modifying some of our BAMP apps.

PKG_INFO tells me I have apache+mod_ssl-1.3.41+2.8.31 installed.

I issue the command: portupgrade -o www/apache22 -rf apache13\*
which according to a couple of web sources should update and recompile the Apache and dependencies to 2.2.

The command uninstalls and the reinstalls the apache+mod_ssl-1.3.41+2.8.31 package.

What is the proper (and safest) way to update our Apache?

Thanks,

Brett

[DutchDaemon]

portupgrade -o www/apache22 apache13\* should work just fine.

[beandip]

shoot. I pasted the wrong command in my post last night. When I use portupgrade -o www/apache22 -rf apache13\* I am told ** No such installed package: apache13*

So then I tried portupgrade -o www/apache22 -rf apache+mod_ssl\*
which is the one that results in uninstalling and reinstalling the Apache 1.3 mod_ssl.

[DutchDaemon]

Drop -rf

[beandip]

Originally Posted by DutchDaemon

Drop -rf

I just tried it but nothing happens. The system seems to pause and then my bash prompt comes up.

<copy and paste>
[root@team ~]# portupgrade -o www/apache22 apache+mod_ssl\*
[root@team ~]#

[DutchDaemon]

grep the exact package name (for the installed version of apache) from pkg_info and use that as the last argument.

[beandip]

#pkg_info | grep apache
apache+mod_ssl-1.3.41+2.8.31 The Apache 1.3 webserver with SSL/TLS functionality
apache-ant-1.7.0_2 Java- and XML-based build tool, conceptually similar to mak


so i then tried portupgrade -o www/apache22 apache+mod_ssl-1.3.41+2.8.31
but get the same results as above.

Any ideas on why I seem to be stuck here? What are the ramifications if I uninstall the current Apache and reinstall Apache 2.2?

[DutchDaemon]

The only thing you could try is put the old port in quotes. Maybe the plus sign breaks something in your shell. Other than that: not much difference, really. It's basically what portupgrade -o does all by itself. So if you either use pkg_delete on the old port, or cd to its port dir and run make deinstall clean, it doesn't matter much.

[beandip]

My maintenance window ran out. I'll have to wait until the weekend.

If I deinstall the current port, leave the current httpd.conf in place, and install the Apache22 port will Apache2 basically use the same settings or am I better with a clean one and changing things to match such as directory locations, php, etc?

[DutchDaemon]

The latter. There are a lot of differences (esp. the minimal httpd.conf and the separate vhosts and ssl config files which are now pulled in by 'Include'ing them) and it's better to get used to the changes straight away. Keep your old httpd.conf as a reference and fill in the necessary details in the new config files.

[beandip]

I finally was able to get it updated.

The only gotcha was I couldn't get Apache2 to start and ended up having to remove mod_perl and install mod_perl2.

Thanks DutchDaemon for your advice.

[DutchDaemon]

yw!