gmane.comp.version-control.subversion.trac.general

[Trac] Reports: PostgreSQL Join/Sum Help

dkl13 — 2013-05-17T15:19:42


I can do some basic SQL, but my overall SQL knowledge is very light. What 
SQL would return the desired results for the scenario below?

   - Trac 0.12
   - PostgreSQL 8.3
   - ticket-custom fields:
      - *parent*: e.g., If ticket #22 is a child ticket of ticket #14, 
      ticket #22 will have 14 in this field.
      - *backlog_points*: Backlog points as numbers (e.g., 11), although 
      this field is a text field (so to_number() needed?).
   
  
*Desired report:*

   - Display *only parent tickets* in the report. These parent tickets are 
   identified by *parent = blank* (ticket_custom table).
   - Sum the backlog_points (ticket_custom table) for any child tickets for 
   each parent and display that on each row of the parent tickets report 
   (Total Backlog Points)
   - Would also be great to have a column that lists all the child tickets 
   as clickable ticket links, but that may not be possible.

  
*Sample data:*

   - #14 = parent ticket
      - #22 (backlog_points = 5) = child of #14, so has 14 in parent field
      - #24 (backlog_points = 1) = child of #14, so has 14 in parent field
      - #25 (backlog_points = 7) = child of #14, so has 14 in parent field
   - #12 = parent ticket
      - #15 (backlog_points = 1) = child of #12, so has 12 in parent field
      - #17 (backlog_points = 5) = child of #12, so has 12 in parent field
   
Report:
 
*ID  Total Backlog Points  Child Tickets*
14          13            22, 24, 25
12           6            15, 17
 
Most of the scrum/agile plugins we've tried, by the way, have problems. (We 
are on an out-dated version of Python, which is a situation 1) I have no 
control over, and 2) probably won't change for a year or so. This tends to 
limit what plugins we can use.) Thanks!
 
D

[Trac] SimpleMultiProject x Milestone - How to Use?

Ivanelson Nunes — 2013-05-15T16:45:38

About SimpleMultiProject Plugin

What I could understand is that the plugin is a partnership between a custom
field called "project" and Milestones tool that already exists in Trac. So it
makes sense to create tickets without assigning a milestone? Or is this just
a administrative decision?

Or milestone is a requirement of Plugin?

I want to use this plugin, but as I have many Tickets. Tickets
Inclsuive without
Milestnoe. Then came a question. What to do with these Tickets?

< at >ivanelson
[]s

[Trac] Apache Error After Upgrade to Trac 12.2

2013-05-14T14:55:32

Good Morning,
 
I ran the easy_install upgrade in order to upgrade trac from version 12.1 
to 12.2.  However, apache displays the following error after the upgrade 
:"The server encountered an internal error or misconfiguration and was 
unable to complete your request."  A check in the ssl_error_log yields this 
message: "PythonHandler trac.web.modpython-frontend: ImportError: No module 
name trac".  I am not sure how to get trac back to working.  Attempting to 
restore from the hotcopy backup was not successful.  Any help or 
suggestions would be greatly appreciated.

[Trac] Dealing with large files and trac tickets: git annex + trac?

2013-05-13T08:35:04

Hello!

To give background or 'what is the real problem', here is what is our situation:

We are having teams 'developers' and 'sales'. Team 'sales' communicates with customers and creates tickets to our internal Trac with information needed to process the task. Team 'developers' takes care of the actual work and accepts->does->closes the tickets. Now some tickets have request like 'make a movie file from large dataset xyz', and the results are quite large files: from 10M to 2G.

Now how to deliver the data to 'sales'? Us, 'developers' are technically aware, while sales is not that much. Also we would like to have some information from the files (who uploaded, when, why, was this file updated).

Possible solutions include at least:
* Shared network drive: Set up standarad samba/etc share. Doable, though missing commit messages and we need to configure the 'sales' machines (mac + windows) so they can access the disk. Needs also extra backups to avoid 'whops did i delete wrong file'.
* Normal SVN/Git: Use normal Trac and version control. Team 'sales' access the results via Trac/browse-source but would require 'developers' to check out all the results (of ~500G) before able to make a commit. Not nice.
* Some 'public dropbox.com': Not doable due management decision.
* Some 'private dropbox': Could be doable but i am not too eager to add 'yet another service' -- nor to upload files via www-interface.
* SVN + post commit hooks: Make hooks that clear some 'upload' directory to 'view' directory. Hack solution, not good. How to remove files? Replace content of 'bigfile.bin' with text 'post commit moved the file' and handle removal of that? Re-inventing git annex?

Now what i came up as best solution would be to use git-annex [1] with central repository: 'sales' can access the results via www-interface in the Trac, developers can update/upload files without downloading the content of the whole repository and we have full version history of all files. And developers even get to download (existing) results easily from command line if such is needed/wanted.

Unfortunately, git-annex does not work with Trac browse-source www-interface. I can see the files but downloading the content fails.

Any suggestions how to proceed:
* Are we doing just something silly -- we cannot be the only ones with this sort of situation?
* I guess the problem is how the Trac gets content to file from Git repository -- hacking tips? Somebody done this all ready? I tried googling but got very little results from some reason.

Thanks!

[1] http://git-annex.branchable.com/

[Trac] TracQuery: Update Button Missing

Will Green — 2013-05-13T14:54:58

Hello,

I'm running Trac 1.0.0 on CentOS 6. When I try to use the custom query
interface the update button is missing. This happens on Chrome,
Safari, IE and Firefox. See screenshot:
https://flux.org.uk/tmp/trac-no-update-button.png

When I query the source in a browser it seems the div containing the
button is set not to be displayed:

<div class="buttons" style="display: none;">
<input type="hidden" value="priority" name="order">
<input type="submit" value="Update" name="update">
</div>

I have admin permissions and trac.ticket.query.*, QueryModule and
TicketQueryMacro are enabled. Running trac-admin upgrade says the
database is up-to-date.

Could installing/uninstalling a plugin have caused this? This is the
first time I've used this feature, so not sure if it was working when
I first installed Trac.

Not managed to find any similar cases on the mailing list or in the
documentation. Am I missing something obvious?

TIA,
Will

[Trac] WARNING: Discarding duplicate repository ''

Brettschneider Falk — 2013-05-14T07:36:20

Hi,
my trac.log is full of this warning:
[2013-05-13 12:20:25,832 p4408:t3128] api.py:599 WARNING: Discarding duplicate repository ''

How can I fix that?

I have several repos:
Name            Type            Directory               Revision
(Standard)                      Alias of Foo
Foo             svn             X:/svn/Foo              [12345]
Foo2            svn             X:/svn/Foo2             [67890]
Foo3            svn             X:/svn/Foo3             [23456]
...


CU, F< at >lk

----
R&D Software
Baumer Optronic GmbH
www.baumer.com




Gesch?ftsf?hrer: Dr. Albert Schmidt* Dr. Oliver Vietze
Sitz der Gesellschaft: Radeberg
Amtsgericht Dresden: HRB 15379
Ust. ID: DE 189714583

[Trac] Upgrading TRAC from 0.12.1 to 0.12.2

2013-05-10T18:58:59

Good Aftternoon,
 
I am fairly new with managing/administering TRAC and subversion on my 
project.  I have been tasked with conducting an upgrade of TRAC from 
version 0.12.1 to version 0.12.2.  We use a subversion repository.  What is 
the best way to conduct this ugrade?  I am starting by using a test version 
that is running on a development server.  My plan was to load a subversion 
dump from the production server into subversion that is running on the 
development server.  Next, I planned to resync TRAC with the repository and 
then conduct the upgrade of TRAC to version 0.12.2.  Is this a sound method 
for conducting this upgrade?

[Trac] Request for feedback WAS: [Apache Bloodhound] #509: Test compatibility with XMLRPC Plug-in

Olemis Lang — 2013-05-10T06:17:21

Hi !

It'd be nice if you could follow the instructions below and try recent
compatibility improvements applied upon trachacks:XmlRpcPlugin .

In the next few days I'll be adding more RPC handlers expose data
managed by Trac core , and other plugins . The former might be
backported relatively soon in trachacks:XmlRpcPlugin , if they prove
to be useful .

Thanks for your interest in Apache™ Bloodhound and supported plugins .

---------- Forwarded message ----------
From: Apache Bloodhound <dev-ysmIyYXm7GsV5AlzV+g+s80vGNN6ct63< at >public.gmane.org>
Date: Fri, 10 May 2013 05:54:59 -0000
Subject: Re: [Apache Bloodhound] #509: Test compatibility with XMLRPC Plug-in
To:
Cc: commits-ysmIyYXm7GsV5AlzV+g+s80vGNN6ct63< at >public.gmane.org

#509: Test compatibility with XMLRPC Plug-in
-----------------------+------------------------------
  Reporter:  mbooth    |      Owner:  mbooth
      Type:  task      |     Status:  review
  Priority:  critical  |  Milestone:
 Component:  plugins   |    Version:
Resolution:            |   Keywords:  rpc XmlRpcPlugin
-----------------------+------------------------------
Changes (by olemis):

 * status:  accepted => review
 * owner:  olemis => mbooth


Comment:

 Hi Matt !

 Replying to [comment:7 mbooth]:
 > Cool, thanks for your work on this.
 >
 > I'm actually okay with a fork as long as the XML-RPC API remains
 unchanged. There is already a lot of software out there that talks to Trac
 programatically and it would be great if it all could also talk to
 Bloodhound without change -- it would greatly lower the barrier to
 adoption :-)

 I have pushed some changes onto [https://bitbucket.org/olemis/bloodhound-
 rpc/src/8075ed8a7cd4?at=bloodhound_rpc bloodhound_rpc branch] in
 [https://bitbucket.org/olemis/bloodhound-rpc olemis/bloodhound-rpc
 repository < at > Bitbucket] . All plugin tests are successful in my local
 working copy after applying the following patches (order matters).

 {{{#!sh

 $ hg qapplied
 t509/t509_r1477773_tracadmin_globalcmd_attr.diff
 t514/t514_r1477773_load_bootstrap_handler.diff
 t514/t514_r1477773_tracd_bootstrap.diff

 $ hg log -r qparent --template="[{svnrev}] - {desc}\n"
 [1480224] - Translate SELECT part of CREATE TABLE ... AS SELECT ...
 queries.

 Fixes an issue where some product plugin tables were prepopulated with
 rows from global product.

 }}}

 After reviewing [https://bitbucket.org/olemis/bloodhound-
 rpc/compare/bloodhound_rpc..#diff the differences] it is possible to
 realize that not much has changed in the plugin but there are subtle
 (backwards compatible) usage differences if running against product
 environments .

 Please review .

[Trac] Ticket date problem (TracJSGanttChart related?)

Joost Kraaijeveld — 2013-05-09T08:39:47

Hi

I am trying to convince Trac to use the Dutch version of date and time
notation ( hh:mm:ss dd-mm-yyyy , ISO 8601). While experimenting I
managed to introduce an error. I created a ticket and now I get the
following errors, depending on the actual date notation used of course:

Ticket 4 has an invalid userstart value, "11-5-2013". It should match
the format "%Y-%m-%d".
Ticket 4 has an invalid userstart value, "11-5-13". It should match the
format "%Y-%m-%d".
Ticket 4 has an invalid userstart value, "11-05-13". It should match the
format "%Y-%m-%d".

Changing the date to "2013-05-13" works OK, but that is not what I
want. 

The only entry in the Trac.ini that mentions "date_format = %Y-%m-%d" is
[TracPM], which is JSGanttChart related I believe?. Changing that to
another format (e.g. to "date_format = dd/mm/yyyy" or "date_format =
dd-mm-yyyy" or "date_format = %d-%m-%Y") did not change the error
message part "It should match the format "%Y-%m-%d".

Is it possible to convince Trac to use Dutch time/date notation
*throughout* the whole interface? I.e. tickets, timelines, roadmaps?

TIA

Joost

[Trac] Many errors in plugin TracChartMacro - Trac1.0

Ivanelson Nunes — 2013-05-09T00:10:23

Hello,

My Trac1.0 / Ubuntu / Postgres.

I'm trying to use the plugin [1]TracChartMacro.

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

Found 02 errors:

2013-05-08 20:48:25,537 Trac[formatter] ERROR: Macro TicketChart(type =

2013-05-08 21:02:06,537 Trac[formatter] ERROR: Macro TicketChart(type =


Thank You.

[Trac] Bloodhound/Trac Replacement for some MS Sharepoint Functions

Ted Allen — 2013-05-08T19:34:04

Hello,

I am looking at an open-source option for replacing at least one of the 
functions we currently utilize Microsoft's Sharepoint product for, in 
particular a searchable record of problems/issues/tasks or team ends up 
working on.  When a team member is on-call, we may receive requests for 
assistance in a number of ways including page/SMS Text, phone, email to a 
shared team mailbox, email to individual user and Microsoft Lync chat 
session.

We typically record these by creating a new Sharepoint item in our "Support 
Notes" section.  One thing that this allows that we would like to maintain 
is the ability to send/forward an email to an email address that results in 
an item being added to the "Support Notes" section on Sharepoint without 
having to cut/paste the contents of an email and use the web interface to 
access Sharepoint and create a new item.

Sharepoint has worked well for us in the past, however, due to the large 
number of entries being created by all groups within our organization we 
are finding that search capabilities are running months behind (new entries 
added are not detected by a search for at least 30-60 days after being 
created and if errors during a "crawl" occur, this gets extended by another 
30-60 days).  As such, it is becoming less useful as a searchable 
repository for our on-call support notes.

While looking for options, I noticed the Apache Bloodhound project looked 
like a potential option and that it was built on Trac.  What I am wondering 
is if Bloodhound/Trac has any built-in capabilities to have new entries 
created via a SMTP mail message coming into a mail account on the server 
where Bloodhound/Trac is running?  If not, is there a plug-in mechanism 
that would allow us to develop a component that could take the subject line 
of a received email and utilize it as the "Summary" and the email body as 
the content of a new ticket to be created within Bloodhound/Trac?  If so, 
is there a documented API for creating such an entry?  When I tried the 
online Bloodhound demo and created a new ticket, it looked like there was a 
basic window and an "full dialogue" option which would prompt for more 
details when creating the ticket.  With the email option we might only 
easily have access to data for the "Summary" and "Description" sections (no 
specifics for "Product", "Version", "Type").

Any thoughts on how we might be able to utilize Bloodhound/Trac (or an 
alternative) running on SLES 11 on System z (s390x Mainframe architecture) 
to provide us the stated functions of Sharepoint without the search issues 
we are encountering would be greatly appreciated.  Thanks in advance for 
your time and assistance.

Best Regards,

Ted

[Trac] how to escape special charactors in connection strings

xiangjun zhang — 2013-05-08T08:35:02

I just type command:

trac-admin /path/to/project initenv

and when it comes to the connect strings, my database password is something 
like this:

mysql://root:*< at >*< at >localhost:3306/project


escaping or quoting does not work, any help?

[Trac] SOLVED 0.11 to 0.12 Genshi Translator error

Paul Mackinney — 2013-05-07T21:34:18

I've found several other threads by people who updated from RHEL 5 to RHEL 
6, only to encounter *AttributeError: 'Translator' object has no attribute 
'setup**'*

This post is for the next person who hits this one ;-)

- Started with working 0.11 Trac running on RHEL5 with mod_python
- Follow the Trac Migration page to move it onto a brand new RHEL6 system 
with Trac 0.12 installed from EPEL6.
- Read up on Trac & mod_wsgi and configure. I used the method that creates 
a /tmp/deploy folder which you then move into your main site folder. The deploy 
folder has cgi-bin and htdocs, trac.wsgi is in cgi-bin (unlike some of the 
examples which assume that trac.wsgi is in a folder named 'apache')

At this point running "tracd --port 8000 /my/path" works fine, but through httpd 
it fails

Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/trac/web/api.py", line 446, in send_error
    data, 'text/html')
  ... 10-12 lines omitted ...
  File "/usr/lib/python2.6/site-packages/trac/web/chrome.py", line 802, in <lambda>
    Translator(translation.get_translations()).setup(template))
AttributeError: 'Translator' object has no attribute 'setup'



Genshi-0.5.1 is installed in /usr/lib64/python2.6/site-packages/ but 
Genshi-06 is installed in /usr/lib/python2.6/site-packages

mod_wsgi lets you append to the PythonPath, but I needed to insert, soinstead I tweaked the trac.wsgi file:

import os
*import sys
sys.path.insert(0,'/usr/lib/python2.6/site-packages/Genshi-0.6-py2.6.egg')*

def application(environ, start_request):
    if not 'trac.env_parent_dir' in environ:
        environ.setdefault('trac.env_path', '/data/system/trac/ondmain')
    if 'PYTHON_EGG_CACHE' in environ:
        os.environ['PYTHON_EGG_CACHE'] = environ['PYTHON_EGG_CACHE']
    elif 'trac.env_path' in environ:
        os.environ['PYTHON_EGG_CACHE'] = \
            os.path.join(environ['trac.env_path'], '.egg-cache')
    elif 'trac.env_parent_dir' in environ:
        os.environ['PYTHON_EGG_CACHE'] = \
            os.path.join(environ['trac.env_parent_dir'], '.egg-cache')
    from trac.web.main import dispatch_request
    return dispatch_request(environ, start_request)

[Trac] Attachments not moved to new structure after upgrade to 1.0

Quintin Siebers — 2013-05-03T14:54:59

Hey,

I've recently upgraded one of my environments to Trac 1.0, and something 
went wrong in the process. My attachments have not been moved to the new 
structure and are still located in the attachment folder. I've tried to 
re-do the environment upgrade, but it doesn't change the attachments, just 
states that the database is already up to date. 

Is there a way to force a re-check for the attachment upgrade?

With regards,

Quintin Siebers

[Trac] Exclude Wiki pages in RecentChanges macro

Franz — 2013-04-30T08:27:49

Hi,

I would like to see all recently made changes except of QM-pages (which 
resides under QM/Step1, QM/Description, etc.)

Is there a way to exclude wiki pages in RecentChanges macro?

Thanks in advance,
Franz

[Trac] Non-ticket reports with the # sign prepended

Chris — 2013-04-24T00:19:13

I'm generating a report with the following query:

SELECT owner as id, 
(SELECT count(*) FROM ticket b WHERE b.owner=a.owner AND status = 'new') as 
New,
(SELECT count(*) FROM ticket b WHERE b.owner=a.owner AND status = 
'assigned') as Assigned,
(SELECT count(*) FROM ticket b WHERE b.owner=a.owner AND status = 'fixed') 
as Fixed,
(SELECT count(*) FROM ticket b WHERE b.owner=a.owner AND status = 
'verified') as Verified,
(SELECT count(*) FROM ticket b WHERE b.owner=a.owner AND status = 'closed') 
as Closed,
(SELECT count(*) FROM ticket b WHERE b.owner=a.owner AND status = 'hold') 
as Hold
FROM ticket a
WHERE status <> ''
GROUP BY owner

Which gives me something like:

Id      | New  | Assigned | Fixed  | Verified | Closed | Hold 
---------------------------------------------------------------
#user1  |    8 |     0    |  14    |   2      |   2    |  12
#user2  |    2 |    10    |   1    |   0      |   5    |   2
#user3  |   18 |     5    |   4    |   0      |   8    |   5
#user4  |    1 |     1    |   0    |   1      |   1    |   0

Is there a way to get the "#user1" to lose the "#" symbol and link 
somewhere useful?

Please forgive the ugly SQL, I'm pretty rusty. I'm open to suggestions on 
cleaning it up.

[Trac] Trac Account Manager / Tracd / ajp / proxypass / apache

geos_one — 2013-04-25T09:09:44

Hallo i am unable to find the reason for this problem
i get this error when i login to trac that is running via tracd via ajp via 
apache2 
so what could result to this error

i think its a proxy pass related problem but i am unable to find the reason 
any help welcome

the trac.ini is postet there
http://bpaste.net/show/94050/

my apache vhost looks like this

<VirtualHost *:80>
    ServerName opsi.disconnected-by-peer.at
    ServerAdmin mario.fetka-+zpghU0kKgY< at >public.gmane.org
    ErrorLog /var/log/apache2/opsi.disconnected-by-peer.at-error_log
    CustomLog /var/log/apache2/opsi.disconnected-by-peer.at-access_log 
combined
    DocumentRoot /var/www/opsi/htdocs
    ProxyPass         /opsi/  ajp://localhost:8000/opsi/
    RewriteEngine On
    RewriteRule   ^/$  /opsi/  [R]
</VirtualHost>


the error
Oops…
*Trac detected an internal error:*

AssertionError:

There was an internal error in Trac. It is recommended that you notify your 
local Trac administrator with the information needed to reproduce the issue.

To that end, you could  a ticket.

The action that triggered the error was:

POST: /login

[Trac] Plugin Options for Graphics

Ivanelson Nunes — 2013-04-24T00:00:58

I want an option to generate graphs on my wiki pages. I tried using the
TicketChartsMacro [1], but without success. Examples desire:

* Graphics by owner
* By Type
* For Situation (open, closed, etc. ..)
* For owner and situation.

* My trac version 1.0

Note: The plugin "TicketChartMacro" has a TicketCharts.py module that
imports another module "openFlashCharts". Trac can not find this module
"openFlashCharts".

Suggestions?!

Thank you.

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


< at >ivanelson
[]s

[Trac] Versionizing/branching sections of the Wiki

Manuel Holtgrewe — 2013-04-23T18:39:43

Dear all,

the Trac Wiki at trac.edgewall.org uses version namespaces to keep around 
multiple versions of the manual concurrently.

I would like to do the same with tutorials for our software project.

I imaging that copying over the pages manual is pretty tedious. What is the 
best way to copy all pages, say below "Tutorial/", to "/1.4/Tutorial/"? 
Does anyone of you have a script using the HTTP API of Trac, is this best 
done using direct database access, or is there even a plugin for that (I 
could not find any)?

Thanks,
Manuel

[Trac] permission to add ticket-component / versions?

Joost Kraaijeveld — 2013-04-23T16:26:02

Hi,

Is it possible to create a permission that allows an authenticated user
to administer ticket-component and versions without being able to change
the Priorities, Resolutions Severities and Ticket Types? If so how?

TIA

Joost

[Trac] jsgantt day view

Mark Maciolek — 2013-04-22T18:54:10

hi,

When using the jsgantt and viewing a milestone, I can see the Format for 
Week, Month, Qtr display properly.

When I choose the Format day nothing changes in the view it stays showing 
the last Format I chose.

Where in the trac.ini is this Format setup?


Here is my trac.ini

{{{

# -*- coding: utf-8 -*-

[TracPM]
blocking = text
blocking.label = Blocking
complete = select
complete.label = % Complete
complete.options = 
0|5|10|15|20|25|30|35|40|45|50|55|60|65|70|75|80|85|90|95|100
complete.order = 3
date_format = %m/%d/%Y
days_per_estimate = 0.125
default_estimate = 4.0
due_assign = text
due_assign.label = Start (MM/DD/YYYY)
due_assign.order = 1
due_close = text
due_close.label = End (MM/DD/YYYY)
due_close.order = 2
estimate_pad = 0.0
estimatedhours = text
estimatedhours.label = Estimated Number of Hours
estimatedhours.order = 1
estimatedhours.value = 0
fields.estimate = estimatedhours
fields.finish = due_close
fields.parent = parents
fields.pred = blockedby
fields.start = due_assign
fields.succ = blocking
fields.worked = totalhours
goal_ticket_type = milestone
hours = text
hours.label = Add Hours to Ticket
hours.order = 2
hours.value = 0
hours_per_estimate = 1
loe = select
loe.label = Estimate of Effort
loe.options = low|medium|high
loe.value = low
parent_format = %s
parents = text
parents.label = Parent Tickets
prim_developer = select
prim_developer.label = Primary Developer
prim_developer.options = 
na|allison|aracicot|chander|gcorradini|pmc2|rfsl|winkey
test_desc = textarea
test_desc.cols = 80
test_desc.format = wiki
test_desc.label = Testing Instructions
test_desc.rows = 10
totalhours = text
totalhours.label = Total Hours
totalhours.order = 4
totalhours.value = 0

[account-manager]
authentication_url =
db_htdigest_realm =
force_passwd_change = true
hash_method = HtDigestHashMethod
htdigest_realm =
htpasswd_file = /data1/trac/conf/passwd.conf
htpasswd_hash_type = crypt
password_file = /data1/trac/conf/passwd.conf
password_format = htpasswd
password_store = HtPasswdStore
persistent_sessions = False
refresh_passwd = False
user_lock_max_time = 86400
verify_email = true

[attachment]
max_size = 157286400
render_unsafe_content = false

[browser]
downloadable_paths = /trunk, /branches/*, /tags/*
hide_properties = svk:merge
render_unsafe_content = false

[changeset]
max_diff_bytes = 10000000
max_diff_files = 0
wiki_format_messages = true

[components]
acct_mgr.htfile.htdigeststore = disabled
cmtekniktheme.* = enabled
crystalxtheme.* = enabled
githubsimple.* = enabled
mastertickets.* = enabled
skittlishtheme.* = enabled
themeengine.* = enabled
themeengine.admin.themeadminmodule = enabled
themeengine.api.themeenginesystem = enabled
themeengine.web_ui.themeenginemodule = enabled
timingandestimationplugin.* = enabled
trac.web.auth.loginmodule = disabled
tracjsgantt.* = enabled
tracjsgantt.tracjsgantt.tracjsganttchart = enabled
tracjsgantt.tracjsgantt.tracjsganttsupport = enabled
tracjsgantt.tracpm.projectsorter = enabled
tracjsgantt.tracpm.resourcescheduler = enabled
tracjsgantt.tracpm.simplecalendar = enabled
tracjsgantt.tracpm.simplesorter = enabled
tracjsgantt.tracpm.ticketrescheduler = disabled
tracjsgantt.tracpm.tracpm = enabled
tracopt.versioncontrol.git.* = enabled
tracopt.versioncontrol.svn.svn_fs.subversionconnector = enabled
tracopt.versioncontrol.svn.svn_prop.subversionmergepropertydiffrenderer = 
enabled
tracopt.versioncontrol.svn.svn_prop.subversionmergepropertyrenderer = 
enabled
tracopt.versioncontrol.svn.svn_prop.subversionpropertyrenderer = enabled
tracsubtickets.api.* = enabled
tracsubtickets.web_ui.* = enabled

[githubsimple]
browser = http://github.com/noaaerma/erma/commit/
suppress_changesets = true

[header_logo]
alt = ERMA TRAC Site
height = -1
link = https://erma-trac.sr.unh.edu/
src = common/trac_banner.png
width = -1

[logging]
log_file = /data1/trac/logs/trac.log
log_level = ERROR
log_type = file

[mimeviewer]
enscript_modes = text/x-dylan:dylan:4
enscript_path = enscript
max_preview_size = 262124
mime_map = text/x-dylan:dylan,text/x-idl:ice,text/x-ada:ads:adb
php_path = php
silvercity_modes =
tab_width = 8

[notification]
always_notify_owner = true
always_notify_reporter = true
always_notify_updater = true
mime_encoding = base64
smtp_always_bcc =
smtp_always_cc =
smtp_default_domain =
smtp_enabled = true
smtp_from = trac-k4TL3pSa9Rndlda8eOpuOfZ8FUJU4vz8< at >public.gmane.org
smtp_password =
smtp_port = 25
smtp_replyto = trac-k4TL3pSa9Rndlda8eOpuOfZ8FUJU4vz8< at >public.gmane.org
smtp_server = localhost
smtp_subject_prefix = __default__
smtp_user =
use_public_cc = false
use_short_addr = false
use_tls = false

[project]
descr = ERMA Development Site
footer = Visit the Trac open source project at<br /><a 
href="http://trac.edgewall.org/">http://trac.edgewall.org/</a>
icon = common/trac.ico
name = ERMA
url = http://erma-dev.sr.unh.edu./

[repositories]
repository_dir =
repository_type = git

[search]
min_query_length = 3

[theme]
theme = CMTeknik

[ticket]
default_component = ERMA
default_milestone = SONS Drill Items to fix
default_owner = true
default_priority = normal
default_severity = normal
default_type = defect
default_version = 2.0
restrict_owner = true

[ticket-custom]
billable = checkbox
billable.label = Billable?
billable.order = 3
billable.value = 1
blockedby = text
blockedby.label = Blocked By
blocking = text
blocking.label = Blocking
due_assign = text
due_assign.label = Start (MM/DD/YYYY)
due_assign.order = 1
due_close = text
due_close.label = End (MM/DD/YYYY)
due_close.order = 2
estimatedhours = text
estimatedhours.label = Estimated Number of Hours
estimatedhours.order = 1
estimatedhours.value = 0
hours = text
hours.label = Add Hours to Ticket
hours.order = 2
hours.value = 0
parents = text
parents.label = Parent Tickets
totalhours = text
totalhours.label = Total Hours
totalhours.order = 4
totalhours.value = 0

[ticket-workflow]
accept = new,assigned,reopened -> accepted
accept.default = 9
accept.name = Accept this ticket
accept.operations = set_owner_to_self
accept.permissions = TICKET_MODIFY
deploy = accepted,testing -> deploy
deploy.default = 3
deploy.name = Mark ticket for Deployment
deploy.permissions = TICKET_MODIFY
leave = * -> *
leave.default = 10
leave.name = Leave
leave.operations = leave_status
reassign = new,assigned,accepted,reopened,review -> assigned
reassign.default = 1
reassign.name = Reassign
reassign.operations = set_owner
reassign.permissions = TICKET_MODIFY
reassign_deploy = deploy -> accepted
reassign_deploy.default = 1
reassign_deploy.name = Mark ticket back to Accepted
reassign_deploy.permissions = TICKET_MODIFY
reassign_review = review -> accepted
reassign_review.default = 1
reassign_review.name = Mark ticket back to Accepted
reassign_review.permissions = TICKET_MODIFY
reassign_testing = testing -> accepted
reassign_testing.default = 1
reassign_testing.name = Mark ticket back to Accepted
reassign_testing.permissions = TICKET_MODIFY
reopen = closed -> reopened
reopen.operations = del_resolution
reopen.permissions = TICKET_CREATE
resolve = new,assigned,accepted,reopened,review,deploy -> closed
resolve.default = 0
resolve.name = Resolve
resolve.operations = set_resolution
resolve.permissions = TICKET_MODIFY
review = accepted -> review
review.default = 5
review.name = Mark ticket for Review
review.permissions = TICKET_MODIFY
testing = accepted,review -> testing
testing.default = 4
testing.name = Mark ticket for Testing
testing.permissions = TICKET_MODIFY

[timeline]
changeset_long_messages = false
changeset_show_files = 0
default_daysback = 30
ticket_show_details = true

[trac]
authz_file =
authz_module_name =
base_url =
check_auth_ip = true
database = sqlite:db/trac.db
debug_sql = true
default_charset = iso-8859-15
default_handler = WikiModule
htdocs_location =
ignore_auth_case = false
mainnav = wiki,timeline,roadmap,browser,tickets,newticket,search
metanav = login,logout,settings,help,about
permission_store = DefaultPermissionStore
repository_dir = /data1/svn/repos/erma
repository_type = svn
timeout = 20

[trac-jsgantt]
option.caption = Resource
option.colorby = priority
option.comp = 0
option.datedisplay = mm/dd/yyyy
option.dur = 0
option.enddate = 1
option.expandclosedtickets = 1
option.format = month
option.formats = day|week|month|quarter
option.hoursperday = 8.0
option.lwidth = 500
option.omitmilestone = 0
option.openlevel = 0
option.res = 0
option.schedule = asap
option.showdep = 1
option.startdate = 1
option.usermap = 0

[wiki]
ignore_missing_pages = false
render_unsafe_content = false
split_page_names = false
}}}


{{[

 cat /etc/issue
Debian GNU/Linux 6.0 \n \l

sqlite3 --version
3.7.7.1 2011-06-28 

}}}