Re: [Trac] svnauthz (or similar) with MultipleRepositories?
On Mon, Jan 3, 2011 at 7:12 PM, Remy Blank remy.bl...@pobox.com wrote: You don't need a pluign for that. Just add the AuthzSourcePolicy component to [trac] permission_policies, and configure your authz file with [trac] authz_file. In your authz file, use the [repos:/path] syntax to specify permissions for different repositories. Using your description and some effort to fill the information a Trac-Noob needs to be told explicitely, I finally figured it out, so it works. So you don't need a plugin for that should be changed to there is no plugin for that, as svnauthz will only work partially with a multi-repo syntax.. At least my svnauthz plugin cannot cope with the [repos:/path] sections of the authz file. Richard -- 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] Some more 0.12.1 update woes
Hi, in the 2nd week of the ongoing process of updating to 0.12.1, there are some small/medium issues I would like to ask here en bulk for a solution: * We used the Get the red out recipe from http://trac.edgewall.org/wiki/CookBook/SiteStyleCss, but in the source browser, css class pathentry remains reddish no matter what (we do). Is there something somewhere hardcoded? * In our earlier setup (1 SVN - 1 Trac), every commit to SVN got instantly visualized in the source browser/timeline. Now I have to manually issue trac-admin path repository resync SVNREPO, which is quite bad. The idea to put this command into post-hook is also quite bad (every post-hook will get slower and slower). There must be an at least as elegant as before way - howto? * We used in trac.ini the i18n configuration to change date time to a more sane format: [i18n] date_format = %Y-%m-%d datetime_format = %Y-%m-%d %H:%M:%S time_format = %H:%M:%S It seems to be completely ignored now. How do I get rid of the horror that is MM/DD/? * On a related note: I assume there has accumulated lots of cruft in our trac.ini (read in the .ini of the last remaining - consolidated - trac), is there any way to find out what of this isn't used anymore? Thanks! Richard -- 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] Some more 0.12.1 update woes
Hi Richard,
[...]
* On a related note: I assume there has accumulated lots of cruft in
our trac.ini (read in the .ini of the last remaining - consolidated -
trac), is there any way to find out what of this isn't used anymore?
i recently ran into the same problem. My solution was to merge the old
configuration from Trac 0.10.4 into a default sample configuration from
0.12.1 and then manually reduce the overhead
HTH
~eike
#== merge.py ==
import os
import glob
from ConfigParser import ConfigParser
# new default configuration from 0.12.1
sample = /tmp/sample/conf/trac.ini
# path to 0.10.4 environments
basedir = /var/trac/environments
ini_files = glob.glob(basedir + '/*/conf/trac.ini')
write sorted configuration to file,
if specified, appends extension to file name
def write(file, extension, config):
if extension != '':
file += . + extension
try:
out = open(file, w)
out.write('# -*- coding: utf-8 -*-\n\n')
for section in sorted(config.sections()):
out.write('[%s]\n' % section)
for option in config.options(section):
value = config.get(section, option)
value = value.replace('\r\n', '\n').replace('\n', '\n ')
out.write('%s = %s\n' % (option, value))
out.write('\n')
except Exception:
raise
Compares to configurations. Differences in section or
option will be merged from config_1 to config_2.
Conflicts are treated in such a way, that an affected option
from config_2 will be written as a comment.
Returns the merged configuration.
def merge(config_1, config_2):
for section in sorted(config_1.sections()):
if ( not config_2.has_section(section)):
config_2.add_section(section)
for option in sorted(config_1.options(section)):
if (config_2.has_option(section, option)):
value = config_2.get(section, option)
config_2.remove_option(section, option)
config_2.set(section, # + option, value)
config_2.set(section, option, config_1.get(section, option))
return config_2
default = ConfigParser()
default.read(sample)
# backup normalized sample
write(sample, '0.12.1', default)
for file in ini_files:
print file
config = ConfigParser()
config.read(file)
# backup normalized 0.10.4 configuration
write(file, 0.10.4, config)
config_merged = merge(config, default)
write(file, 0.12.1, config_merged)
# EOF
--
Eike Jordan jor...@fiz-chemie.de
| FIZ CHEMIE BERLIN
| Franklin Str. 11 --,__o
| 10587 Berlin -- _-\_,
| -- (+)/'(+)
| Tel. : 0049-30-39977 214
--
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] Cannot marshal Empty class using Mylyn
Hi. I'm using Eclipse Mylyn with the Trac connector. Recently I noticed this warning: cannot marshal class 'trac.util.text.Empty' objects while executing 'ticket.get()' Searching for this warning I found a patch for postgres that was already checked in, my installation however is using Mysql and, if I'm not wrong, the issue was not fixed for that database. Is there a patch somewhere that fixes this issue ? I'm using Trac 0.12.1. Regards, Marco. -- 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] Trac notifications 'from' field
Hello, I would like to have the notifications from field modified so it contains the username that's creating/updating a ticket. From trac.ini this is: [notification] ... smtp_from_name = ... I've tried using $USER, $USERNAME and other variables but none of them seems to be expanded, not even one. I believe no variables are being expanded for this setting so I don't know how to accomplish this, any ideas? Thanks in advance! 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.
[Trac] Re: Cannot marshal Empty class using Mylyn
On Jan 10, 4:49 pm, Marco Maccaferri ma...@maccasoft.com wrote:
Hi.
I'm using Eclipse Mylyn with the Trac connector. Recently I noticed this
warning:
cannot marshal class 'trac.util.text.Empty' objects while executing
'ticket.get()'
Searching for this warning I found a patch for postgres that was already
checked in, my installation however is using Mysql and, if I'm not
wrong, the issue was not fixed for that database. Is there a patch
somewhere that fixes this issue ?
I'm using Trac 0.12.1.
Regards,
Marco.
The issue is that the DB query returns Empty class to signify
difference from empty string ('') and similar, and that the RPC
protocol like XML-RPC and JSON-RPC need to be aware of this special
class to marshal it to empty value. Recent versions of the RPC plugin
should be aware.
Are you using latest version from svn trunk? See here for details of
how to get latest source version installed - and link to creating new
ticket if the problem persists.
http://trac-hacks.org/wiki/XmlRpcPlugin
:::simon
--
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] Trac notifications 'from' field
Francisco Puente wrote: I would like to have the notifications “from” field modified so it contains the username that’s creating/updating a ticket. Coming shortly: http://trac.edgewall.org/ticket/8360 -- Remy signature.asc Description: OpenPGP digital signature
