-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Alain Miniussi skrev 22. mai 2009 23:04: > On Fri, 22 May 2009 13:54:34 +0200, Emmanuel Blot <[email protected]> > wrote:
(...) >>> It's trac 0.10.3 >> SO old! >> Moreover, 0.10.3 has some security issue that has been fixed in 0.10.3.1. >> Check out http://trac.edgewall.org/wiki/ChangeLog#a0.10.3.1 >> >> Anyway, you should definitely think about installing Trac 0.11.4, >> rather than starting up with an ancient Trac release. > > Well, I first had a look at the dependency constraints on the web page and > though that using the default (the one you get with apt-get) package for > debian would at least deal with that part of the problem :-) moreover, > from a maintenance perspective, (and I am not alone on that one) working > with the default packages is close to a no brainer. Now, if there is a > security > issue, I'll probably move to the last stable version. > > Does anyone kown of an alternate, up to date, source for trac on debian ? Currently we run upstream trac0.11. It is handily installed with: aptitude install python-setuptools easy_install trac on Debian. You might want to look at virtualenv and friends -- as long as trac is a moving target, the "latest" version will never be in Debian stable. Whether packages such as python eggs, ruby gems, perl or php "PEAR" modules are best handled with aptitude or their various non-distribution counterparts is a matter of some debate -- personally I use setuptools/easy_install for trac, but not for other python modules. You might want to have a look at linux-vserver, the schroot package, xstow and/or apt-pinning and see which suits you better. Bottom line is that Debian Stable tries to guarantee feature/behaviour-freeze across the entire life of a release -- which is a very good thing, but does not work well with rapidly changing software, like trac (or various Ruby on Rails solutions, many small php-frameworks etc). I'd have a look at the section http://trac.edgewall.org/wiki/TracDev/DevelopmentEnvironmentSetup#Setupavirtualenvironment and below on the trac wiki -- I find this works quite nicely for managing trac installs. It does force you to use "more than aptitude" (unless you implement your own backport-mirror...) -- but that is hard to avoid with a fast-moving target like trac. Hopefully you have some way to manage your apache-config outside aptitude (even if that process consists of "editing the files when needed"). Also have a look at "yolk" (easy_install yolk), for managing python eggs (and trac) -- in particular "yolk --show-updates", that will give you an idea of packages that might need upgrading (always good to check the various dev-lists and debian-changelogs though -- packages in "main" gets security backports, after all). Btw, if you get CAS to play nice with Trac and svn, a small howto would be greatly appreciated -- might save me (and many ohters) some trial-and-error :-) - -e - -- .---. Eirik Schwenke <[email protected]> ( NSD ) Harald Hårfagresgate 29 Rom 150 '---' N-5007 Bergen tlf: (555) 889 13 GPG-key at pgp.mit.edu Id 0x8AA3392C -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkoZW7sACgkQxUW7FIqjOSzgBgCfYdqk8j+KdiiZo2aZDnqQjU4A mXwAn3Exjlsp3eLl+/zObQmsfdc3nPWb =svy6 -----END PGP SIGNATURE----- --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
