Changes between Version 14 and Version 15 of TracFaq
- Timestamp:
- May 12, 2015, 7:37:56 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracFaq
v14 v15 5 5 If you have a question not answered on this page, you can ask it on the MailingList or in the IrcChannel. See the TracSupport page for more options on getting support for Trac. 6 6 7 ----8 7 **Note:** If you don't find the answer you are looking for here and you are using Trac 0.12 or older versions, also have a look in the old [wiki:"0.12/TracFaq"]. 9 8 … … 18 17 ==== Q: Why do I get `NameError: global name 'log' is not defined` when trying to use `setup.py`? 19 18 20 {{{ 19 {{{#!sh 21 20 ../trunk/$ python setup.py egg_info 22 21 running egg_info … … 26 25 }}} 27 26 28 **A:** You're most likely working from a Subversion **1.7** checkout and you're using a too old `setuptools` package, eg `/setuptools-0.7a1dev_r66608`. Upgrade to a newer setuptools, downgrade to svn 1.6.x, or use distribute. 29 See #7598. 27 **A:** You're most likely working from a Subversion **1.7** checkout and you're using a too old `setuptools` package, eg `/setuptools-0.7a1dev_r66608`. Upgrade to a newer setuptools, downgrade to svn 1.6.x, or use distribute. See also #7598. 30 28 31 29 ==== Q: Why does installing `distribute` fail with `ValueError: A 0.7-series setuptools cannot be installed with distribute.`? 32 30 33 31 You tried to install `distribute` as advised elsewhere: 34 {{{ 32 {{{#!sh 35 33 $ curl http://python-distribute.org/distribute_setup.py | python 36 34 }}} 35 37 36 but you're greeted with: 38 {{{ 37 {{{#!sh 39 38 ValueError: A 0.7-series setuptools cannot be installed with distribute. Found one at /packages/trac/virtualenv-0.13/lib/python2.7/site-packages/setuptools-0.7a1dev_r66608-py2.7.egg 40 39 }}} 41 40 42 **A:** Don't give up, it's just `setuptools` giving you a last fight. 43 44 You can remove the offending setuptools .egg and if it keeps re-appearing, you have it installed not only in the virtualenv but also in the parent Python installation (the one in which you installed virtualenv itself). If this is the case, remove it from there as well and installing distribute should now work. 41 **A:** Don't give up, it's just `setuptools` giving you a last fight. You can remove the offending setuptools .egg and if it keeps re-appearing, you have it installed not only in the virtualenv but also in the parent Python installation, the one in which you installed virtualenv itself. If this is the case, remove it from there as well and installing distribute should now work. 45 42 46 43 ==== Q: Why does Apache crash (500) with a `ZipImportError` in the error log? … … 53 50 }}} 54 51 55 **A:** You most certainly forgot to stop and restart your server during an upgrade. The zip importer mechanism keeps an internal cache which has trouble detecting replaced files, so a restart is needed, see TracUpgrade#ZipImportError.52 **A:** You probably forgot to stop and restart your server during an upgrade. The zip importer mechanism keeps an internal cache which has trouble detecting replaced files, so a restart is needed, see TracUpgrade#ZipImportError. 56 53 57 54 ==== Q: Why do ticket notification emails contain unexpected backslash characters? … … 61 58 **A:** This is the result of a defect in Genshi 0.7 (genshi:#569). Until Genshi 0.7.1 is released, your options are: 62 59 * Downgrade to Genshi 0.6.1 63 * Convert the line endings of the ticket notification email template from `CRLF` to `LF`. For example, on a Unix-like system you can run the following from the directory in which the egg is installed (you may need elevated privileges, and your egg may have a different name depending on your Trac and Python versions):60 * Convert the line endings of the ticket notification email template from `CRLF` to `LF`. For example, on a Unix-like system you can run the following from the directory in which the egg is installed: 64 61 {{{#!sh 65 dos2unix Trac-1.0.1-py2.7.egg/trac/ticket/templates/ticket_notify_email.txt62 $ dos2unix Trac-1.0.1-py2.7.egg/trac/ticket/templates/ticket_notify_email.txt 66 63 }}} 64 You may need elevated privileges, and your egg may have a different name depending on your Trac and Python versions. 67 65 68 66 === Upgrade troubleshooting … … 73 71 74 72 If that still doesn't work, look in your server configuration to see where the chrome files are supposed to be served from (`Alias` or `AliasMatch` directive), and maybe you are serving them as static files from a different location: 75 {{{ 73 {{{#!apache 76 74 Alias /trac/bct/chrome /packages/trac/virtualenv-0.13/share/htdocs 77 75 }}} 76 78 77 In this case, don't forget to: 79 {{{ 78 {{{#!sh 80 79 $ trac-admin <yourenv> deploy /packages/trac/virtualenv-0.13/share 81 80 }}} 81 82 82 See TracUpgrade#a5.Refreshstaticresources. 83 84 83 85 84 ==== Q: Attachments are missing after upgrade … … 114 113 115 114 And then apply it to the broken environment: 116 {{{ 115 {{{#!sh 117 116 $ python run-db28.py /path/to/tracenv 118 117 }}} … … 126 125 The community site [TracHacks:WikiStart trac-hacks.org] is a great place for finding plugins, it also contains a few [TracHacks:wiki:tutorial tutorials] to get you started. 127 126 128 129 127 === Q: How to contribute to Trac? 130 128