Mailing List Archive: Trac: Users

Unsupported version control system "svn", Trac broken between [11050] and [11125]

Index | Next | Previous | View Threaded

jeffbuhrt at gmail

Jul 17, 2012, 12:40 PM

Post #1 of 5 (336 views)
Permalink

Unsupported version control system "svn", Trac broken between [11050] and [11125]

Somewhere between Trac changesets [11050] (0.13) and [11125] the trunk
(dev) Trac broke access to svn. Best guess is [11082] broke it.
*
Warning:* Can't synchronize with repository "(default)" (Unsupported
version control system "svn": Can't find an appropriate component, maybe
the corresponding plugin was not enabled? ). Look in the Trac log for more
information.

After reviewing what seems like one of the top issues from a couple years
ago, comparing the two revisions and noticing the refactoring of files like
trac/versioncontrol/svn_fs.py, ./trac/versioncontrol/svn_prop.py, etc. and
working through the tests in
http://trac.edgewall.org/wiki/TracSubversion#unsupported-vcs ... I gave up
for now and reverted back to [11050], things seem fine again.

I assume others will hit this also.

My config on the machine with Trac:
httpd-2.2.15-1.fc12.2.i686
mod_python-3.3.1-11.i686
subversion-1.6.13-1.fc12.1.i686

There are no errors in the log while set to debug, I only see svn things
like:
2012-07-17 12:48:54,115 Trac[loader] DEBUG: Loading
tracopt.versioncontrol.svn.svn_fs from
/usr/lib/python2.6/site-packages/Trac-1.0dev_r11125-py2.6.egg
2012-07-17 12:48:54,116 Trac[loader] DEBUG: Loading
tracopt.versioncontrol.svn.svn_prop from
/usr/lib/python2.6/site-packages/Trac-1.0dev_r11125-py2.6.egg

I see that mod_python shows deprecated (seems seem to show as
optional/supported). Nothing else on the machine has changed and reverting
to [11050] makes things work fine.

While using [11050], in General -> Repositories -> Type dropdown on the
right contains: (default), direct-svnfs, svn, svnfs; with a Default: svn
While using [11125] the dropdown only contains '(default)'

If you have something else to try, please let me know.

Thanks & FYI,

-Jeff

--
You received this message because you are subscribed to the Google Groups "Trac Users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/trac-users/-/Q1B4b7IJsRoJ.
To post to this group, send email to trac-users [at] googlegroups
To unsubscribe from this group, send email to trac-users+unsubscribe [at] googlegroups
For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.

christian.boos at free

Jul 17, 2012, 1:52 PM

Post #2 of 5 (323 views)
Permalink

Re: Unsupported version control system "svn", Trac broken between [11050] and [11125] [In reply to]

On 7/17/2012 9:40 PM, Jeff Buhrt wrote:
> Somewhere between Trac changesets [11050] (0.13) and [11125] the trunk
> (dev) Trac broke access to svn. Best guess is [11082] broke it.
> *
> Warning:* Can't synchronize with repository "(default)" (Unsupported
> version control system "svn": Can't find an appropriate component, maybe
> the corresponding plugin was not enabled? ). Look in the Trac log for
> more information.
>
> After reviewing what seems like one of the top issues from a couple
> years ago, comparing the two revisions and noticing the refactoring of
> files like trac/versioncontrol/svn_fs.py,
> ./trac/versioncontrol/svn_prop.py, etc. and working through the tests in

> http://trac.edgewall.org/wiki/TracSubversion#unsupported-vcs ... I gave
> up for now and reverted back to [11050], things seem fine again.
>

Please visit that link again, I've documented the r11082 change a bit
more. Basically you just need to explicitly enable the new optional
component (tracopt.versioncontrol.svn.* = enable, in the [components]
section of you <env>/conf/trac.ini file). Sorry for the disruption,
we'll emphasize this point in the upgrade notes.

-- Christian

--
You received this message because you are subscribed to the Google Groups "Trac Users" group.
To post to this group, send email to trac-users [at] googlegroups
To unsubscribe from this group, send email to trac-users+unsubscribe [at] googlegroups
For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.

manu.blot at gmail

Jul 18, 2012, 1:34 AM

Post #3 of 5 (309 views)
Permalink

Re: Unsupported version control system "svn", Trac broken between [11050] and [11125] [In reply to]

> Please visit that link again, I've documented the r11082 change a bit more.
> Basically you just need to explicitly enable the new optional component
> (tracopt.versioncontrol.svn.* = enable, in the [components] section of you
> <env>/conf/trac.ini file). Sorry for the disruption, we'll emphasize this
> point in the upgrade notes.

IMHO, the "upgrade" command should automatically update the
[components] section to transparently enable back SVN when SVN was
already used for the upgraded environment. There are already far too
many ways to fail a Trac installation, maybe this one could be
avoided. It took me about one work day to replicate a Trac environment
from our server to a local development machine. I'm not a Trac expert,
but I used to know Trac and I bumped into half a dozen issues when
performing this replication (most of them are due to Trac
dependencies). Upgrade should be as seamless as possible, I believe.
Upgrading is always a risky task, reducing the risk to stop the
service for hours would be great.

Just my two cents - I know it is far easier to give advice than to
work on the implementation ;-)

Cheers,
Manu

--
You received this message because you are subscribed to the Google Groups "Trac Users" group.
To post to this group, send email to trac-users [at] googlegroups
To unsubscribe from this group, send email to trac-users+unsubscribe [at] googlegroups
For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.

remy.blank at pobox

Jul 18, 2012, 1:57 AM

Post #4 of 5 (310 views)
Permalink

Re: Unsupported version control system "svn", Trac broken between [11050] and [11125] [In reply to]

Emmanuel Blot wrote:
> IMHO, the "upgrade" command should automatically update the
> [components] section to transparently enable back SVN when SVN was
> already used for the upgraded environment.

I tend to agree with this, but it has one drawback: currently, when we
programmatically rewrite trac.ini, we throw away comments and
formatting. But maybe that's not really a problem.

-- Remy

Attachments:

signature.asc (0.19 KB)

manu.blot at gmail

Jul 18, 2012, 2:04 AM

Post #5 of 5 (308 views)
Permalink

Re: Unsupported version control system "svn", Trac broken between [11050] and [11125] [In reply to]

> I tend to agree with this, but it has one drawback: currently, when we
> programmatically rewrite trac.ini, we throw away comments and
> formatting. But maybe that's not really a problem.

IIRC this also happends whenever the conf file is updated through the
administration panel, right?
I guess that if the existing config file is backed up, it is less
intrusive to ditch comments than to leave Trac upgrade with a
non-functional installation�

Cheers,
Manu.

--
You received this message because you are subscribed to the Google Groups "Trac Users" group.
To post to this group, send email to trac-users [at] googlegroups
To unsubscribe from this group, send email to trac-users+unsubscribe [at] googlegroups
For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads