-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jeroen Ruigrok van der Werven skrev 08-05-2008 09:24: | -On [20080508 06:22], Noah Kantrowitz ([EMAIL PROTECTED]) wrote: |> arrowes wrote: |>> I installed Trac 0.11rc1 from easy_install on debian etch with |>> python2.5 and apache2 with mod_wsgi and I get this message when I try |>> to load Trac:
(...) For more on getting python2.5+mod_wsgi to work, see below I have trac 0.11rc1 running on Debian etch with apache2, mod_python and python2.4. I recently did an upgrade (easy_install -U Trac), to follow along with upstream. If you are able to either run a different apache instance, or use mod_python, you shouldn't have any problems running trac 0.11rc1 on Debian. Note that you can have both python2.5 and python2.4 installed on Debian. Whether or not this helps you, depends on your reason for running mod_wsgi, of course. |> I really hope you just sent this before asking the exact same question in |> #trac, and receiving a clear answer. | | Which was the following, summarized: | | Debian Etch' system Python is 2.4, so basically moving to 2.5 brings you in | not-vendor (Debian) supported territory. (You want up to date packages? | Don't follow Debian. At least that's my impression of witnessing Linux from | the side of the BSDs.) Well, no. If you want stable packages follow Debian stable. If you want to "follow along with" upstream and can live with potential api-changes and other problems between upgrades, run Debian testing. (For example, Debian would never allow the kind of changes made to genshi in ~ a stable release -- now I *know* that genshi isn't considered to be stable ~ yet, just making the point that if you tested your package on a given Debian ~ stable release a year ago it will work (or fail:) the same way today as then). If you want binary packages that are essentially following upstream, use Debian unstable. (Ok, I'm a Debian fan, so I get a bit too easily annoyed when people comment on ~ the state of packages i Debian -- Please do not think that I'm ~ flaming/trolling, I've for a long time wanted to give *bsd a serious try, but ~ haven't gotten around to it yet). You are of course correct in your assertion that running anything outside of Debian stable, moves you into "non-vendor" territory. But it's not a bad such place to be, at least not on Debian :-) Besides, using easy_install/source-packages directly from upstream puts you in this position regardless of you distribution. If you can't live with the level of testing done in Debian Testing, you probably shouldn't be using any upstream packages at all. | Also, there is no Debian Etch supported mod_wsgi for 2.5. | | So all in all the conclusion was that trying to compile things by yourself | on Debian gets hairy at best. Well, being on Debian stable, means living with a stable feature set, frozen in time, waiting for next release. There are a couple of ways around this: * It's very easy to run a chroot with testing or unstable on your otherwise ~ stable server, I'd recommend using this with the linux-vserver patch, but ~ that is optional. Running a xen vm is also an option, ofcourse. * You could install lenny packages directly on your stable server, pulling only ~ needed dependencies from lenny (this is hard to do for things like python, ~ that are so tightly integrated with the distribution, and depends on newer ~ libc...) * You could pull source-packages from testing, and build them on your stable ~ system - this usually works quite well. * You could simply run lenny (testing) on the server serving trac Unfortunately http://www.debian-administration.org appears to be down at the moment, for some information on vserver on Debian see: ~ http://wiki.debian.org/LinuxVserver For some information on Debootstrap see: ~ http://wiki.debian.org/Debootstrap Note that all these solutions, with the possible exception of just sticking with debian testing -- might be considered "advanced". One important thing to keep in mind if you choose to go with testing (or especially unstable) is that you cannot like in stable, simply "update and forget" every night -- things might break! So list the updates, have a look at the changelogs, before upgrading your packages, and you should be fine. Best regards, - -- ~ .---. 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.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIIzlixUW7FIqjOSwRAvMeAKDFN/SFT5to3AMweRTcUW+CQrglYACfUbpe Z+RTGDGGg6TKyoBGkNPnK5o= =srkK -----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 -~----------~----~----~----~------~----~------~--~---
