Hello,

Just joined the list to ask this question: the Release Notes for 1.0.x say
it's compatible with Python 2.5, 2.6 and 2.7.  (If I should have filed a
bug report instead, please be gentle.)

I was able to build Trac 1.0.1 from a Fedora Core 19 SRPM on my
Red Hat RHEL 6.5 system with Python 2.6.6.

If I try to upgrade it using either a trac-1.0.2-1 or trac-1.0.2-2 SRPM
from Fedora Core 19, it fails 1 test in both cases and the RPM isn't built.

The RPM build attempt failure message is the same in both cases:

[root@stride2 tests]# printenv LANG
en_US.UTF-8

[root@stride2 SRPMS]# rpmbuild --rebuild trac-1.0.2-2.fc19.src.rpm 
Installing trac-1.0.2-2.fc19.src.rpm

[...]

======================================================================
ERROR: test_get_node (tracopt.versioncontrol.git.tests.git_fs.GitNormalTestCase)
----------------------------------------------------------------------
Traceback (most recent call last):
  File 
"/root/rpmbuild/BUILD/Trac-1.0.2/tracopt/versioncontrol/git/tests/git_fs.py", 
line 267, in test_get_node
    self._git('branch', u'tïckét10605', 'master')
  File 
"/root/rpmbuild/BUILD/Trac-1.0.2/tracopt/versioncontrol/git/tests/git_fs.py", 
line 53, in _git
    cwd=self.repos_path, **kwargs)
  File "/usr/lib64/python2.6/subprocess.py", line 642, in __init__
    errread, errwrite)
  File "/usr/lib64/python2.6/subprocess.py", line 1234, in _execute_child
    raise child_exception
TypeError: execv() arg 2 must contain only strings

----------------------------------------------------------------------

This smells a lot like Ticket 12020 (or 11675?) but I thought that was fixed
by now?  Sorry, I don't know enough about Trac 1.0.x to decipher this.

Thanks,

        - Greg

-- 
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.

Reply via email to