Trac Development Google Group

Re: [Trac-dev] Test failures on buildbot

2009-11-26T01:09:57Z

Correct, I could finally reproduce the issue by switching my timezone to
PST. Actually, any timezone different from the one used in that
particular test (which happens to be mine) reproduces the issue.
No, actually some of the changes in [8831] were wrong. The issue is
fixed with [8857]. I guess we now have enough reasons to make a second

Re: [Trac-dev] Trac0.11.6 - Cannot operate on a closed cursor

2009-11-25T15:09:14Z

* Christian Boos <cb...@neuf.fr> [2009-11-23 18:22]:

Great. Thanks for testing. It seems something is broken in my
environment.

I can reproduce it with just a one request, 100% of time, so it is
either something really stupid or really bad setup somewhere.
I'll debug it more next week.

Re: [Trac-dev] Test failures on buildbot

2009-11-25T11:28:12Z

Right, look at time.daylight usage in the code. Tim's buildbot must live
in a non-DST timezone.
I suppose the test has to take this into account, for choosing an
appropriate expected value.

-- Christian

Re: [Trac-dev] Test failures on buildbot

2009-11-24T15:20:12Z

That was also my guess, but I could reproduce the issue neither with nor
without pytz.
If pytz is not installed, how could two Linux platforms have different
behaviors for this, if we only use our own timezone classes (which don't
use local TZ info)? It would basically mean that the datetime module, in

Re: [Trac-dev] Test failures on buildbot

2009-11-24T11:18:46Z

None I guess, as I see <FixedOffset "GMT +1:00" 1:00:00> in the test
results, which is our own tzinfo subclass.

-- Christian

Test failures on buildbot

2009-11-23T23:45:42Z

I have noticed that Tim's buildbot fails on trunk since I merged [8831]
(the timezone fix). For example:
[link]
Unfortunately, all tests pass on all my machines (Linux + OS X), both
with and without pytz. Any ideas what could be wrong?

Re: changed sqlite requirements in 0.12dev (#8625)

2009-11-23T19:17:36Z

Am 23.11.2009 10:13, schrieb Christian Boos:
In order to provide the best possible integration with the distro (and
to lower the maintenance burden), Fedora uses a custom spec file
template. However the packaging process still uses 'setup.py
build'/'setup.py install'.
This is the current trac.spec in Fedora:

Re: changed sqlite requirements in 0.12dev (#8625)

2009-11-23T08:47:39Z

Am 23.11.2009 04:09, schrieb Eli:
Mostly rumors, but I'm confident that RHEL 6 will be released in Q2.
fs

recursion-safe permission policies

2009-11-23T18:28:02Z

Is there a recommended way of implementing IPermissionPolicy such that
multiple policies don't cause infinite recursion? I'm writing a
simple policy similar to SensitiveTicketsPolicy that requires a new
permission in order to view sensitive components, and I would like to
use it in combination with PrivateTicketsPolicy.

Re: [Trac-dev] Trac0.11.6 - Cannot operate on a closed cursor

2009-11-23T17:21:57Z

...

This should work... it worked for me on Windows (older SQLite and
Pysqlite versions, then same versions) and Linux (same SQLite and
Pysqlite versions as you), using Trac 0.11.6rc1.

Even with no poolable connections, that connection should normally end
up in the _active map, and stay there until the shutdown of the request.

Trac0.11.6 - Cannot operate on a closed cursor

2009-11-23T13:19:37Z

Hi.

I upgraded my installations to latest 0.11 stable (8846).
Unfortunately it killed my custom plugin, tracking lead me to commit
8590 that enabled connetion pooling on linux.

In my plugin I'm reusing generating ticket group stats from roadmap to
display similar progress bars.

Some simplified code is here that triggers the error:

Re: [Trac-dev] changed sqlite requirements in 0.12dev (#8625)

2009-11-22T05:14:24Z

don't forget...

if from a repo, it may be handy to add a PYTHONPATH entry so it can be
found - or make a .pth file in /usr/lib64/python2.5/site-pack ages/
(YDMV)
being there and being found makes it work.

thx All

Re: [Trac-dev] Re: changed sqlite requirements in 0.12dev (#8625)

2009-11-23T09:13:24Z

Thank you for these detailed informations.

Now I have another question. For building the packages, do you use the
`python setup.py bdist_rpm` method?
If not, are the extra changes needed a matter of changing the setup.cfg
or the setup.py files?
In this case, we should integrate those changes, if possible.

Trac 0.11.6rc1 is available

2009-11-23T09:00:50Z

Hello,

Yesterday we prepared the first release candidate for 0.11.6:
[link]

For an overview of the changes, please see
[link]

As usual, we will be going through a period of one week of testing

Re: [Trac-dev] Re: changed sqlite requirements in 0.12dev (#8625)

2009-11-23T03:09:04Z

Is RHEL6 supposed to come out in Q1 2010, or has RedHat given any guidance on
their intentions?

Eli
------------------. "If it ain't broke now,
Eli Carter \ it will be soon." -- crypto-gram
retrac...@gmail.com `----------------------------- --------------------