hello
i encountered a problem with trac, which gives the following message:
Oops…
Trac detected an internal error:
SubversionException: (Failed to load module for FS type 'fsfs',
160033)
There was an internal error in Trac. It is recommended that you inform
your local Trac administrator and
I have installed the timing and estimation plugin and the work log
plugins - neither of which is entirely satisfactory.
Are there any alternatives to help me reduce the time it takes to
generate invoices?
--~--~-~--~~~---~--~~
You received this message because
Still: there should not be a logout button if not log out action is
available.
Logout is sometimes possible by clicking logout and restarting the browser.
Sure, but this was not my point ;-)
(btw: A browser with a clear HTTP credential option is even better)
Yunior Armando Hernandez Andrade wrote:
Actually you need 2 more dependencies,
- the ones you said, plus
3) Task A cannot start until task B starts (finish doesn't matter)
4) Task A cannot end until task B ends (start doesn't matter)
I don't see it. Can you give me an example of those types
Hi,
I want to add a CustomField to the Tickets. The new CustomField should
contain The Version when the Bug was fixed. The Version field
contains the Version in which the Bug was introduced or discoverd.
Therefore i've added
[ticket-custom]
fixedin = select
fixedin.label = Fixed In
Emmanuel Blot wrote:
That is why I think it is _NOT_ an issue. It's just the way HTTP is.
Still: there should not be a logout button if not log out action is
available.
Logout is sometimes possible by clicking logout and restarting the browser.
--
Chef de
On Tue, Apr 7, 2009 at 12:58 AM, Jani Tiainen rede...@gmail.com wrote:
John Hampton kirjoitti:
Olemis Lang wrote:
This is in order to use the ORM. Ok. But my question was actually
about overriding Trac built-in models by using classes generated by
the ORM, perhaps using the same or similar
On Apr 7, 6:39 am, MartinHMB mar...@senfdax.de wrote:
Hi,
I want to add a CustomField to the Tickets. The new CustomField should
contain The Version when the Bug was fixed. The Version field
contains the Version in which the Bug was introduced or discoverd.
Therefore i've added
Marcus Lindblom wrote:
Hi all,
I'm trying to fix this for the TracMercurial-hook, but I suppose it's no
different for other hooks, such as subversion. (By default, it just
ignores out-of-band changesets)
I've tried to alter an existing hook but I don't know enough Trac to
spot the
I'd like to close a component for reporting, but do not want to
invalidate the existing tickets in this component.
thoughts?
__
cu
christian unger
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups Trac
Users
Hi.
I'd like to close a component for reporting, but do not want to
invalidate the existing tickets in this component.
thoughts?
Just do it, it should not harm existing tickets. Deleting a component just
makes it unavailable for future selection, but does not remove it from any
already
The debian etch does not come with Subversion 1.5.
So I followed instruction over here: http://www.rooftopsolutions.nl/article/198
A new trac project with a new repository works fine. However,
integrating this old trac project with new repository seems to be a
problem.
Any further clues?
-
CS.
12 matches
Mail list logo