The two instances are on different domains and servers hosted at DreamHost.com, but the servers are both running the same Ubuntu configurations as far as I know. I diff'ed the two trac.ini files and mostly the differences are for notifications (email addresses, etc).
Here is the background: The 1.0.2 Trac is my test install. I built it from scratch by making a python virtualenv, then running: python ~/trac/python/bin/easy_install --install-dir=~/trac/python/lib/python2.7/site-packages/ Trac==1.0.2 Then I copied in my trac.ini and trac.db from the previous Trac 0.11 installation, and then installed all my plugins. (Lots of other steps and changes, of course.) When I saw this all worked perfectly, I repeated the installation on the company's domain. A day or two later I saw that Trac 1.0.3 was released. I tried to upgrade 1.0.2 to 1.0.3 by uploading the egg using the Admin panel, but it didn't seem to take effect. I then deleted the whole thing and repeated the install using 1.0.3. I thought everything was fine until I discovered this problem uploading zip files. I could upgrade the 1.0.2 to 1.0.3. I need to know the proper way to do it though. I assume my attempt using the Admin panel was wrong? Is this the correct way: python ~/trac/python/bin/easy_install --install-dir=~/trac/python/lib/python2.7/site-packages/ --upgrade Trac==1.0.3 - Rick -- 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.
