Opened 4 years ago

Closed 4 years ago

# Unable to compile

Reported by: Owned by: patrick.little@… Steffen Hoffmann normal AnnouncerPlugin normal setuptools svn-1.7 0.12

My organization uses VisualSVN and it's Trac plugin to host our environment. Therefore I have to compile plugins as eggs and then install them through the web admin interface. (I do not get command access to the server.)

To match the server environment, I installed the same server programs on my machine so that I can build compatible eggs. This has worked with several other plugins, but I'm unable to get a compile to proceed.

VisualSVN includes Trac 0.12.3 and python 2.6.6

running bdist_egg
Traceback (most recent call last):
File "setup.py", line 87, in <module>
**extra
File "C:\VisualSVNServer\trac\python\lib\distutils\core.py", line 152, in setup
dist.run_commands()
File "C:\VisualSVNServer\trac\python\lib\distutils\dist.py", line 975, in run_commands
self.run_command(cmd)
File "C:\VisualSVNServer\trac\python\lib\distutils\dist.py", line 994, in run_command
cmd_obj.ensure_finalized()
File "C:\VisualSVNServer\trac\python\lib\distutils\cmd.py", line 117, in ensure_finalized
self.finalize_options()
File "C:\VisualSVNServer\trac\python\lib\site-packages\setuptools-0.6c11-py2.6.egg\setuptools\command\bdist_egg.py", line 94, in finalize_options
File "C:\VisualSVNServer\trac\python\lib\distutils\cmd.py", line 319, in get_finalized_command
cmd_obj.ensure_finalized()
File "C:\VisualSVNServer\trac\python\lib\distutils\cmd.py", line 117, in ensure_finalized
self.finalize_options()
File "C:\VisualSVNServer\trac\python\lib\site-packages\setuptools-0.6c11-py2.6.egg\setuptools\command\egg_info.py", line 85, in finalize_options
File "C:\VisualSVNServer\trac\python\lib\site-packages\setuptools-0.6c11-py2.6.egg\setuptools\command\egg_info.py", line 185, in tags
File "C:\VisualSVNServer\trac\python\lib\site-packages\setuptools-0.6c11-py2.6.egg\setuptools\command\egg_info.py", line 233, in get_svn_revision
IndexError: list index out of range


### comment:1 Changed 4 years ago by Ryan J Ollos

Description: modified (diff)

I've seen this issue before. You are using SVN 1.7.x?

### comment:2 Changed 4 years ago by patrick.little@…

VisualSVN 2.5.1 runs SVN 1.7.1

### comment:3 Changed 4 years ago by Ryan J Ollos

Please try removing tag_svn_revision = true from setup.cfg. I think this is a known issue and I'm working on digging up previously reported information.

### comment:4 follow-up:  7 Changed 4 years ago by Ryan J Ollos

The issue seems to be that setuptools doesn't support SVN 1.7 metadata: #9565, #9709, mailing list, t:#10658, setuptools issue #79.

There seem to be some ways to workaround the issue:

• Remove the line tag_svn_revision = true form setup.cfg, or set it to tag_svn_revision = false.
• Download the zip archive and run easy_install or setup.py bdist_egg on the extracted archive rather than a working copy.
• Run easy_install tracaccountmanager to install directly from PyPI.

I haven't tested any of those methods myself, so please report back if you have success with any particular one of them.

hasienda: I suggest we close this as invalid since it's an installation issue. We could make a note about this on the AccountManagerPlugin page, but it affects all plugins and the note is unlikely to be read, so I think we just need to be mindful of the issue and continue to deal with the installation issues as they arise on the mailing list and in the issue tracker.

### comment:5 Changed 4 years ago by patrick.little@…

Yes, the setup completes after removing that line. I'll keep that in mind for other plugins as well.

I agree with hasienda that this issue is resolved. For those same reasons I did not want to mark this ticket as a defect or an enhancement, leaving it as the only remaining type [task].

Thank you for the quick response time :) Now to get my IT department to upgrade the environment.

### comment:6 Changed 4 years ago by Ryan J Ollos

One other note for future reference: from reading various resources, it appears that another valid workaround is to install the setuptools_subversion package.

### comment:7 in reply to:  4 ; follow-up:  8 Changed 4 years ago by Steffen Hoffmann

Resolution: → worksforme new → closed

The issue seems to be that setuptools doesn't support SVN 1.7 metadata ...

hasienda: I suggest we close this as invalid since it's an installation issue. We could make a note about this on the AccountManagerPlugin page, but it affects all plugins and the note is unlikely to be read, so I think we just need to be mindful of the issue and continue to deal with the installation issues as they arise on the mailing list and in the issue tracker.

Hm, I remember you introducing this config option. I'm fine with your suggestion, because anything apart from removing that option would not be effective in the long run. Most of the users won't RTFM, very true.

Special thanks to the OP for being that mindful to not claim a plugin defect for this issue.

### comment:8 in reply to:  7 ; follow-up:  11 Changed 4 years ago by Ryan J Ollos

... because anything apart from removing that option would not be effective in the long run.

I hadn't considered removing it until you mentioned now. The value of the option is that we can more easily determine the SVN revision for users that choose to install from the trunk using Subversion (SVN revision is shown in error reports, on the plugin admin panel, on the About page). However, in light of this defect, it might be worth considering to remove the option from setup.cfg. Maybe, we should keep that under consideration and see if it gets to be more of a problem as SVN 1.7 gains more widespread usage.

### comment:9 Changed 4 years ago by patrick.little@…

Could you instead use SubWCRev to determine/encode the SVN rev of the trunk the user built from?

### comment:10 Changed 4 years ago by Ryan J Ollos

That might work if we only had to worry about the Windows platform ;) It sounds similar to the solution proposed in setup tool issue #79, using the SVN client to get the query the WC metadata.

### comment:11 in reply to:  8 Changed 4 years ago by Steffen Hoffmann

... because anything apart from removing that option would not be effective in the long run.

I hadn't considered removing it until you mentioned now. The value of the option is that we can more easily determine the SVN revision for users that choose to install from the trunk using Subversion (SVN revision is shown in error reports, on the plugin admin panel, on the About page).

Yes, reasonable and potentially helpful. That's why I didn't complain before.

However, in light of this defect, it might be worth considering to remove the option from setup.cfg.

Well, I'm not married to it either, and was thinking straight and loud.

Maybe, we should keep that under consideration and see if it gets to be more of a problem as SVN 1.7 gains more widespread usage.

Agree.

### comment:12 Changed 4 years ago by Ryan J Ollos

Resolution: worksforme → cantfix

### comment:13 follow-up:  14 Changed 2 years ago by anonymous

I would like to apply the remedy 'Remove the line tag_svn_revision = true form setup.cfg, or set it to tag_svn_revision = false' for I situation where I encounter the same error when trying to install with 'sudo easy_install -Z -U http://trac-hacks.org/svn/xmlrpcplugin/trunk'. Where would I find or place that setup.cfg?

### comment:14 in reply to:  13 Changed 2 years ago by Ryan J Ollos

I would like to apply the remedy 'Remove the line tag_svn_revision = true form setup.cfg, or set it to tag_svn_revision = false' for I situation where I encounter the same error when trying to install with 'sudo easy_install -Z -U http://trac-hacks.org/svn/xmlrpcplugin/trunk'. Where would I find or place that setup.cfg?

You'll need to checkout the source from SVN. The file is located here: xmlrpcplugin/trunk/setup.cfg. Instructions for checkout from SVN are found here: XmlRpcPlugin#DownloadandSource. See trac:TracPlugins for more info on installing Trac plugins. Again, please ask on the trac:MailingList if you have more questions (I assume this is the same commenter as comment:11:ticket:9709 and SO:27032905).

### comment:15 Changed 2 years ago by anonymous

Thx, now works with checkout, etc.. Indeed same commenter as comment:11:ticket:9709. Will sign up to mailing list.

### Modify Ticket

Change Properties