[Trac] Trac 0.11rc1 Released
Trac 0.11rc1
We now have a first release candidate for the much awaited Trac 0.11.
You will find this release at the usual place:
http://trac.edgewall.org/wiki/TracDownload
Here are some of the features you can expect from this version:
* New template engine for generating content (Genshi)
* New configurable workflow in the ticket subsystem
* Finer-grained control of permissions
* Support for Pygments as the default syntax highlighter
* Improved repository browser ("blame" support, dynamic in-place
expansion of folders)
* Improved user preferences subsystem, among which the possibility
for any user to select their time zone and disable access keys
* The WebAdmin plugin is now an integral part of Trac
You can find a more detailed release note at:
http://trac.edgewall.org/wiki/TracDev/ReleaseNotes/0.11
Acknowledgements
Many thanks to the growing number of people who have, and continue to,
support the project. Also our thanks to all people providing feedback
and bug reports that helps us make Trac better, easier to use and more
effective.
Without your invaluable help, Trac would not evolve. Thank you all.
Finally, we offer hope that Trac will prove itself useful to like-
minded programmers around the world, and that this release will prove an
improvement over the last version.
Please let us know. :-)
/The Trac Team http://trac.edgewall.org/
--~--~-~--~~~---~--~~
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 email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---
[Trac] Re: Milestone ticket status by bug?
Christian Boos wrote: > > Jani Tiainen wrote: >> When selecting ticket status by 'Reporter' in milestone view doesn't do >> nothing at t.e.o. I was just wondering is this generic bug or feature of >> t.e.o. itself... >> >> All other options seem to work. >> >> And further investigation revelead that it works in IE 7 but not in FF >> 2.0.0.14 >> > > We're aware of the issue, it's a local configuration problem, see > http://trac.edgewall.org/ticket/7154 Sorry about the delay, it should be fixed now. / Jonas --~--~-~--~~~---~--~~ 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 email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Trac 0.11rc2 Released
Trac 0.11rc2
We now have a second release candidate for the much awaited Trac 0.11.
You will find this release at the usual place:
http://trac.edgewall.org/wiki/TracDownload
Here are some of the features you can expect from this version:
* New template engine for generating content (Genshi)
* New configurable workflow in the ticket subsystem
* Finer-grained control of permissions
* Support for Pygments as the default syntax highlighter
* Improved repository browser ("blame" support, dynamic in-place
expansion of folders)
* Improved user preferences subsystem, among which the possibility
for any user to select their time zone and disable access keys
* The WebAdmin plugin is now an integral part of Trac
You can find a more detailed release note at:
http://trac.edgewall.org/wiki/TracDev/ReleaseNotes/0.11
Acknowledgements
Many thanks to the growing number of people who have, and continue to,
support the project. Also our thanks to all people providing feedback
and bug reports that helps us make Trac better, easier to use and more
effective.
Without your invaluable help, Trac would not evolve. Thank you all.
Finally, we offer hope that Trac will prove itself useful to like-
minded programmers around the world, and that this release will prove an
improvement over the last version.
Please let us know. :-)
/The Trac Team http://trac.edgewall.org/
--~--~-~--~~~---~--~~
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 email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---
[Trac] Re: TraceError Ubuntu
Jann wrote: > > Has anyone experience this problem: > > Traceback (most recent call last): > File "/var/lib/python-support/python2.5/trac/web/main.py", line 406, > in dispatch_request > dispatcher.dispatch(req) > File "/var/lib/python-support/python2.5/trac/web/main.py", line 206, > in dispatch > req.hdf = HDFWrapper(loadpaths=chrome.get_all_templates_dirs()) > File "/var/lib/python-support/python2.5/trac/web/clearsilver.py", > line 135, in __init__ > raise TracError, "ClearSilver not installed (%s)" % e > TracError: ClearSilver not installed (/usr/lib/python2.5/site-packages/ > neo_cgi.so: undefined symbol: Py_InitModule4) This seems to be a known ubuntu hardy x86_64 problem: https://bugs.launchpad.net/ubuntu/+source/clearsilver/+bug/86685 / Jonas --~--~-~--~~~---~--~~ 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 email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] SECURITY: Trac 0.10.5 Released
Release Notes for Trac 0.10.5 = June 22, 2008 (Note: Trac 0.11 will also be released later today) We're happy to announce the Trac 0.10.5 release, available from: http://trac.edgewall.org/wiki/TracDownload For questions, comments and user discussions, please use the Trac mailing list. List information, subscription and archive available at: http://trac.edgewall.org/wiki/MailingList Trac 0.10.5 contains two security fixes and a couple of bug fixes. The following list contains only a few highlights: * Fixes a cross-site redirection vulnerability in the quickjump function reported by Russ McRee. * Fixes a wiki engine XSS vulnerability found by Nathan Collins. * Added PostgreSQL 8.3 support. * Fixes FineGrainedPermissions for scoped repositories. * Fixes problem with repository syncing raising exceptions. The complete list of closed tickets can be found here: http://trac.edgewall.org/query?status=closed&milestone=0.10.5 Acknowledgements Many thanks to the growing number of people who have, and continue to, support the project. Also our thanks to all people providing feedback and bug reports that helps us make Trac better, easier to use and more effective. Without your invaluable help, Trac would not evolve. Thank you all. Finally, we offer hope that Trac will prove itself useful to like-minded programmers around the world, and that this release will prove an improvement over the last version. Please let us know. :-) /The Trac Team http://trac.edgewall.org/ --~--~-~--~~~---~--~~ 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 email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Trac 0.11 Released
Trac 0.11
=
We're happy to announce the much awaited Trac 0.11 release.
You will find this release at the usual place:
http://trac.edgewall.org/wiki/TracDownload
Here are some of the features you can expect from this version:
* New template engine for generating content (Genshi)
* New configurable workflow in the ticket subsystem
* Finer-grained control of permissions
* Support for Pygments as the default syntax highlighter
* Improved repository browser ("blame" support, dynamic in-place
expansion of folders)
* Improved user preferences subsystem, among which the possibility
for any user to select their time zone and disable access keys
* The WebAdmin plugin is now an integral part of Trac
You can find a more detailed release note at:
http://trac.edgewall.org/wiki/TracDev/ReleaseNotes/0.11
Acknowledgements
Many thanks to the growing number of people who have, and continue to,
support the project. Also our thanks to all people providing feedback
and bug reports that helps us make Trac better, easier to use and more
effective.
Without your invaluable help, Trac would not evolve. Thank you all.
Finally, we offer hope that Trac will prove itself useful to like-
minded programmers around the world, and that this release will prove an
improvement over the last version.
Please let us know. :-)
/The Trac Team http://trac.edgewall.org/
--~--~-~--~~~---~--~~
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 email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---
[Trac] Re: Trac and PostgreSQL DB
Reynier Perez Mira wrote: > > Hi every: > I try to run Trac with PostgreSQL Database. For that I check all this links: > * http://trac.edgewall.org/wiki/TracInstall > * http://trac.edgewall.org/wiki/DatabaseBackend#Postgresql( > * http://www.egenix.com/products/python/mxBase/ > > When I run trac-admin init env I get all this errors: What did the connection string look like? / Jonas --~--~-~--~~~---~--~~ 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 email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: TRAC_DB_POOL_SIZE in 0.11?
Russ Brown wrote: > Not long back I switched from the prefork apache MPM to the worker one, > at the suggestion of coderanger (due to better memory efficiency etc). I > set it up to run on two processes each spawning a number of threads. > > Yesterday we encountered Trac being unable to connect to the database > (Postgres 8.2, Trac 0.11 RC2), and when investigating it noticed that > trac only had two connections open (two large requests were being > processed at this time leading to the site being unavailable to other > requests). Did you get a "Unable to get database connection within 20 seconds"-error or something else? The exact traceback would also be interesting. > I asked about this in IRC and was told that there were issues with the > pooling in RC2 and that I should upgrade to 0.11. coderanger also > mentioned the TRAC_DB_POOL_SIZE environment variable which could be used > to control the connection pooling. The connection currently in 0.11 is limited to 5 connections per environment per apache process. So as far as I can tell you should be able to get up to 10 concurrent requests with your setup, and certainly more than 2. > I did that, but Trac still only held two connections open. I viewed > trac/db/pool.py and saw no mention of TRAC_DB_POOL_SIZE. Looking at the > file on trunk (of t.e.o) I do see it there, which suggests that > TRAC_DB_POOL_SIZE was actually added post 0.11. I also don't see it in > that file on the 0.11-stable branch. > > Is there any estimate as to when this change might be released (e.g. > 0.11.1)? Yes, it's planned for 0.11.1. If you want to test it now all you need to do is to download and replace pool.py from trunk: http://svn.edgewall.org/repos/trac/branches/0.11-stable/trac/db/pool.py / Jonas --~--~-~--~~~---~--~~ 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 email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: [newbie] Pb with Image macro and onclick
Pechoultres Xavier wrote: > > Hello, I've resolved my problem by creating a custom marco, hacked > from trac Image macro. > > it may be usefull to be able to add ja event handler to Image macro. Useful perhaps, but extremely dangerous since this opens up Trac for XSS attacks. Malicious users could use this feature to for example inject javascript code that steals other users trac sessions and bypass the security system. http://en.wikipedia.org/wiki/Cross-site_scripting / Jonas --~--~-~--~~~---~--~~ 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 email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: New Trac User. Confused about Links.
slade867 wrote: > > Actually, I'm confused about a ,lot of things and will probably have > many questions. Here's my first one > > How do I make it so that a CamelCase word is not considered a page > link? > > For example suppose I want to say "The name of the class is 'ThisName' > ". I don't want "ThisName" to be a link to a wiki page and have a > question mark after it. > > I still want to be able to use the CamelCase as usual for other > instances, just not thi specific one. http://trac.edgewall.org/wiki/WikiFormatting#Links / Jonas --~--~-~--~~~---~--~~ 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 email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Trouble upgrading to .11
bduke wrote: > > Hi, I have a 10.4 installation working fine on a Windows server. I'm > trying to upgrade to .11 and getting an error when I run trac-admin. > To upgrade, I ran the setuptools, then genshi, then trac-0.11 > installers in that order. After that I tried to run the trac-admin > upgrade like this: > > python c:\python24\scripts\trac-admin.py c:\svn\trac.db upgrade > > I get this output: > > Traceback (most recent call last): > File "c:\python24\scripts\trac-admin.py", line 21, in ? > from trac.scripts.admin import run > File "c:\python24\lib\site-packages\trac\scripts\admin.py", line 28, > in ? > from trac.config import default_dir > ImportError: cannot import name default_dir > > Could someone help me with what step I'm missing? I think this traceback is actually from Trac 0.10.4 and not 0.11. Try to completely uninstall/remove your previous version of Trac and then reinstall 0.11. / Jonas --~--~-~--~~~---~--~~ 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 email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: AttributeError: 'module' object has no attribute 'ChangeSet'
Stodge wrote:
>
> I just installed Trac 0.11.1 on Centos 5.2. I configured Apache
> (mod_python) and restarted and all looks ok. I can browse
> http://localhost/trac
> and I see:
>
> Available Projects
>
> * .egg-cache: Error
> ('module' object has no attribute 'ChangeSet')
This should be fixed by [7481] which will be included in the upcoming
Trac 0.11.2 release. Until as a workaround you can first remove the
".egg-cache" directory and then point the PYTHON_EGG_CACHE variable on a
directory outside TRAC_ENV_PARENT_DIR.
Exactly how to set this variable depends on which frontend you're using.
But the syntax should be the same as for TRAC_ENV_PARENT_DIR.
http://trac.edgewall.org/changeset/7481
> I get en exception when I run trac-admin with no parameters:
*snip*
> from trac.ticket.model import *
> AttributeError: 'module' object has no attribute 'ChangeSet'
This looks strange, the Trac source code does not contain the string
"ChangeSet" (with a capital S) at all. Which plugins do you have
installed?
/ Jonas
--~--~-~--~~~---~--~~
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 email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---
[Trac] Re: PYTHON_EGG_CACHE setting always ignored
Stodge wrote: > > I'm having problems with PYTHON_EGG_CACHE on Centos 5.2 with Trac 0.11 > and 0.11.1. > > No matter what I set PYTHON_EGG_CACHE to, and no matter where I set > it, it's always ignored and the cache is always in /root/. > > I noticed that the TracPython page states that mod_python 3.3 is > required for the cache to work properly, but Centos 5.2 only includes > 3.2. Could someone verify that mod_python v3.3 IS absolutely required > for Trac to work without egg cache errors? No, mod_python 3.2 should work just fine. 3.3 was required for a few days during the 0.11.1 development but we've switched to a different approach. I've removed that from the wiki page. Do you setting the variable using PythonOption or SetEnv? Both are supposed to work but I'm sure PythonOption works. / Jonas --~--~-~--~~~---~--~~ 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 email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: "'NoneType' object is not callable" in
stefano wrote: > > Hi, > > I wrote a script where I open a connection to the db, fetch some info > from there and then close the connection. > > The script worked for almost 2 years without any prob but recently it > started producing this warning: > > Exception exceptions.TypeError: "'NoneType' object is not callable" in > > ignored > > > It happens exactly when I do cursor.close(). > > I suspect a db corruption somehow but I have no idea how to find it / > fix it. We'll need some more information to figure out what's happening here: 1. What version of Trac are you using? 2. What database are you using? 3. Did you upgrade Trac or any other dependency what this started happening? / Jonas --~--~-~--~~~---~--~~ 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 email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] New SSL cert for svn.edgewall.org
Hi, The SSL certificate for svn.edgewall.org expired and has been replaced with a new certificate. Fingerprints: SHA1: 16 6B 09 E6 89 67 A2 99 9A A3 AA F5 D8 6F 40 5B AF A9 33 6F MD5: BF D2 CF 99 7E 4C 5D 37 BF FD CA 91 66 28 12 89 / Jonas Btw, Godaddy is currently offering free SSL certificates for Open Source projects: http://godaddy.com/gdshop/ssl/ssl_opensource.asp --~--~-~--~~~---~--~~ 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 email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Ticket corruption?
David Starr wrote: > > Hi all.. > > We have many tickets in our sqlite db... (almost 2000) and now > experiencing at least one ticket which Trac refuses to load (times out). > > Any ideas how to diagnose and repair this ticket? I'm not quite sure > where to start. I can still see the history inside it using > TicketDeletePlugin. Did you notice any weird ticket comments or similar when looking at the ticket history? Reproducing the timeout using the standalone server tracd might give you some more details. To rule out actual database corruption you can always "reload" the database like this: $ mv db/trac.db db/trac.db.old $ sqlite3 db/trac.db.old .dump | sqlite3 db/trac.db .load / Jonas --~--~-~--~~~---~--~~ 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 email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: occasional database error
Greg Troxel wrote:
> Occasionally ticket queries fail with a database error:
>
> Oops#
> Trac detected an internal error:
>
> OperationalError: ERROR: duplicate key violates unique constraint
> "session_attribute_pk"
Hi Greg,
It appears to be a small window of opportunity for two concurrent
requests from a single user to cause this constraint violation in
session.py.
I have attached a patch which I think will fix this which I'm currently
testing. If you have the opportunity please give it a try as well.
/ Jonas
--~--~-~--~~~---~--~~
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 email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---
Index: trac/web/session.py
===
--- trac/web/session.py (revision 7647)
+++ trac/web/session.py (working copy)
@@ -93,8 +93,15 @@
(self.sid, e))
if self._old != self:
attrs = [(self.sid, authenticated, k, v) for k, v in self.items()]
-cursor.execute("DELETE FROM session_attribute WHERE sid=%s",
- (self.sid,))
+try:
+cursor.execute("DELETE FROM session_attribute WHERE sid=%s",
+ (self.sid,))
+# The session variables might already have been updated by a
+# concurrent request.
+except Exception, e:
+db.rollback()
+self.env.log.warning('Attributes for session %s already
updated: %s' %
+ (self.sid, e))
self._old = dict(self.items())
if attrs:
cursor.executemany("INSERT INTO session_attribute "
[Trac] Re: problem upgrading plugin to 0.11 - TypeError: can't compare
.M. wrote: > > Hi > > Can I get some help upgrading my plugin to trac 0.11 from trac 0.10? > > I'm getting this error - TypeError: can't compare datetime.datetime to > int > > Not sure where to change type in this case and unclear what the > revised API is doing now that requires this. As of 0.11 Trac internally only deals with timestamps as real datetime objects instead of integers. So whenever you're fetching a timestamp from the database you'll need to convert it into a datetime object like this: from trac.util.datefmt import utc from datetime import datetime date = datetime.fromtimestamp(ts, utc) / Jonas --~--~-~--~~~---~--~~ 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 email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: occasional database error
Greg Troxel wrote:
> I don't quite understand what is going on. I think the error happened
> on the INSERT, but on reflection this is because of two similar
> transactions:
>
> delete foo if foo is there
> insert bar
>
> and the point is that the delete doesn't fail. Your patch is to try to
> catch the delete failing, and skip the insert. But I would expect the
> delete to return DELETE 0, which doesn't seem like an error:
>
> trac-redacted2=# delete from session_attribute where sid = 'no-such-user';
> DELETE 0
>
> Is this because we are running read committed instead of full
> transactions? We are having the second transaction to do the insert see
> database state from before the first insert is committed.
Yes you're right. It's the INSERT statement and not the DELETE statement
that might fail if another transaction manages to execute and commit
between the DELETE and INSERT of the first transaction (if read
committed is being used).
I somehow managed to wrap the wrong cursor.execute statement with an
exception handler.
I've attached an updated version of the patch.
Thanks for spotting this!
/ Jonas
--~--~-~--~~~---~--~~
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 email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---
Index: trac/web/session.py
===
--- trac/web/session.py (revision 7647)
+++ trac/web/session.py (working copy)
@@ -97,9 +97,16 @@
(self.sid,))
self._old = dict(self.items())
if attrs:
-cursor.executemany("INSERT INTO session_attribute "
- "(sid,authenticated,name,value) "
- "VALUES(%s,%s,%s,%s)", attrs)
+# The session variables might already have been updated by a
+# concurrent request.
+try:
+cursor.executemany("INSERT INTO session_attribute "
+ "(sid,authenticated,name,value) "
+ "VALUES(%s,%s,%s,%s)", attrs)
+except Exception, e:
+db.rollback()
+self.env.log.warning('Attributes for session %s already '
+ 'updated: %s' % (self.sid, e))
elif not authenticated:
# No need to keep around empty unauthenticated sessions
cursor.execute("DELETE FROM session "
[Trac] Re: occasional database error
Christian Boos wrote: > I also wondered a bit about that DELETE... thought there was something > special going on ;-) Heh not really, just sloppiness on my part ;) I didn't even realize the patch was fubared until I read Greg's response. > So, I think it's just another symptom of #3563, and we can track this > defect in http://trac.edgewall.org/ticket/7663. > Another last minute candidate for 0.11.2 in case everything works fine > with the patch? Probably, I'm currently testing it on t.e.o which before this patch did hit this issue about once or twice a day. / Jonas --~--~-~--~~~---~--~~ 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 email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: occasional database error
Greg Troxel wrote: > Thanks, will apply and rebuild. > > Should we be thinking about setting backends to use full transactions > instead of READ COMMITTED, as in > > set transaction ISOLATION LEVEL SERIALIZABLE ; > > perhaps only for such operations, but maybe for more? Not unless we really have to since that will bring the PostgreSQL concurrency level down to something close to sqlite. If this really happens frequent enough to be an issue (which I don't think it is) we should instead rewrite the session code to be smarter about updating session attributes. Instead of deleting all attributes and inserting them again as soon as some attribute is updated we should try to update only actually modified attributes. This would reduce the risk of causing a conflict. / Jonas --~--~-~--~~~---~--~~ 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 email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: "Failure sending notification on change to ticket #6:
marten wrote:
>
> When I create a ticket or comment on a ticket, I'm expecting an email
> to be sent (see trac.ini below). However, that never happens. In the
> log I find this:
>
> Trac[web_ui] ERROR: Failure sending notification on change to ticket
> #6: 'NoneType' object has no attribute 'find' Traceback (most recent
> call last): File "/usr/lib/python2.5/site-packages/Trac-0.11.1-
> py2.5.egg/trac/ticket/web_ui.py", line 992, in _do_save
> tn.notify(ticket, newticket=False, modtime=now) File "/usr/lib/
> python2.5/site-packages/Trac-0.11.1-py2.5.egg/trac/ticket/
> notification.py", line 140, in notify 'ticket_props':
> self.format_props(), File "/usr/lib/python2.5/site-packages/
> Trac-0.11.1-py2.5.egg/trac/ticket/notification.py", line 159, in
> format_props if fval.find('\n') != -1: AttributeError: 'NoneType'
> object has no attribute 'find'
>
> What does this mean? Any ideas what's wrong here?
Do you have any plugins enabled and/or are you using any custom ticket
fields?
My guess is that there are some NULL values in your ticket_custom table
for some reason, which trac/ticket/notification.py didn't expect.
If you can, please test the following patch for trac/ticket/model.py
which might help:
http://pastebin.ca/1247150
/ Jonas
--~--~-~--~~~---~--~~
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 email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---
[Trac] SECURITY: Trac 0.11.2 Released
Trac 0.11.2 === We're happy to announce the Trac 0.11.2 release. You will find this release at the usual place: http://trac.edgewall.org/wiki/TracDownload 0.11.2 is a new stable maintenance release. It contains several security fixes and everyone is recommended to upgrade their installations. Bug fixes: * Fixes potential DOS vulnerability with certain wiki markup. Reported by Matt Murphy. * Improved HTML sanitizer filter to detect possible phishing attempts. Reported by Simon Willison. * MySQL db backend improvement (reconnect after idle timeout #4465) * TicketQuery speed improvements (#6436) * Fixes for RSS feeds (timeline entries no longer truncated #7316, no longer download some feeds under Firefox #3899) * Search now works for custom fields (#2530) * Same order for ticket fields for new and existing tickets (#7018) * Enforce fine-grained permission for "quickjump" search results (#7655) * E-mail obfuscation was not done in a few remaining places (#7688, #6532) * Uninstall of plugins from WebAdmin was not working - feature disabled for now * More robust pagination of results for reports and custom queries (#7424, #7544) * Support for newer version of pygments (#7622) * Documentation updated (#7603, #7205, #7318) Minor improvements: * Better support for Wiki page hierarchy (show path #2780, link to parent #2150) * Custom query allow to search in description and other text fields (#4824) You can find a more detailed release note at: http://trac.edgewall.org/wiki/TracDev/ReleaseNotes/0.11 Acknowledgements Many thanks to the growing number of people who have, and continue to, support the project. Also our thanks to all people providing feedback and bug reports that helps us make Trac better, easier to use and more effective. Without your invaluable help, Trac would not evolve. Thank you all. Finally, we offer hope that Trac will prove itself useful to like- minded programmers around the world, and that this release will prove an improvement over the last version. Please let us know. :-) /The Trac Team http://trac.edgewall.org/ --~--~-~--~~~---~--~~ 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 email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Trac 0.11.2.1 Released
Trac 0.11.2.1 = We're happy to announce the Trac 0.11.2.1 release. You will find this release at the usual place: http://trac.edgewall.org/wiki/TracDownload Trac 0.11.2.1 fixes a Python 2.3 incompatibility introduced 0.11.2. Python 2.4+ users already running Trac 0.11.2 do not need to upgrade. You can find a more detailed release note at: http://trac.edgewall.org/wiki/TracDev/ReleaseNotes/0.11 Acknowledgements Many thanks to the growing number of people who have, and continue to, support the project. Also our thanks to all people providing feedback and bug reports that helps us make Trac better, easier to use and more effective. Without your invaluable help, Trac would not evolve. Thank you all. Finally, we offer hope that Trac will prove itself useful to like- minded programmers around the world, and that this release will prove an improvement over the last version. Please let us know. :-) /The Trac Team http://trac.edgewall.org/ --~--~-~--~~~---~--~~ 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 email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: The ordinal 284 could not be located in the dynamic link
Gaz wrote: > > > Hi there I am trying to install trac using Postres. > > I am using Python 2.4, trac 0.11.2.1, psycopg 2-2.0.8, Postgres 8.3 > > After installing everything, I tried to create a new environment using > the following connection string: > > postgres://User:[EMAIL PROTECTED]:5432/TracDB > > I get an error pop up with : > > The ordinal 284 could not be located in the dynamic link library > SSLEAY32.dll > > When I hit ok on the pop up a message in the command prompt says: *snip* > I thought pyPgSQL was separate to psycopg, does pyPgSQL need to be > installed as well. Trac prefers psycopg2 and only attempts to import pyPgSQL if it failed to import psycopg2 for some reason. Try typing "import psycopg2" manually into a python interpreter to see if that works or gives any usable error message. / Jonas --~--~-~--~~~---~--~~ 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 email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Code for the edgewall.org site?
Steve Roussey wrote: > > Is there code available for how the multiple trac install was setup > there with the tabs for "Trac", "Bitten", etc. It is much easier to > start from a sample... The tabs are created by a single site.html template shared by all projects: http://pastebin.com/f43096b9a It works pretty well but it requires some manual updates every time a new project is added. / Jonas --~--~-~--~~~---~--~~ 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 email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Problem setting up track with Apache 2.2
Hendrik Maryns wrote: >> > P.S. Is there some way to follow this group in a proper mail/news >> > reader, such as via Gmane? I’d rather not get all the mails but view >> > it in a usenet-like fashion. >> >> Have you tried: >> >> http://groups.google.com/group/trac-users > > Um, yes, that is exactly what I *do not* want to do. I want to access > them through Thunderbird, as a newsgroup, Usenet-like. Have you checked gmane? Both lists should be there. / Jonas --~--~-~--~~~---~--~~ 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 email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: prob with milestone names containing \r
julien.lesommer wrote: > Hi, > > I have trouble with a milestone whose name seem to be cause problem to > trac. > The milestone is visible on the raodmap and with trac-admin milestone > list > but no url seem to be associated with the link provided on the roadmap > which returns > the following message : > Milestone WP3: Large scale impact of eddy forcing and lateral stirring > does not exist. > > I would like to delete this milestone but I just can't provide a valid > name to trac-admin. > > any guess of how I could proceed ? One option is to update the database directly: (just remember to backup your database before you start) UPDATE milestone SET name='New name' WHERE name LIKE 'WP3%'; UPDATE ticket SET milestone='New name' WHERE milestone LIKE 'WP3%'; btw, how did you manage to create that milestone in the first place? / Jonas --~--~-~--~~~---~--~~ 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 email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Missing users in dropdowns
Emmanuel Blot wrote: > >> As I know you need to config trac environment for dropdowns after that users >> (which you have added) must log in once into the trac. > > Unfortunately, it is required but not sufficient: each user should > have made some modification - such as changing their trac preferences > or created a ticket - in order to appear in the drop-down list... Visiting the timeline page should also so it since it stores some settings in the session. / Jonas --~--~-~--~~~---~--~~ 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 email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: external access
Mads Pedersen wrote: > > I have installed trac on a linux box and its working great from the > internal network (http://10.0.0.7:8000). > > I have a static external ip address 127.236.237.47 and have setup the > router NAPT to forward all traffic on port 8000 to 10.0.0.7. > > The problem is that the browser won't load http://127.236.237.47:8000 You'll have to verify that the port forwarding is correctly configured and working. You shouldn't really need to configure tracd any differently to get a simple port forwarding setup to work. / Jonas --~--~-~--~~~---~--~~ 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 email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Is there a size limit to the Trac.ini file
Aron wrote: > > I am new to this group, and I tried to search for my question here but > could not find an answer, so here is my question: > > Is there a size limit to the Trac.ini file? > I have a [ticket-custom] area in the trac.ini file that is pretty big > and it seems like I have hit the limit now. Each time I try to add > more to the [ticket-custom] area now, Trac will crash. Not that I know of. Do you have any more details about the "crash" such as tracebacks, error messages etc? / Jonas --~--~-~--~~~---~--~~ 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 email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Trac 0.11.3 Released
Trac 0.11.3 === We're happy to announce the Trac 0.11.3 release. You will find this release at the usual place: http://trac.edgewall.org/wiki/TracDownload Trac 0.11.3 contains a number of bug fixes and minor enhancements. The following list contains only a few highlights: * Compatibility with Python 2.6 (#7876, #7458) * PostgreSQL db backend improvement (#4987, #7600) * Highlighting of search results is more robust (#7324, #7830) * Unicode related fixes (#7672, #7959, #7845, #7935, #8024) * Fixed Trac link rendering in ReST (#7712) You can find a more detailed release note at: http://trac.edgewall.org/wiki/TracDev/ReleaseNotes/0.11 Acknowledgements Many thanks to the growing number of people who have, and continue to, support the project. Also our thanks to all people providing feedback and bug reports that helps us make Trac better, easier to use and more effective. Without your invaluable help, Trac would not evolve. Thank you all. Finally, we offer hope that Trac will prove itself useful to like- minded programmers around the world, and that this release will prove an improvement over the last version. Please let us know. :-) /The Trac Team http://trac.edgewall.org/ --~--~-~--~~~---~--~~ 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 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 0.11.4rc1 Released
Trac 0.11.4rc1 (Release Candidate 1) This is the first and hopefully final release candidate for the upcoming 0.11.4 release. You will find this release at the usual place: http://trac.edgewall.org/wiki/TracDownload Trac 0.11.4rc1 contains a number of bug fixes and minor enhancements. The following list contains only a few highlights: * Fixed Python 2.3 incompatibility (#8061) * Fixed Python 2.6 notification issue (#8083) * Fixed PostgreSQL multi column index issue (#7600) You can find a more detailed release note at: http://trac.edgewall.org/wiki/TracDev/ReleaseNotes/0.11 Acknowledgements Many thanks to the growing number of people who have, and continue to, support the project. Also our thanks to all people providing feedback and bug reports that helps us make Trac better, easier to use and more effective. Without your invaluable help, Trac would not evolve. Thank you all. Finally, we offer hope that Trac will prove itself useful to like- minded programmers around the world, and that this release will prove an improvement over the last version. Please let us know. :-) /The Trac Team http://trac.edgewall.org/ --~--~-~--~~~---~--~~ 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 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: Installation, FATAL: database "trac" does not exist
On 3/22/09 8:21 AM, ray wrote: > I am trying to install trac in Windows using PostgreSQL and SVN. > Python 2.5 is installed, as is PostgreSQL 8.3. When I first ran C: > \Python25\Scripts\trac-admin C:\trac initenv, it failed on "pyPgSQL". > I performed an install of "psycopg2". > > I ran the initenv again but it saw that the c:trac was all ready > initialized and would not progress. So I renamed it to C:tracOLD and > ran initenv again where the following was produced: > > Creating and Initializing Project > Initenv for 'C:\trac' failed. > Failed to create environment. > FATAL: database "trac" does not exist *snip* > OperationalError: FATAL: database "trac" does not exist > > I have no idea what database "trac" is. I tried naming a PostgreSQL > server "trac" but that didn't help. What should I be doing to get > this working? What "Database connection string" did you use when running "initenv"? When using PostgreSQL initenv expects that the database specfied in the connection string already exists and is empty. http://trac.edgewall.org/wiki/DatabaseBackend#Postgresql / Jonas --~--~-~--~~~---~--~~ 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 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 0.11.4rc2 Released
Trac 0.11.4rc2 (Release Candidate 2) This release candidate addresses one regression found in rc1. Trac 0.11.4 (final) is scheduled for release on Monday, 03/30. You will find this release at the usual place: http://trac.edgewall.org/wiki/TracDownload Bugs fixed in this release -- * Custom mainnav links regression (#8153) You can find a more detailed release note at: http://trac.edgewall.org/wiki/TracDev/ReleaseNotes/0.11 Acknowledgements Many thanks to the growing number of people who have, and continue to, support the project. Also our thanks to all people providing feedback and bug reports that helps us make Trac better, easier to use and more effective. Without your invaluable help, Trac would not evolve. Thank you all. Finally, we offer hope that Trac will prove itself useful to like- minded programmers around the world, and that this release will prove an improvement over the last version. Please let us know. :-) /The Trac Team http://trac.edgewall.org/ --~--~-~--~~~---~--~~ 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 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 0.11.4 Released
Trac 0.11.4 === We're happy to announce the Trac 0.11.4 release. You will find this release at the usual place: http://trac.edgewall.org/wiki/TracDownload Trac 0.11.4 contains a number of bug fixes and minor enhancements. The following list contains only a few highlights: * Custom mainnav links regression (#8153) * Fixed Python 2.3 incompatibility (#8061) * Fixed Python 2.6 notification issue (#8083) * Fixed PostgreSQL multi column index issue (#7600) You can find a more detailed release note at: http://trac.edgewall.org/wiki/TracDev/ReleaseNotes/0.11 Acknowledgements Many thanks to the growing number of people who have, and continue to, support the project. Also our thanks to all people providing feedback and bug reports that helps us make Trac better, easier to use and more effective. Without your invaluable help, Trac would not evolve. Thank you all. Finally, we offer hope that Trac will prove itself useful to like- minded programmers around the world, and that this release will prove an improvement over the last version. Please let us know. :-) /The Trac Team http://trac.edgewall.org/ --~--~-~--~~~---~--~~ 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 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 0.11.5rc1 Released
Trac 0.11.5rc1 (Release Candidate 1) This is the first and hopefully final release candidate for the upcoming 0.11.5 release. 0.11.5 (final) is scheduled for release on July 7. Trac 0.11.5rc1 contains a number of bug fixes and minor enhancements. The following list contains only a few highlights: * Implemented pre-upgrade backup support for PostgreSQL and MySQL. * Fixed PostgreSQL upgrade issue (#8378) * More robust diff parsing (#2672) * Avoid intermittent hangs by not calling apr_terminate explicitly. You can find a more detailed release note at: http://trac.edgewall.org/wiki/TracDev/ReleaseNotes/0.11 Acknowledgements Many thanks to the growing number of people who have, and continue to, support the project. Also our thanks to all people providing feedback and bug reports that helps us make Trac better, easier to use and more effective. Without your invaluable help, Trac would not evolve. Thank you all. Finally, we offer hope that Trac will prove itself useful to like- minded programmers around the world, and that this release will prove an improvement over the last version. Please let us know. :-) /The Trac Team http://trac.edgewall.org/ --~--~-~--~~~---~--~~ 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 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 0.11.5rc2 Released
Trac 0.11.5rc2 (Release Candidate 2) This is the second and hopefully final release candidate for the upcoming 0.11.5 release. Trac 0.11.5rc2 fixes two regressions found in rc1 and one minor enhancement: * Fixed workaround for zipped Genshi eggs, [8354], #7823 * Fixed internal error when removing a wiki page version [8343]. * Fixed display of merge properties for scoped repositories #7715. You can find a more detailed release note at: http://trac.edgewall.org/wiki/TracDev/ReleaseNotes/0.11 Acknowledgements Many thanks to the growing number of people who have, and continue to, support the project. Also our thanks to all people providing feedback and bug reports that helps us make Trac better, easier to use and more effective. Without your invaluable help, Trac would not evolve. Thank you all. Finally, we offer hope that Trac will prove itself useful to like- minded programmers around the world, and that this release will prove an improvement over the last version. Please let us know. :-) /The Trac Team http://trac.edgewall.org/ --~--~-~--~~~---~--~~ 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 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 0.11.5 Released
Trac 0.11.5 Released We're happy to announce the Trac 0.11.5 release. You will find this release at the usual place: http://trac.edgewall.org/wiki/TracDownload Trac 0.11.5 contains a number of bug fixes and minor enhancements. The following list contains only a few highlights: * Implemented pre-upgrade backup support for PostgreSQL and MySQL (#2304) * Fixed PostgreSQL upgrade issue (#8378) * More robust diff parsing (#2672) * Avoid intermittent hangs by not calling apr_terminate explicitly (#7785) * Fixed display of merge properties for scoped repositories #7715. You can find a more detailed release note at: http://trac.edgewall.org/wiki/TracDev/ReleaseNotes/0.11 Acknowledgements Many thanks to the growing number of people who have, and continue to, support the project. Also our thanks to all people providing feedback and bug reports that helps us make Trac better, easier to use and more effective. Without your invaluable help, Trac would not evolve. Thank you all. Finally, we offer hope that Trac will prove itself useful to like- minded programmers around the world, and that this release will prove an improvement over the last version. Please let us know. :-) /The Trac Team http://trac.edgewall.org/ --~--~-~--~~~---~--~~ 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 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 0.10rc1 Released
Release Notes for Trac 0.10rc1 == September 22, 2006 We're happy to announce the Trac 0.10rc1 release, available from: http://trac.edgewall.org/wiki/TracDownload This is a release candidate, which means that the Trac developers feel that this release is ready for production use, so we encourage people to test this release thoroughly. If no serious bugs are found the final stable 0.10 release will be released on Monday. For questions, comments and user discussions, please use the Trac mailing list. List information, subscription and archive available at: http://trac.edgewall.org/wiki/MailingList User visible changes Advanced diff support - The TracRevisionLog view can now be used to select two arbitrary revisions of a given path in the repository and see the differences between them, in the familiar TracChangeset view. A related change is the possibility to navigate through a sequence of restricted changesets. A restricted changeset is the subset of changes within a changeset inside a given directory. One can easily start navigating such a sequence by following the new Last Change navigation link present for the currently browsed path. It's now also possible to compare two arbitrary paths at any revision. This can be used to check the differences between a tagged version and trunk, or to review the set of differences between two branches. Other enhancements have been made to the version control subsystem, in particular the support of scoped repositories has been improved. You should therefore perform a trac-admin resync operation. InterWiki and InterTrac support --- An InterWiki link can be used to refer to a Wiki page located on another Wiki system, and by extension, to any object located on any other Web site, as long as simple URL mapping is possible. An InterTrac link can be used for referring to a Trac resource (Wiki page, changeset, ticket, ...) on an other Trac environment. This makes it easier to work with multiple separate projects, and seamlessly refer to resources from one Trac to another. Improved modularity --- Trac now supports database and version control backends as third-party plugins. It is now easier to add support for new database backends. In addition to the already existing support for SQLite and PostgreSQL, Trac now features experimental support for the MySQL database. As for the version control systems, Trac still features best of breed Subversion support, but the Subversion bindings and libraries are no longer mandatory for using Trac itself. Other version control systems can be supported by external plugins. Improved notification system The encoding for emails sent out by Trac can now be configured. This may decrease email size and can avoid useless encoding for western languages that make some touchy SMTP servers bounce the notifications. Support for local network installations using local email addresses (addresses without a domain name) and a configurable default domain name has been added, as well as support for both visible and blind carbon copies. Support for spam protection --- Trac now provides extension point that allow plugins to intercept content submissions, which can be used to filter out spam. One plugin that does this is the SpamFilter plugin, which is available as a separate package: http://trac.edgewall.org/wiki/SpamFilter This plugin implements a number of different strategies for testing content, such as regular expression matching, IP blacklisting, and Akismet queries. WSGI used as web server protocol Trac now uses WSGI (the "Python Web Server Gateway Interface") internally. While Trac continues to provide builtin support for CGI, FastCGI and mod_python, as well as the standalone server "tracd", you can now take advantage of the WSGI support to use Trac in other setups, such as Twisted, Paste, SCGI, or ISAPI. Lots of minor improvements -- To the Wiki syntax Numerous improvements have been made in the WikiFormatting syntax: * Headings can optionally be given explicit id. * MoinMoin ["internal free link"] syntax is now supported. * Introduced citation syntax for the Wiki (e-mail style). * Added more robust parsing and formatting of Wiki lists and robust coupling of lists and quotes. * Improved the way external links are displayed. * Lots of new ways to refer to specific repository views (diff:from// to, log:, [x:y], rx:y) * htdocs:, useful for referring to local resources in TracStandalone * MoinMoin-style syntax for description lists * Removed support for direct embedding of images using links: use the [[Image]] macro instead. To the Wiki subsystem * Quicker access to last change on a page and better navigation in the page history * Preview the change comment before saving a change and dis
[Trac] Trac 0.10 Released
Release Notes for Trac 0.10 'Zengia' September 28, 2006 We're happy to announce the Trac 0.10rc1 release, available from: http://trac.edgewall.org/wiki/TracDownload For questions, comments and user discussions, please use the Trac mailing list. List information, subscription and archive available at: http://trac.edgewall.org/wiki/MailingList User visible changes Advanced diff support - The TracRevisionLog view can now be used to select two arbitrary revisions of a given path in the repository and see the differences between them, in the familiar TracChangeset view. A related change is the possibility to navigate through a sequence of restricted changesets. A restricted changeset is the subset of changes within a changeset inside a given directory. One can easily start navigating such a sequence by following the new Last Change navigation link present for the currently browsed path. It's now also possible to compare two arbitrary paths at any revision. This can be used to check the differences between a tagged version and trunk, or to review the set of differences between two branches. Other enhancements have been made to the version control subsystem, in particular the support of scoped repositories has been improved. You should therefore perform a trac-admin resync operation. InterWiki and InterTrac support --- An InterWiki link can be used to refer to a Wiki page located on another Wiki system, and by extension, to any object located on any other Web site, as long as simple URL mapping is possible. An InterTrac link can be used for referring to a Trac resource (Wiki page, changeset, ticket, ...) on an other Trac environment. This makes it easier to work with multiple separate projects, and seamlessly refer to resources from one Trac to another. Improved modularity --- Trac now supports database and version control backends as third-party plugins. It is now easier to add support for new database backends. In addition to the already existing support for SQLite and PostgreSQL, Trac now features experimental support for the MySQL database. As for the version control systems, Trac still features best of breed Subversion support, but the Subversion bindings and libraries are no longer mandatory for using Trac itself. Other version control systems can be supported by external plugins. Improved notification system The encoding for emails sent out by Trac can now be configured. This may decrease email size and can avoid useless encoding for western languages that make some touchy SMTP servers bounce the notifications. Support for local network installations using local email addresses (addresses without a domain name) and a configurable default domain name has been added, as well as support for both visible and blind carbon copies. Support for spam protection --- Trac now provides extension point that allow plugins to intercept content submissions, which can be used to filter out spam. One plugin that does this is the SpamFilter plugin, which is available as a separate package: http://trac.edgewall.org/wiki/SpamFilter This plugin implements a number of different strategies for testing content, such as regular expression matching, IP blacklisting, and Akismet queries. WSGI used as web server protocol Trac now uses WSGI (the "Python Web Server Gateway Interface") internally. While Trac continues to provide builtin support for CGI, FastCGI and mod_python, as well as the standalone server "tracd", you can now take advantage of the WSGI support to use Trac in other setups, such as Twisted, Paste, SCGI, or ISAPI. Lots of minor improvements -- To the Wiki syntax Numerous improvements have been made in the WikiFormatting syntax: * Headings can optionally be given explicit id. * MoinMoin ["internal free link"] syntax is now supported. * Introduced citation syntax for the Wiki (e-mail style). * Added more robust parsing and formatting of Wiki lists and robust coupling of lists and quotes. * Improved the way external links are displayed. * Lots of new ways to refer to specific repository views (diff:from// to, log:, [x:y], rx:y) * htdocs:, useful for referring to local resources in TracStandalone * MoinMoin-style syntax for description lists * Removed support for direct embedding of images using links: use the [[Image]] macro instead. To the Wiki subsystem * Quicker access to last change on a page and better navigation in the page history * Preview the change comment before saving a change and display the change comment when viewing a specific version of a page. This hopefully will encourage authors to document their changes! To the Ticket subsystem * Possibility to Reply to ticket description and changes * Export individual ticket
[Trac] Moving to a new server
Hi guys, We're moving the edgewall.org site to a new and faster server tonight. If everything goes as expected the site should be back online in 1-3 hours. Cheers, Jonas --~--~-~--~~~---~--~~ 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 email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users -~--~~~~--~~--~--~---
[Trac] Re: Moving to a new server
The new server is now up and running. Your might still get "connection refused" errors if the dns change hasn't propagated to your part of the world yet. If you need to access the site right away you can add a few lines from the following page: http://rafb.net/paste/results/BIjNPo60.txt to your "/etc/hosts" file and restart your browser. Cheers, Jonas --~--~-~--~~~---~--~~ 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 email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users -~--~~~~--~~--~--~---
[Trac] UK Linux Awards 2006 - Best Linux/OSS Developer Tool
Good news everyone :) I just found out that Trac is the winner of this year's Best Linux/OSS Developer Tool award. Trac was nominated alongside Mono and Launchpad. Here's a link to the official story: http://www.linuxuser.co.uk/index.php?option=com_content&task=view&id=214 I would like to take this opportunity to thank the entire Trac community for your invaluable contribution, making Trac such a great project. Thank you! Cheers, Jonas --~--~-~--~~~---~--~~ 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 email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users -~--~~~~--~~--~--~---
[Trac] Re: psycopg2 vs. pyPgSQL
John Joseph Bachir wrote: > Hi. I am about to install trac with postgres and am deciding between > psycopg2 and pyPgSQL. Does anyone have any preference for one bindings > library of the other? Any pros and cons? As far as I know both of them should work just fine with Trac. Psycopg2 might be a bit more actively maintained and also uses Trac on their own project site, which might be a good sign :) trac.edgewall.org is using psycopg2 right now. Cheers, Jonas --~--~-~--~~~---~--~~ 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 email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] SECURITY: Trac 0.10.1 Released
Release Notes for Trac 0.10.1 = November 8, 2006 We're happy to announce the Trac 0.10.1 release, available from: http://trac.edgewall.org/wiki/TracDownload For questions, comments and user discussions, please use the Trac mailing list. List information, subscription and archive available at: http://trac.edgewall.org/wiki/MailingList Trac 0.10.1 is a security and bug fix release. This release fixes a Cross Site Request Forgery (CSRF) vulnerability reported by Daniel Kahn Gillmor. Trac 0.10.1 also fixes a number of bugs found since the last release. The complete list of closed tickets can be found here: http://trac.edgewall.org/query?status=closed&milestone=0.10.1 Acknowledgements Many thanks to the growing number of people who have, and continue to, support the project. Also our thanks to all people providing feedback and bug reports that helps us make Trac better, easier to use and more effective. Without your invaluable help, Trac would not evolve. Thank you all. Finally, we offer hope that Trac will prove itself useful to like-minded programmers around the world, and that this release will prove an improvement over the last version. Please let us know. :-) /The Trac Team http://trac.edgewall.org/ --~--~-~--~~~---~--~~ 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 email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Trac 0.10.2 Released
Release Notes for Trac 0.10.2 = November 13, 2006 We're happy to announce the Trac 0.10.2 release, available from: http://trac.edgewall.org/wiki/TracDownload For questions, comments and user discussions, please use the Trac mailing list. List information, subscription and archive available at: http://trac.edgewall.org/wiki/MailingList Trac 0.10.2 is a bug fix release and fixes few bugs introduced in the 0.10.1 release. A brief summary of major changes: * Fixes deadlock when using authz_file config option (#3996). * Makes the CSRF code play nice with the XmlRpcPlugin (#4122). * Fixes Timeline breakage after svn commit when using sqlite (#4120). The complete list of closed tickets can be found here: http://trac.edgewall.org/query?status=closed&milestone=0.10.2 Acknowledgements Many thanks to the growing number of people who have, and continue to, support the project. Also our thanks to all people providing feedback and bug reports that helps us make Trac better, easier to use and more effective. Without your invaluable help, Trac would not evolve. Thank you all. Finally, we offer hope that Trac will prove itself useful to like-minded programmers around the world, and that this release will prove an improvement over the last version. Please let us know. :-) /The Trac Team http://trac.edgewall.org/ --~--~-~--~~~---~--~~ 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 email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Trac 0.10.3rc1 Released
Release Notes for Trac 0.10.3rc1 December 7, 2006 NOTE: This is a release candidate, the real 0.10.3 will hopefully be released early next week. We're happy to announce the Trac 0.10.3-rc1 release, available from: http://trac.edgewall.org/wiki/TracDownload For questions, comments and user discussions, please use the Trac mailing list. List information, subscription and archive available at: http://trac.edgewall.org/wiki/MailingList Trac 0.10.3 is a bug fix release and fixes few bugs introduced in the 0.10.1 and 0.10.2 releases. A brief summary of major changes: * Timeline fail to load with a "NoSuchChangeset" error message (#4132). * Timed out MySQL connections not handled properly (#3645). * Subversion repository resync broken. (#4204). The complete list of closed tickets can be found here: http://trac.edgewall.org/query?status=closed&milestone=0.10.3 Acknowledgements Many thanks to the growing number of people who have, and continue to, support the project. Also our thanks to all people providing feedback and bug reports that helps us make Trac better, easier to use and more effective. Without your invaluable help, Trac would not evolve. Thank you all. Finally, we offer hope that Trac will prove itself useful to like-minded programmers around the world, and that this release will prove an improvement over the last version. Please let us know. :-) /The Trac Team http://trac.edgewall.org/ --~--~-~--~~~---~--~~ 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 email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Duplicate key on creation of new ticket & Date representation question
[EMAIL PROTECTED] wrote:
> Hi,
> I recently installed trac and attempted to migrate existing ticket data
> with scripts to a trac database on PostgreSQL ver 8.1.5. The trac
> version is 0.10.2
>
> All seemed fine - i could view the tickets but now, when I try to add a
> new ticket i get "Trac detected an internal error:" with the following
> Python Traceback:
>
*snip*
> I guess trac is trying to create a new ticket with an existing
> id/ticket number, but can only guess how trac determines what number to
> use next.
Hi,
it sound like you forgot to increase the "ticket_id_seq" sequence after
inserting ticket rows. The following command is probably what you're
looking for:
SELECT setval('ticket_id_seq', max(id)) FROM ticket;
You might need to repeat this for other sequences if you inserted data
into other tables as well.
>
> Also, it would be useful to know what date representation is being used
> in the trac database. It appears to be the number of seconds since the
> 1970-01-01 epoch, but the converted values show up in trac as exactly
> one month later than the original values.
That's strange it really should be seconds since the unix epoch...
Cheers,
Jonas
--~--~-~--~~~---~--~~
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 email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---
[Trac] Trac 0.10.3 Released
Release Notes for Trac 0.10.3 = December 12, 2006 We're happy to announce the Trac 0.10.3 release, available from: http://trac.edgewall.org/wiki/TracDownload For questions, comments and user discussions, please use the Trac mailing list. List information, subscription and archive available at: http://trac.edgewall.org/wiki/MailingList Trac 0.10.3 is a bug fix release and fixes a few bugs introduced in the 0.10.1 and 0.10.2 releases. A brief summary of major changes: * Timeline fail to load with a "NoSuchChangeset" error message (#4132). * Timed out MySQL connections not handled properly (#3645). * Subversion repository resync broken. (#4204). The complete list of closed tickets can be found here: http://trac.edgewall.org/query?status=closed&milestone=0.10.3 Acknowledgements Many thanks to the growing number of people who have, and continue to, support the project. Also our thanks to all people providing feedback and bug reports that helps us make Trac better, easier to use and more effective. Without your invaluable help, Trac would not evolve. Thank you all. Finally, we offer hope that Trac will prove itself useful to like-minded programmers around the world, and that this release will prove an improvement over the last version. Please let us know. :-) /The Trac Team http://trac.edgewall.org/ --~--~-~--~~~---~--~~ 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 email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] SECURITY: Trac 0.10.3.1 Released
Release Notes for Trac 0.10.3.1 === March 8, 2007 We're happy to announce the Trac 0.10.3.1 release, available from: http://trac.edgewall.org/wiki/TracDownload For questions, comments and user discussions, please use the Trac mailing list. List information, subscription and archive available at: http://trac.edgewall.org/wiki/MailingList Trac 0.10.3.1 is a security release: * Always send "Content-Disposition: attachment" headers where potentially unsafe (user provided) content is available for download. This behaviour can be altered using the "render_unsafe_content" option in the "attachment" and "browser" sections of trac.ini. * Fixed XSS vulnerability in "download wiki page as text" in combination with Microsoft IE. Reported by Yoshinori Oota, Business Architects Inc. Acknowledgements Many thanks to the growing number of people who have, and continue to, support the project. Also our thanks to all people providing feedback and bug reports that helps us make Trac better, easier to use and more effective. Without your invaluable help, Trac would not evolve. Thank you all. Finally, we offer hope that Trac will prove itself useful to like-minded programmers around the world, and that this release will prove an improvement over the last version. Please let us know. :-) /The Trac Team http://trac.edgewall.org/ --~--~-~--~~~---~--~~ 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 email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Trac 0.10.4 Release candidate 1
Hi, The 0.10.4 Release candidate 1 is now available for download here: http://ftp.edgewall.org/pub/trac/trac-0.10.4rc1.tar.gz http://ftp.edgewall.org/pub/trac/trac-0.10.4rc1.zip http://ftp.edgewall.org/pub/trac/trac-0.10.4rc1.win32.exe This release is mainly a bug fix release, more information about the changes can be found here: http://trac.edgewall.org/wiki/ChangeLog If no unexpected errors are found we hope to be able to release Trac 0.10.4 in a couple of days. / The Trac Team --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [EMAIL PROTECTED] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Some details on the t.e.o slowdown earlier today
As at least some of you have noticed t.e.o was very unresponsive one or two hours ago. It took a while to identify the cause, but then I noticed that somebody from 239.237.broadband7.iol.cz (88.102.237.239) is running some type of web-spider hitting the site att full speed (no pause between requests). This shouldn't normally be any problem but after a while it found its way to the slowest urls on t.e.o. A search on the term "trac" results in more than 500 result pages which the spider started to download, one after the other. Anyway, as soon as I blacklisted the ip in the firewall the load avg quickly dropped down from 25 to more normal levels. Please let me know if you notice any more problems. Cheers, Jonas --~--~-~--~~~---~--~~ 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 email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: List owner
Andrew Stewart wrote: > > Can anyone tell me if this list has a list-owner address? I'm kinda new to > google groups, and the retarded firewall I'm behind blocks certain google > pages (like the google groups subscription management pages). > Hi Andrew, the list owner address is [EMAIL PROTECTED] but you can also contact me off-list if you need help with anything list-related. Cheers, Jonas --~--~-~--~~~---~--~~ 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 email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: "Connect" psycopg2 with selfcompiled Python version
petschni wrote: > > Hello, > > I had to install/compile my own Pythonversion, since the version of my > hoster was too old. After that I also installed "psycopg2". (I could > not do the system wide installation, since I am not root.) > > But after that I was not able to find any documentation on how to tell > Python that it is supposed to use "psycopg2". This is probably a very > basic question, but I did not find information on this on the > "psycopg2"-website. > > Does somebody know what I have to do? (Right now the when I want to > create a new project, trac "complains" that i cannot connect to the > database...) It sounds like you perhaps used the old python version that came with the system instead of the new one when you installed psycopg2. That would explain why "setup.py install" failed and why your python version can't seem to find the psycopg2 module. You should probably run something like this to install psycopg2: $ cd psycopg2-2.0.x/ $ /somewhere/bin/python setup.py install Cheers, Jonas --~--~-~--~~~---~--~~ 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 email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Moving Trac project from Windows to unix
Jani Tiainen wrote: > > Emmanuel Blot kirjoitti: >>> What would be best option to make transfer? Setup projects as blank in >>> Linux and copy only DB? Or copy whole projects and update paths accordingly? >> >> Well, the safest way is to use portable file format between two >> different hosts (if the HW architecture is different, you might get >> real issues if you simply copy binary files) >> >> Use 'sqlite3' to dump and re-read /db/trac.db files, and >> svnadmin for the Subversion repositories. >> Other files can be copied as is, although I would recommend you run >> 'dos2unix' or the eq. command on /conf/trac.ini files to >> convert CRLF end-of-lines into LF end-of-lines. >> Sqlite dump/load should only be necessary when moving from sqlite2 to sqlite3. The sqlite file format is platform independent. > > Well I meant "dumping" in some protable format. > > But still, would anything bad happen if I recreate my trac projects and > just replace db with dump data? Simply copying the env to the new system should work. One possible issue might be file attachments when an environment is moved from a case insensitive filesystem to a case sensitive filesystem. But iirc NTFS is case preserving so this might not be an issue after all... Cheers, Jonas --~--~-~--~~~---~--~~ 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 email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Moving Trac project from Windows to unix
Jani Tiainen wrote: > Yep, NTFS is (by default, can be changed) case insensitive, case preserving. > > So I'm pretty much good to go. > > Altough still bothers me: is it better to setup projects before copying > data (creating new ini files etc?) or doesn't matter? > It's probably easiest to simply copy the env to the new system and update trac.ini with the new repository location. Cheers, Jonas --~--~-~--~~~---~--~~ 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 email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: trac search performance?
Aaron Watters wrote: > > It looks to me like the Trac search functionality uses SQL "like". > I was wondering if anyone has seen performance issues with > this approach. Just testing using > > http://twistedmatrix.com/trac/search?q=the > > I get about 8000 documents, pretty quickly (which is probably > the whole database). So I guess performance would > degrade at sizes larger than that, if ever. > > My personal motivation for this musing is that I wrote > the NUCULAR full text retrieval package > > http://nucular.sourceforge.net > > and would love to see it used in Trac. Hi Aaron, Yes, we're aware of this performance issue. There is a wiki page discussing how the search system could be improved: http://trac.edgewall.org/wiki/AdvancedSearch As far as I know nobody has started coding on this yet. And there are a few things that have to be decided before that can happen, for example if we should select a single indexer or use an abstraction layer (pyndexter[1] or some special type of plugins). [1]: http://swapoff.org/pyndexter btw, I noticed that according to the homepage nucular does not work on NTFS. This would be a show stopper for us. Do you have any info about when/if this will be solved? Cheers, Jonas --~--~-~--~~~---~--~~ 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 email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: OT: Why do e-mails always arrive twice?
Alexander Kriegisch wrote: > > Off-topic, but important enough to ask, because it is getting on my > nerves: I get each single message from this list twice. How can I fix that? It looks like you subscribed both your kriegisch.name and googlemail.com address on December 13. I\ve now unsubscribed your googlemail address so you should receive only one copy of this message. Cheers, Jonas --~--~-~--~~~---~--~~ 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 email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Trac 0.11b1 Released
Trac 0.11b1
===
We now have a beta1 release for the much awaited Trac 0.11.
You will find this release at the usual place:
http://trac.edgewall.org/wiki/TracDownload
Here are some of the features you can expect from this version:
* New template engine for generating content (Genshi)
* New configurable workflow in the ticket subsystem
* Finer-grained control of permissions
* Support for Pygments as the default syntax highlighter
* Improved repository browser ("blame" support, dynamic in-place
expansion of folders)
* Improved user preferences subsystem, among which the possibility
for any user to select their time zone and disable access keys
* The WebAdmin plugin is now an integral part of Trac
You can find a more detailed release note at:
http://trac.edgewall.org/wiki/TracDev/ReleaseNotes/0.11
Note that the beta1 should already be very stable and we don't expect
any critical issues with it. If everything goes well, we can expect a
real 0.11 to follow quite soon after the beta1 testing period.
Acknowledgements
Many thanks to the growing number of people who have, and continue to,
support the project. Also our thanks to all people providing feedback
and bug reports that helps us make Trac better, easier to use and more
effective.
Without your invaluable help, Trac would not evolve. Thank you all.
Finally, we offer hope that Trac will prove itself useful to like-
minded programmers around the world, and that this release will prove an
improvement over the last version.
Please let us know. :-)
/The Trac Team http://trac.edgewall.org/
--~--~-~--~~~---~--~~
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 email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---
[Trac] Server maintenance
Hi all, The server hosting *.edgewall.org is currently down for hardware maintenance. Hopefully it won't take too long. Cheers, Jonas signature.asc Description: OpenPGP digital signature
[Trac] svn.edgewall.org is now https-only
Hi, I've just made svnedgewall.org https-only. Your existing woking copies needs to be fixed if checked-out over HTTP. If you see the following error message: svn: E170011: Repository moved temporarily to 'https://svn.edgewall.org/repos/trunk The working copy can be fixed like this: $ svn relocate http:// https:// / Jonas -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To post to this group, send email to trac-users@googlegroups.com. Visit this group at https://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
