It turns out our server is a VPS (at DreamHost), but we don't have root
access.
I have had some success on my test subdomain (also at DreamHost, but
regular shared hosting, not a VPS).
It turns out there is a system-wide Trac v1.2 installed, and that's what's
getting run.
ls -l /usr/bin/tracd
-rwxr-xr-x 1 root root 362 Dec 3 2016 /usr/bin/tracd
$ cat /usr/bin/tracd
#!/usr/bin/python
# EASY-INSTALL-ENTRY-SCRIPT: 'Trac==1.2','console_scripts','tracd'
__requires__ = 'Trac==1.2'
import re
import sys
from pkg_resources import load_entry_point
if __name__ == '__main__':
sys.argv[0] = re.sub(r'(-script\.pyw?|\.exe)?$', '', sys.argv[0])
sys.exit(
load_entry_point('*Trac==1.2*', 'console_scripts', 'tracd')()
)
I copied the trac directory from our production server and ran various
update commands (that I'm trying to duplicate) and I successfully got my
production Trac upgraded and it runs with the above v1.2. I don't know what
to do on the production VPS server that has no system-wide Trac, just our
v1.0.3. I'm afraid to mess with it in place.
I'm trying to find out what they updated 10 days ago that might have broken
it.
On Tuesday, November 10, 2020 at 12:20:03 PM UTC-7 RjOllos wrote:
> On Monday, November 9, 2020 at 10:14:40 PM UTC-8 sailo...@gmail.com wrote:
>
>> Looking at the broken installation closer, I found that a couple of years
>> ago I created a script to start-tracd. I barely remember why though. I
>> think it had to do with the ISP not having any interest in supporting our
>> use of Trac. I can't believe this survived for almost 2 years.
>>
>> nohup tracd -s --port 8000 --basic-auth="project,/home/user/
>> example.com/trac/trac.passwd,Example Trac" /home/user/example.com/trac &
>>
>> If I run this now (without the "-s") I get this error. Could this be the
>> problem?
>>
>> Traceback (most recent call last):
>> File "/home/user/trac/python/lib/python2.7/site-packages/tracd", line
>> 5, in <module>
>> from pkg_resources import load_entry_point
>> File "/home/user/
>> example.com/trac/python/lib/python2.7/site-packages/pkg_resources/__init__.py",
>>
>> line 2970, in <module>
>> working_set = WorkingSet._build_master()
>> File "/home/user/
>> example.com/trac/python/lib/python2.7/site-packages/pkg_resources/__init__.py",
>>
>> line 567, in _build_master
>> ws.require(__requires__)
>> File "/home/user/
>> example.com/trac/python/lib/python2.7/site-packages/pkg_resources/__init__.py",
>>
>> line 876, in require
>> needed = self.resolve(parse_requirements(requirements))
>> File "/home/user/
>> example.com/trac/python/lib/python2.7/site-packages/pkg_resources/__init__.py",
>>
>> line 761, in resolve
>> raise DistributionNotFound(req)
>> pkg_resources.DistributionNotFound: Genshi>=0.6
>>
>
> I can't say how this relates to your other problems, but the issue here is
> that Genshi is not found. So you probably need to install Genshi into the
> Python install at "/home/user/trac/python".
>
> $ /home/user/trac/python/bin/pip install Genshi
>
> might accomplish that.
>
> Bigger picture, you might consider moving to another hosting provider if
> they aren't willing to help you and yet your access is restricted on the
> system. You could get a virtual private server running Debian or Ubuntu on
> a hosting provider such as Digital Ocean. Bitnami and TurnKey Linux offer
> virtual appliances that would speed up the configuration:
> https://trac.edgewall.org/wiki/CommercialServices#VirtualAppliances
>
> Ryan
>
--
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 trac-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/trac-users/660cb3cf-86bf-483d-9902-a729eb7ae607n%40googlegroups.com.
