Edgewall Software
Modify

Ticket #8365 (closed defect: fixed)

Opened 3 years ago

Last modified 22 months ago

Trac trunk requiring Genshi "0.6dev_r960" but only "0.6dev_r0" available

Reported by: Tony Owned by: cboos
Priority: high Milestone: 0.12
Component: general Version: 0.12dev
Severity: normal Keywords: Trac trunk Genshi version
Cc:
Release Notes:
API Changes:

Description

I installed Trac Trunk today, Genshi Trunk and Babel Trunk.
After creating a new environment as usual, when trying to run the project it was requesting Genshi 0.6dev_r960, but in my Genshi install I was getting the .egg as Genshi-0.6dev_r0-py2.5-win32.egg.

Note that I tried the complete Trac, Genshi and Babel installation many times with Python 2.5.4 and 2.6.2, I used easy_install and tried to install by downloading (SVN) their source code and doing a setup.py.

I solved the problem by just changing the egg name to
Genshi-0.6dev_r960-py2.5-win32.egg

I think that by mistake this egg name is wrong, or Trac is looking for the wrong version of Genshi, or the trunk version of Genshi is wrong.

Attachments

Change History

comment:1 in reply to: ↑ description Changed 3 years ago by cboos

  • Severity changed from blocker to normal

Replying to Tony:

I installed Trac Trunk today, Genshi Trunk and Babel Trunk.

Well, that's wrong, as of today, Trac trunk needs Genshi:source:branches/experimental/advanced-i18n and Babel 0.9.4, as stated in wiki:TracL10N and the milestone:0.12.

It seems that this information is easily overlooked. It would be helpful if you could tell us in which places you looked for informations and where else we would need to indicate those requirements.

After creating a new environment as usual, when trying to run the project it was requesting Genshi 0.6dev_r960, but in my Genshi install I was getting the .egg as Genshi-0.6dev_r0-py2.5-win32.egg.

See also #8362 which discusses that issue. As that other ticket is already closed, let's use the present ticket for tracking the resolution of this problem.

comment:2 Changed 3 years ago by Tony

Maybe by not getting the Genshi:source:branches/experimental/advanced-i18n was the cause of problems, ill try it and post the results, but its strange that Genshi Trunk is of an older version than this one.

comment:3 Changed 3 years ago by Tony

It have not worked. I did a SVN Checkout from http://svn.edgewall.org/repos/genshi/branches/experimental/advanced-i18n/ and installed. The egg was with the same name as I said. After renaming it it worked.

comment:4 Changed 3 years ago by cboos

  • Priority changed from normal to high

comment:5 Changed 3 years ago by osimons

I think this is Subversion 1.6+ that has yet again changed formats in checkout, and setuptools not being able to parse revision properly. I see it too with 1.6.2 and now 1.6.3 that I recently upgraded to on my dev setup.

You're using 'svn --version' 1.6.x, right?

comment:6 Changed 3 years ago by cboos

Right, the problem with svn 1.6 is well known (http://bugs.python.org/setuptools/issue64) but I think we have now to find a workaround, as the fix upstream is taking way too much time to be applied.

Anyway requiring 'Genshi>=0.6dev-r960' misses its purpose as this also matches Genshi trunk, which is wrong. So I think we should simply require 'Genshi>=0.6dev', as this is not worse and at least would avoid the current problem with setuptools.

Then, make it clear by other means that the genshi:source:branches/experimental/advanced-i18n branch is required.

For example:

  • setup.py

     
    7070 
    7171    install_requires = [ 
    7272        'setuptools>=0.6b1', 
    73         'Genshi>=0.6dev-r960' 
     73        'Genshi>=0.6dev' 
    7474    ], 
    7575    extras_require = { 
    7676        'Babel': ['Babel>=0.9.4'], 
     
    121121 
    122122    **extra 
    123123) 
     124 
     125print """ 
     126Note: currently Trac 0.12dev *requires* Genshi advanced-i18n, 
     127      which can be obtained from the repository: 
     128 
     129      svn checkout http://svn.edgewall.org/repos/genshi/branches/experimental/advanced-i18n/ genshi-i18n 
     130 
     131      Make sure you're using that version and not Genshi from trunk, 
     132      as that version is not 100% compatible with Trac trunk. 
     133""" 
     134 

(probably with some refinements, like only showing the notice for install, develop and bdist* targets)

comment:7 Changed 2 years ago by rblank

I have applied the first part of the patch in comment:6 in [8602], as my newly-installed build hosts fail due to this (I had to reinstall Genshi in my virtualenvs, and I had updated to Subversion 1.6).

comment:8 follow-up: Changed 2 years ago by cboos

I wonder if we shouldn't put simply an svn:externals pointing to the genshi dependency. People checking out Trac trunk will then get the appropriate version of Genshi.

That would be useful not only for the current situation (where we could point to advanced-i18n), but also later, for switching back to Genshi trunk, or when we have Trac 0.12-stable, for selecting the corresponding stable/0.6.x. Avoiding "known bad" versions would also be possible that way.

comment:9 in reply to: ↑ 8 Changed 2 years ago by rblank

Replying to cboos:

I wonder if we shouldn't put simply an svn:externals pointing to the genshi dependency. People checking out Trac trunk will then get the appropriate version of Genshi.

Interesting. People would still have to remember to install the checked-out version, instead of relying on easy_install to fetch it for them, though.

comment:10 Changed 2 years ago by cboos

  • Owner set to cboos

Now that setuptools-0.6c10/11 is out with svn 1.6.x support and Genshi trunk is usable again we should probably add a 'Genshi>=0.6dev-r1072' requirement again.

comment:11 Changed 2 years ago by cboos

  • Resolution set to fixed
  • Status changed from new to closed

Done so in [8788].

comment:12 Changed 2 years ago by admin@…

  • Resolution fixed deleted
  • Status changed from closed to reopened

This seems to still be a problem.

I have setup tools 0.6c11 when running easy_install http://svn.edgewall.org/repos/trac/trunk it throws the following

Processing dependencies for Trac==0.12dev-r0
Searching for Genshi>=0.6dev-r1072
Reading http://pypi.python.org/simple/Genshi/
Reading http://genshi.edgewall.org/
Reading http://genshi.edgewall.org/wiki/Download
No local packages or download links found for Genshi>=0.6dev-r1072
error: Could not find suitable distribution for Requirement.parse('Genshi>=0.6dev-r1072')

comment:13 follow-up: Changed 2 years ago by rblank

  • Resolution set to fixed
  • Status changed from reopened to closed

Until Genshi 0.6 is released, you must install Genshi from SVN:

easy_install http://svn.edgewall.org/repos/genshi/trunk

comment:14 in reply to: ↑ 13 Changed 22 months ago by Laurens Blanckenborg <laurens@…>

Replying to rblank:

Until Genshi 0.6 is released, you must install Genshi from SVN:

easy_install http://svn.edgewall.org/repos/genshi/trunk

As I don't know where to put this suggestion, I decided to post it here. Please inform me if there's a more suitable way to make a suggestion like this.

Today, I decided to upgrade my Trac-environment after using my current environment (12dev r8206) for more than a year. Everything went OK, except for the Genshi error as stated in this ticket (r0-issue).

The problem was easily solved by updating setuptools to the newest setuptools (0.6c11), but I couldn't find that solution quickly in the Installation Guide, so I had to search for it. Via Google I found some messages which put me on the right track.

My suggestion is to add a remark to the Installation Guide, so that other users don't need to search for it. Something like this:

...

...

But... I'm not sure if 0.6c10 will work, so I decided to add a comment here instead of editing the Install Guide itself.

View

Add a comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
The resolution will be deleted. Next status will be 'reopened'
to The owner will be changed from cboos. Next status will be 'closed'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.