Ticket #100
Attachments
<Attach file button>
note that there are no attachments mentioned on the page. Returning to
the ticket shows that the attachment was not added to it.
I'm using tracd and there is no error shown on the log:
03:53:29 AM Trac[chrome] DEBUG: Prepare chrome data for request
03:53:29 AM Trac[session] DEBUG: Retrieving session for ID u'oscar'
127.0.0.1 - - [30/Apr/2009 03:53:29] "GET /clientes/attachment/ticket/100/?action=new&attachfilebutton=Attach+file HTTP/1.1" 200 -
03:53:29 AM Trac[main] DEBUG: 566 unreachable objects found.
03:54:17 AM Trac[main] DEBUG: Dispatching <Request "POST u'/attachment/ticket/100/'">
03:54:17 AM Trac[chrome] DEBUG: Prepare chrome data for request
03:54:17 AM Trac[session] DEBUG: Retrieving session for ID u'oscar'
127.0.0.1 - - [30/Apr/2009 03:54:17] "POST /clientes/attachment/ticket/100/?action=new&attachfilebutton=Attach+file HTTP/1.1" 200 -
03:54:17 AM Trac[main] DEBUG: 506 unreachable objects found.
I'm using trac 0.11.1 on Kubuntu 9.04 64bits, migrated from 0.11.1 on
Windows XP 32 bits. The last time we succesfully attached a file it was
with tracd 0.10.x running on Windows, so maybe this is caused by the
trac version upgrade or by the platform migration (or by something
else).
--
Oscar
> Would you mind giving some more information about how you switched
> Trac to use python2.5?
>
> I've installed 2.5 and switched the /usr/bin/python link to point to
> 2.5 instead of 2.6, but I'm not sure what I need to do to make apache
> and mod_python or whatever acknowledge this. This is the only python
> site I have running anywhere, so I'm a little unsure of what needs
> done.
>
> Any advice?
I use pkgsrc, which explicitly does not provide a /usr/pkg/bin/python
link. The problem is that python 2.6 looks in a different directory for
extensions, so you need to have all your extensions rebuilt for 2.6
instead of 2.5. So in the pkgsrc world you'd delete all python stuff
and then rebuild trac and ap2-wsgi or whatever you use for apache if
any. Moving the symlink doesn't fix everything, which is the reason
behind thinking using it is harmful and thus not providing it.
I have no idea what system you are using, but my advice is that you try
to answer the following:
Why do I believe that the python bits I had installed before (both the
trac dependencies, and how apache runs python) will be found by trac
running under 2.6, and when found will be linked against the right
python libraries?
I think you'll find the answer is "Gee, I have no reasonable basis for
expecting any of that to work" and hopefully that will point you in the
right direction.
In pkgsrc, one can install py24-genshi and py25-genshi at the same time,
because it's a pure python module that installs wholly within
/usr/pkg/lib/python2.5/site-packages. But ap22-py24-wsgi cannot be
installed with ap22-py25-wsgi because:
> pkg_info -L ap22-py25-wsgi
Information for ap22-py25-wsgi-2.4:
Files:
/usr/pkg/lib/httpd/mod_wsgi.so
it doesn't encode the python version in the module
(or with ap2-py25-wsgi - I am running apache 2.2).
sudo easy_install http://svn.edgewall.org/repos/trac/tags/trac-0.11.4
After an apache restart, the trac web interface shows 0.11.4 and
attachments (and everything else) work.
Ah, so you have used the dependencies in the packaging system to get up
to date and stay with 2.6, which is a fine solution, and lets you avoid
the mess of changing python versions, which I supsect is quite hard in
ubuntu.