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

Re: trac backport; adding me to bpo keyring

Dominic Hargreaves wrote:
> On Tue, Nov 14, 2006 at 03:17:32PM +0100, Norbert Tretkowski wrote:
>> http://www.backports.org/debian/new.html
>> It was already uploaded a week ago.
> I notice this is now available; thanks. However it's not usable with
>  mod_python on sarge due to the lack of a suitable backport of
> libapache2-mod-python2.3 >= 3.2.8-3. Does anyone have any plans to
> backport this? Cheers, Dominic.

I think I second this. Having a Sarge server with some backports
installed, I tell aptitude to upgrade trac 0.9.6-1 to 0.10.3-1~bpo.1. It
marks this for deletion:

    libapache2-mod-python2.3 version 3.2.8-2
    trac conflicts with libapache2-mod-python2.3 (< 3.2.8-3)

I need mod_python packages for another tasks. IIRC, I also happily set
up current trac using mod_python:

    <Location /project>
      SetHandler mod_python
      PythonHandler trac.web.modpython_frontend
      PythonOption TracEnvParentDir /var/lib/trac
      PythonOption TracUriRoot /project                 

Does this mean that I will have either trac 0.10 or mod_python on my
Sarge system?

I surely miss something, but why there exists a Sarge trac backport
without proper mod_python package? You all run standalone trac server
and restrict your servers from using mod_python at all?

Thanks in advance.

fn:Vlada Macek
adr:;;;Liberec;;;Czech Republic
title:UNIX Admin && Developer
tel;cell:+420 608 978 164
note;quoted-printable:GPG info: key 0x1F059424, fingerprint 1494 F8DD 6379 4CD7 E7E3 1FC9 D750=
	 4243 1F05 9424=0D=0A=
	When you find a virus in mail from me, then I intended to infect you, sin=
	ce I use SW that is not distributing malware w/o my knowledge.=0D=0A=

Reply to: