[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Apache, amd64 and sarge



Asbjørn Sloth Tønnesen <asbjorn@asbjorn.biz> writes:

> Hi
>
> I have problems with at least 2 amd64-only problems with apache in
> sarge.
>
> 1. Apache::Request fails with unresolved dynamic load
>    http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=322448
>    required for Apache Gallery (libapache-mod-gallery-perl)
>
> 2. regular expression matching broken on amd64
>    http://issues.apache.org/bugzilla/show_bug.cgi?id=31858
>   
>    Example from http://firefox.asbjorn.it/
>    {w}=works, {b}=broken
>    {w} RewriteEngine On
>    {w} RewriteCond %{REQUEST_FILENAME} !-f
>    {b} RewriteRule ^([a-z0-9]+)-([0-9]+)x([0-9]+)
>          .png$ /$1.php?w=$2&h=$3 [QSA,L]
>    {b} RewriteRule ^([a-z0-9]+)-([0-9]+)x([0-9]+)-
>          ([.=&]*).png$ /$1.php?w=$2&h=$3&$4 [QSA,L]
>    {w} RewriteRule ^feed.xml$ /ffcountdown.php [QSA,L]
>
> A working patch exists for both bugs.
>
> Where should amd64-only bugs in sarge be filed, or shall I just be
> selfish and patch the packages just for my own use only, and forget
> about the time when a Debian server could apply security updates
> automatically (unattended-upgrades)?

Sarge bugs are usualy only fixed if they are security risks or large
issues. The risk of introuding new bugs with changes it too big.

You should make sure that the bugs are fixed in etch/testing so the
upcoming stable release does not suffer from the same problem. Apart
from that just patch your local package.

MfG
        Goswin



Reply to: