a new release is on its way, I'd like to try the new
release (even if it's still beta).
Thanks in advance,
Daniel Serodio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac
Users" group.
To post
?
Thanks in advance,
Daniel Serodio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac
Users" group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send
Jani Tiainen wrote:
(snip)
>
> Not sure about ideas, but it really feels stupid to do something
> manually since Trac upgrade process already automatically, without
> asking added some other stuff (like workflow) in trac.ini file. Why an
> earth it couldn't repeat old behaviour and add that tw
I moved a project to another location in the same repository,
"trac-admin resync'ed", but now the changesets in this Trac environment
don't work anymore (No node at revision 1234).
Is this a known issue? I'm using Trac 0.10.3
Thanks i
ct
seems interesting, but I haven't had the time to give it a try. It's an
engine + commandline frontend, no Trac search plugin yet
(http://supose.soebes.de/ticket/46)
HTH,
Daniel Serodio
--~--~-~--~~~---~--~~
You received this message because you are s
Try http://dev.rectang.com/projects/tram
Pablo Escobar escreveu:
> Hi,
>
> I have installed trac and added three differente projects to it. I am using
> trac 0.10.3-1etch2 from debian etch repositories.
>
> I am trying to add a custom menu in order to change to the differents
> projects. I woul
matt marcum escreveu:
> well I ended up fixing this - sort of. I change the location
> directive in my apache configs to point to a sub directory -
> originally I wanted trac to show up as the root of the website. I
> changed the Location to point to /trac and now all my links work
> correctly,
I guess Apache (mod_php) is answering your request, not Trac. What URL
are you using? What's does your apache config section for Trac looks like?
Daniel Serodio
drmagu wrote:
> Newbie question ...
>
> Browsing a SVN 1.4.6 repository using TRAC 0.10.4
>
> Example, if I ha
ation error, or is it a Google Groups problem?
Where should I report this problem?
TIA,
Daniel Serodio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac
Users" group.
To post to this group, send email to tr
a way to
> modify a Wiki Page.
>
> Has anyone used this for editiing Wiki pages
You may want to track this bug:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=190891
HTH,
Daniel Serodio
--~--~-~--~~~---~--~~
You received this message because you are sub
What's the "recommended" way to deploy Trac, using tracd or mod_python?
Thanks,
Daniel Serodio
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Trac
Users" group.
To post to this group,
Eoin Dunne wrote:
>
> I don't think trac works with apache 2.2.
Ops. That would mean that I'm screwed :-)
Do you have any more information about this?
TIA,
Daniel Serodio
> -Original Message-
> From: trac-users@googlegroups.com [mailto:[EMAIL PROTECTED]
> On
I did a major upgrade on my (Linux) server, including Apache (2.0 to 2.2),
mod_python (from Python 2.3 to 2.4) and Trac (0.10pre to 0.10.2).
After this upgrade, I recompiled my trac plugins for Python 2.4, reinstalled
them, restarted Apache, etc.
After the upgrade, the XML-RPC plugin stopped work
e reports to not care about description.
> Lot faster now.
>
Would you care to ellaborate on these "speed up features"?
TIA,
Daniel Serodio
>
> Now I’m thinking in another possibilities. Is it possible to split the
> database in two? (The tickets type requirements in one da
Lutz Frommberger wrote:
> Hi everyone,
>
> yesterday I fooled around with the Debian unstable 0.10 package (not
> a good idea, these bdb incompatibilities really suck). Now I want to
> go back to 0.9.6, but I noticed that the 0.9.6 package in "testing"
> requires this "python-support" package, whi
How can I add a link to a ticket comment in another ticket, eg, add a
link to Ticket 1's comment #2 in ticket #3?
Using "ticket:1#comment:2" (without the quotes) creates a working link,
but it's displayed as a broken link ("beige" c
16 matches
Mail list logo
