Re: [Trac] Kishore Yanna: Problem with repository

2009-12-28 Thread Kishore Yanna
Hi Olemis

As per your words I have changed repository_dir on trac.ini but i have
getting same problem.
please help me.

On Thu, Dec 24, 2009 at 7:28 PM, Olemis Lang  wrote:

> In a separate thread ;o)
>
> On Wed, Dec 23, 2009 at 10:51 PM, Kishore Yanna 
> wrote:
> > Hi Guys
> >
> > I have a login issues with my trac version 0.11
> > I have paurchesd from Jumpbox. and i have setup with postgres database
> > When ever I click any link on the home page I am getting  Internal error
> >
> > Please find the attachment for screen shot.
> >  Please can you please help any one to resolve my problem
> >
>
> Change your repository settings (reposiry_dir in trac.ini)
>
> --
> Regards,
>
> Olemis.
>
> Blog ES: http://simelo-es.blogspot.com/
> Blog EN: http://simelo-en.blogspot.com/
>
> Featured article:
> Minor optimizations. Protocol provider docs (WikiFormatting) shown in
> RPC docs page.  -
> http://bitbucket.org/osimons/trac-rpc-mq/changeset/f649f024fd90/
>
> --
>
> You received this message because you are subscribed to the Google Groups
> "Trac Users" group.
> To post to this group, send email to trac-us...@googlegroups.com.
> To unsubscribe from this group, send email to
> trac-users+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/trac-users?hl=en.
>
>
>


-- 

--
Thanks & Regards,
Krishna Kishore . Y
91-9177392403

--

You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-us...@googlegroups.com.
To unsubscribe from this group, send email to 
trac-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en.




Re: [Trac] lm-sensors and failure to control fan speed in Ubuntu

2009-12-28 Thread Michael Renzmann
Hi.

> I have a question related to lm-sensors and in particular fan control.

You want to redirect your questions to the lmsensors mailing list:
http://lm-sensors.org/wiki/FeedbackAndSupport#MailingList

Bye, Mike

--

You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-us...@googlegroups.com.
To unsubscribe from this group, send email to 
trac-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en.




[Trac] Re: Postgresql 8.4.2

2009-12-28 Thread ray


On Dec 27, 1:45 pm, ray  wrote:
> Is there a connector for Python 2.6 and Postgresql 8.4.2?  I only see
> pyscopg2 for 8.4.1.
> This will be for Windose XP.
>

I got this reply from psycopg group:

> Does the 2.0.13 (For Python 2.6) titled
> psycopg2-2.0.13.win32-py2.6-pg8.4.1-release.exe work for PostgreSQL
> 8.4.2 also?
>
> My intent is to use this with Trac and SVN with Apache.
>
> BTW, what is the debug build for?

Yes, it will work with 8.4.2.  The PostgreSQL version info is to
indicate what libpq version win psycopg is built against, for those
that
are interested in such things.

The debug builds sets a DEFINE on the compilation of psycopg2
(PSYCOPG_DEBUG) that enables the printing of additional information to
the
console if the environment variable PSYCOPG_DEBUG is set.  Useful if
tracking down a bug in PSYCOPG, and sometimes useful tracking down
problems in your python database code.  FYI, normally I use the
release
builds and NOT the debug builds since it cuts down a little on
unnecessary
overhead.  Note that on many UNIX like platforms, I believe the debug
information is sent to stderr.


-jason

--

You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-us...@googlegroups.com.
To unsubscribe from this group, send email to 
trac-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en.




Re: [Trac] Kishore Yanna: Problem with repository

2009-12-28 Thread Olemis Lang
On Mon, Dec 28, 2009 at 12:24 AM, Kishore Yanna  wrote:
> Hi Olemis
>
> As per your words I have changed repository_dir on trac.ini but i have
> getting same problem.
>

repository_type = svn
repository_dir =

If the problem is still there then there should be a bug in Trac ...
or something I don't know

-- 
Regards,

Olemis.

Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/

Featured article:
Simplified the main request handling/dispatching code. Also started
unittest for this API, te...  -
http://bitbucket.org/osimons/trac-rpc-mq/changeset/69869663370e/

--

You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-us...@googlegroups.com.
To unsubscribe from this group, send email to 
trac-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en.




[Trac] importing from csv

2009-12-28 Thread Francisco Cavaco
Hello,

I'm new to Trac and probably that shows with the problem I will put.
Nonetheless, I have not a lot to go and need to have my tickets
imported. My problem is the following:

I've set up my TRAC environment with the import plugin. afterwards,
I've setup customised fields for tickets and created an CSV file based
on that. Tried also a reduced version of my csv file such as the one
below:

summary;priority;reporter;type;status;milestone
1;1;Administrador;task;new;1.0.5


Tried to import and always get the same error :

Trac Error
The first line of the worksheet contains neither a 'ticket', an 'id'
nor a 'summary' field name. At least one of them is needed to perform
the import. Please check the file and try again.


when to check trac log and could find a similar error . i.e. did'nt
add much:-
2009-12-28 17:33:04,936 Trac[main] DEBUG: Dispatching 
2009-12-28 17:33:04,936 Trac[cache] DEBUG: cache metadata undefined
(youngest_rev=u'')
2009-12-28 17:33:04,936 Trac[cache] INFO: repos rev [0] != cached rev
[None]
2009-12-28 17:33:04,936 Trac[session] DEBUG: Retrieving session for ID
u'fjferreira'
2009-12-28 17:33:04,951 Trac[main] WARNING: HTTPInternalError: 500
Trac Error (The first line of the worksheet contains neither a
'ticket', an 'id' nor a 'summary' field name. At least one of them is
needed to perform the import. Please check the file and try again.)
2009-12-28 17:33:04,951 Trac[chrome] DEBUG: Prepare chrome data for
request


Can anyone help?

already grateful

Francisco

--

You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-us...@googlegroups.com.
To unsubscribe from this group, send email to 
trac-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en.




Re: [Trac] Customizing Ticket Save

2009-12-28 Thread Ryan J Ollos


Wagner Moratelli wrote:
> 
> Which files .py are executed when I submit form Ticket?
> I need customize the ticket to calculate time, then I need known whick
> files
> are used.
> 

I have to agree with Stephen's advice, but if you want to hack up the ticket
template, take a look at the source [1], and the recommendations provided
cboos in this ticket [2].

[1] http://trac.edgewall.org/browser/trunk/trac/ticket/templates
[2] http://trac.edgewall.org/ticket/8611#comment:2



-- 
View this message in context: 
http://old.nabble.com/Customizing-Ticket-Save-tp26811151p26946861.html
Sent from the Trac Users mailing list archive at Nabble.com.

--

You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-us...@googlegroups.com.
To unsubscribe from this group, send email to 
trac-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en.




Re: [Trac] Question about tickets

2009-12-28 Thread Ryan J Ollos


Slavok Slavok wrote:
> 
> Hello! In our company we have two additional properties of tickets:
> deadline, deadline comment. How can I add the checking: users can't
> change the deadline without filling the deadline comment field? Thanks
> for your answers.
> 

You might take a look at the TracTicketValidatorPlugin [1].  I haven't used
it myself.

[1] http://trac-hacks.org/wiki/TracTicketValidatorPlugin

-- 
View this message in context: 
http://old.nabble.com/Question-about-tickets-tp26811290p26947003.html
Sent from the Trac Users mailing list archive at Nabble.com.

--

You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-us...@googlegroups.com.
To unsubscribe from this group, send email to 
trac-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en.




New! Writing doctests for Trac plugins WAS: [Trac] Re: Writing tests for Trac plugins : How ?

2009-12-28 Thread Olemis Lang
On Tue, Jul 21, 2009 at 12:51 AM, Chris Heller
 wrote:
>
> There are numerous plugins on trac-hacks that have unittest based
> tests.

Thanks all for your suggestions and comments.

I have been preparing the next release (coming soon ;o) of TracGviz
1.4.1 and I've been (finally) able to publish the repos [1]_
containing most of the work been done so far. In there (`providers`
branch) you can find the doctests I've written to test Trac RPC
handlers. All this has been implemented on top of `dutest` module and
is the first instance (that I know ... CMIIW) of both a dutest-based
framework for particular purposes thus hiding details about
initialization and cleanup , and a framework to write doctests for
Trac plugins.

All tests pass using TracXmlRpc=1.0.0 and failures with
TracXmlRpc=1.0.6 have only been detected in ReportRPC (/me working on
it :-/ )

> Here are some handy starting points for exploration.
>
[...]

«Starting points for exploration» are here [2]_ [3]_ ;o)

Needless to say that there's a lot of place for enhancements in there
(especially tests for multi-protocol RPC, for repositories, and
in-process web testing ...) but at least you can get the idea of the
style and so on . Once I write further test cases they will show up
;o)

Feedback is welcome !

PS: C'u soon with a new release of TracGViz plugin ... Happy New Year !

o<|:o)

.. [1] TracGViz Hg @ sf.net
(http://simelo.hg.sourceforge.net/hgweb/simelo/trac-gviz/summary)

.. [2] Test cases (i.e. doctests) for RPC providers in TracGViz plugin

(http://simelo.hg.sourceforge.net/hgweb/simelo/trac-gviz/file/providers/trac-dev/gviz/tracgviz/testing/test_rpc.py)

.. [3] Minimalistic testing framework for Trac

(http://simelo.hg.sourceforge.net/hgweb/simelo/trac-gviz/file/providers/trac-dev/gviz/tracgviz/testing/__init__.py)

-- 
Regards,

Olemis.

Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/

Featured article:
Assessment of unittest 2.7 API : new features and opinions  -
http://feedproxy.google.com/~r/simelo-en/~3/cVOgG8NIBFY/assessment-of-unittest-27-api-new.html

--

You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-us...@googlegroups.com.
To unsubscribe from this group, send email to 
trac-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en.




Re: [Trac] Tickets Statuses and Resolutions

2009-12-28 Thread Ryan J Ollos


normalAnomaly wrote:
> 
> 1.   Ticket opened and assigned à Status=”New”.
> 
> 2.   Ticket resolved à Status=”Resolved”, with an option (ie “Action”)
> to “Verify”.
> 
> 3.   Ticket verified à Status=”Closed”.
> 

Have you looked at the TracWorkflow documentation [1]?  You may want to add
the QA step.

[1]
http://trac.edgewall.org/wiki/TracWorkflow#Example:AddingoptionalTestingwithWorkflow

-- 
View this message in context: 
http://old.nabble.com/Tickets-Statuses-and-Resolutions-tp26933087p26948455.html
Sent from the Trac Users mailing list archive at Nabble.com.

--

You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to trac-us...@googlegroups.com.
To unsubscribe from this group, send email to 
trac-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en.