Problem upgrading to apache 1.3.22-1

Problem upgrading to apache 1.3.22-1

Post by Dev Nul » Thu, 17 Jan 2002 04:17:00



I am currently running apache 1.3.14-3 on Red Hat 7.0. I perform regular
upgrades, but I'm having a problem with apache. I installed mm and expat
beforehand, as Red Hat suggests, but when I try to install the apache rpms
and mod_bandwidth, mod_put, & mod_throttle, I get these errors:

 # rpm -Fvh --test *
 error: failed dependencies:
        mod_bandwidth is needed by apache-1.3.22-1.7.1
        mod_put is needed by apache-1.3.22-1.7.1
        mod_throttle is needed by apache-1.3.22-1.7.1

Has anyone encountered or overcome this problem?

 
 
 

Problem upgrading to apache 1.3.22-1

Post by Nemesis Service » Thu, 17 Jan 2002 17:50:45


you could try the --nodeps command but this may break apache as it looks like the mods are only for apache 1.3.22-1.7.1

> I am currently running apache 1.3.14-3 on Red Hat 7.0. I perform regular
> upgrades, but I'm having a problem with apache. I installed mm and expat
> beforehand, as Red Hat suggests, but when I try to install the apache rpms
> and mod_bandwidth, mod_put, & mod_throttle, I get these errors:

>  # rpm -Fvh --test *
>  error: failed dependencies:
>         mod_bandwidth is needed by apache-1.3.22-1.7.1
>         mod_put is needed by apache-1.3.22-1.7.1
>         mod_throttle is needed by apache-1.3.22-1.7.1

> Has anyone encountered or overcome this problem?


 
 
 

1. Apache SCRIPT_NAME problem after upgrade 1.3.14 - 1.3.22

Hi.

I have run into problems trying to upgrade Apache from 1.3.14 to 1.3.22
on a Sun Solaris 8 machine. 1.3.22 does not handle SCRIPT_NAME the same
way (bug?). This is my scenario:

A cgi-script called script.cgi (the same problem occurs for
php-scripts).

Accessing the script with http://server/script.cgi
  both gives SCRIPT_NAME=/script.cgi.

Accessing the script with http://server/script.cgi/foo/bar
  both gives SCRIPT_NAME=/script.cgi and PATH_INFO=/foo/bar.

Accessing the script with http://server/script
  1.3.14 gives SCRIPT_NAME=/script
  1.3.22 gives SCRIPT_NAME=/script.cgi (!)

Accessing the script with http://server/script/
  1.3.14 gives SCRIPT_NAME=/script and PATH_INFO=/
  1.3.22 gives SCRIPT_NAME=/script/script.cgi (!) and PATH_INFO=/

Accessing the script with http://server/script/foo/bar
  1.3.14 gives SCRIPT_NAME=/script and PATH_INFO=/foo/bar.
  1.3.22 gives SCRIPT_NAME=/script/foo/script.cgi (!!!),
PATH_INFO=/foo/bar.

What's going on here???

-----------------------------------------------------------------------------
?ke Holmlund                                    Tel:  +46 - 90 786 57 16
Ume? University                                 Fax:  +46 - 90 786 65 50
Dept of informatics                             Email:

SE-901 87 Ume?
Sweden

2. XFree86-3.2 & Microsoft Mouse

3. Upgrading to Apache 1.3.22

4. setenv and wgtewch(curses)

5. apache upgrade from 1.3.20 to 1.3.22

6. Solaris 2.x backup, tape problem

7. Apache 1.3.22 Virtual Server Problems

8. Linux.com mail relay down?

9. Problems starting Apache 1.3.22

10. apache 1.3.22 start problem (core dump)

11. apache 1.3.22 problems

12. Apache 1.3.22 start problem

13. problems enabling mod_auth_db in Apache 1.3.22