Hello.
This morning the bug isn't there anymore, so it looks like there is
some 'random stuff' regarding different points in time.
This aren't good news, but there's more. Now I pass the
compareResultsErrorFlag test with python2.4, but with python2.5 It
crashes with:
*** glibc detected ***
I've tried to build parsedatetime-0.8.6 from source package and I can
confirm the bug (exactly the same error) with 3 different locale
environments ('C', '[EMAIL PROTECTED]' and 'es_ES.UTF-8').
I'm doing some more testing. I'll attach my conclusions (if any)
probably tomorrow.
-- System
Hi,
Unfortunately, my mailer doesn't properly support starting from a template
with headers, so I can't use it with reportbug.
Using reportbug without a mailer is not an option? Knowing things like
the architecture is something you need for a lot of bugs, I'd have
expected that you're running
severity 485054 normal
tags 485054 + unreproducible moreinfo
thanks
From my pbuilder build log:
Builds just fine here. Please use reportbug next time you're reporting a
bug, looking at an excerpt of your pbuilder log does not help at all.
Until you've provided the proper informations (the
On Monday 09 June 2008 04:06:32 pm you wrote:
severity 485054 normal
tags 485054 + unreproducible moreinfo
thanks
From my pbuilder build log:
Builds just fine here. Please use reportbug next time you're reporting a
bug, looking at an excerpt of your pbuilder log does not help at all.
Package: parsedatetime
Version: 0.8.6-1
Severity: serious
From my pbuilder build log:
...
set -e ;\
for py in python2.4 python2.5; do \
PYTHONPATH=/tmp/buildd/parsedatetime-0.8.6/build/lib $py
run_tests.py parsedatetime; \
done
6 matches
Mail list logo
