"Maciej (Matchek) Blizinski" <[email protected]> writes:
> On Thu, Feb 25, 2010 at 5:27 PM, Peter FELECAN <[email protected]> wrote:
>> As you asked me, I investigated the origin of the files in
>> /opt/csw/lib/python/site-packages and all the files are from the CSWtrac
>> package. However, I do not understand what do you mean by "right version
>> of Trac is present in Trac files"... I didn't found a reference to Trac
>> version in those files.
>
> The theory is that pysetuptools look into the egg files for
> information about installed packages. It can be thought of as the
> Python equivalent of SONAMEs (kind of). pysetuptools might look into
> the egg files to figure out the versions of installed packages. If
> the egg files are missing, pysetuptools think that the package is not
> installed, and they throw an errors.
>
> Trying the package from experimental would test this theory. Can you do that?
Yes. It moves the issue a step farther:
trac-admin /tracs/test resync
Traceback (most recent call last):
File "/opt/csw/bin/trac-admin", line 5, in <module>
from pkg_resources import load_entry_point
File "/opt/csw/lib/python/site-packages/pkg_resources.py", line 2603, in
<module>
working_set.require(__requires__)
File "/opt/csw/lib/python/site-packages/pkg_resources.py", line 666, in
require
needed = self.resolve(parse_requirements(requirements))
File "/opt/csw/lib/python/site-packages/pkg_resources.py", line 565, in
resolve
raise DistributionNotFound(req) # XXX put more info here
pkg_resources.DistributionNotFound: setuptools>=0.6b1
Maybe more eggs missing
--
Peter
_______________________________________________
maintainers mailing list
[email protected]
https://lists.opencsw.org/mailman/listinfo/maintainers
.:: This mailing list's archive is public. ::.
