[Pkg-trac-devel] Trac Packaging Status

[Vincent Caron]

On jeu, 2008-06-26 at 15:02 -0300, Otavio Salvador wrote:
> Chris Hildebrandt <slam at sidux.com> writes:
> 
> > Hi,
> >
> > as I can see here http://packages.qa.debian.org/t/trac.html most of you
> > are quite busy with other stuff, and therefore I offer to assist getting
> > the recently released Trac 0.11 final (together with some common
> > plugins) properly packaged and uploaded into experimental/unstable.
> >
> > Please let me know how I can help.
> 
> Please test current experimental package and report back to me if it
> works. If it does, I can package final and upload to sid.

  I'm interested in helping to do so. I have an Etch server with ~30
Trac instances and ~10GB of data, and would like to test the upgrade
process from 0.10.4 to 0.11.0.

  I have already cloned a subset of my production machine into a Xen
domU and it's ready to be tweaked in any way. I also have some public
Trac data repos to share if it may help.

  Right now I suppose I would have to dist-upgrade my test server from
Etch to Sid, add the 'experimental' branch in my APT sources and try
your latest Trac package. Is that right ?

  However I am wondering how to proceed in my production context: I
traditionnally backport packages here and there to keep all my servers
on the stable release (http://deb.bearstech.com/). I have tried
apt-pinning but python-support >= 0.8.0 basically pulls all the unstable
branch down to the glibc. Seems like building a pre-0.8.0 python-support
would do 90% of the backport job for me.

  Thanks for your work and your help,

  Vincent