p5.12-svn-simple : Warning: SVN::Core missing or outdated - installation fails

[dan@…]

I'm running command:

sudo port install git-core +svn

This fails with error:

Error: org.macports.configure for port p5.12-svn-simple returned: configure failure: command execution failed
Error: Failed to install p5.12-svn-simple
Please see the log file for port p5.12-svn-simple for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_perl_p5-svn-simple/p5.12-svn-simple/main.log
Error: The following dependencies were not installed: p5.12-svn-simple

looking at the log file, it seems following is root cause:

===> Warning: SVN::Core missing or outdated.

Version of SVN which is installed is: svn, version 1.7.5 (r1336830)

I am running OSX Lion 10.7.4 having upgraded from Snow Leopard with an earlier version of MacPorts installed

I have followed instructions at wiki:Migration

I have attempted to implement several fixes suggested in response to other tickets to rectify similar sounding issues - but none have worked (sorry - I did not keep a list of every fix I've tried :-\)

[benedikt.huber@…]

Same problem here, fresh macports install on Lion 10.7.4. CC me, git +svn is important!

[benedikt.huber@…]

Cc Me!

[benedikt.huber@…]

The problem here is that although subversion-perlbindings were installed, they seemed to be broken. Investigating (additional line breaks by me):

perl -e 'use SVN::Core; print "$SVN::Core::VER_MAJOR.$SVN::Core::VER_MINOR.$SVN::Core::VER_MICRO"'
Can't locate SVN/Core.pm in @INC \
(@INC contains: /opt/local/lib/perl5/site_perl/5.12.4/darwin-thread-multi-2level \
                /opt/local/lib/perl5/site_perl/5.12.4 /opt/local/lib/perl5/vendor_perl/5.12.4/darwin-thread-multi-2level \
                /opt/local/lib/perl5/vendor_perl/5.12.4 /opt/local/lib/perl5/5.12.4/darwin-thread-multi-2level \
                /opt/local/lib/perl5/5.12.4 \
                /opt/local/lib/perl5/site_perl \
                /opt/local/lib/perl5/vendor_perl .) at -e line 1.

Although there is a SVN/Core.pm on the system in

/opt/local/lib/perl5/vendor_perl/5.12.4/darwin-multi-2level/

perl cannot find it, as this directory is not in @INC. No idea why, but a workaround which worked for me was

sudo port install subversion-perlbindings +universal
sudo port install p5.12-svn-simple

Now, I have a working git+svn :)

[danielluke (Daniel J. Luke)]

For people who are having this problem, do you have subversion-perlbindings 1.7.5_1 installed (or do you have the pre-revbumped version installed?) There were some changes made to perl5 and all of the perl modules were revbumped to force them to rebuild.

[dan@…]

Replying to benedikt.huber@…:

Thanks - that sorted it for me :)

[dan@…]

Replying to dluke@…:

For people who are having this problem, do you have subversion-perlbindings 1.7.5_1 installed (or do you have the pre-revbumped version installed?) There were some changes made to perl5 and all of the perl modules were revbumped to force them to rebuild.

Not sure - I did a full uninstall + clean + install of subversion-perlbindings - which did not help.

sudo port -f uninstall subversion-perlbindings
sudo port clean subversion-perlbindings
sudo port install subversion-perlbindings

Following @benedikt's instructions:

sudo port -f uninstall subversion-perlbindings
sudo port clean subversion-perlbindings
sudo port install subversion-perlbindings  +universal

Resolved the issue and allowed p5.12-svn-simple (and git-core +svn) to be installed

[danielluke (Daniel J. Luke)]

Replying to dan@…:

Not sure - I did a full uninstall + clean + install of subversion-perlbindings - which did not help.

port installed will tell you the version you installed.

port info subversion-perlbindings will tell you the version that is available to you (in your local copy of the portfiles).

My guess is that you have 1.7.5_0 and that you happened to sync your portfiles after the perl change but before subversion-perlbindings was revbumped. If that's true, doing a port selfupdate (or port sync) followed by port upgrade outdated should fix it for you.

Doing the install with +universal keeps you from getting the 1.7.5_0 package from the buildbot which was built against the previous perl.

Of course, there could be something else going on, in which case we'll want to figure out what the problem is and get it fixed.

[benedikt.huber@…]

@dluke@…: uninstall/update/upgrade/install worked for me:

$ port uninstall subversion-perlbindings p5.12-svn-simple git-core
$ port selfupdate
$ port upgrade outdated
Error: No ports matched the given expression
$ port install git-core +svn
$ port installed subversion-perlbindings
The following ports are currently installed:
  subversion-perlbindings @1.7.5_1 (active)
$ port installed p5.12-svn-simple
The following ports are currently installed:
  p5.12-svn-simple @0.280.0_3 (active)
$ port installed git-core
The following ports are currently installed:
  git-core @1.7.11.1_0+credential_osxkeychain+doc+pcre+python27+svn (active)

[dan@…]

Okay..

$ port installed
...
subversion-perlbindings @1.7.5_0+universal (active)
...
$ port info subversion-perlbindings
subversion-perlbindings @1.7.5 (devel, perl)
Variants:             no_bdb, no_neon, universal

Description:          Subversion (svn) is a version control system designed to be as similar to cvs(1) as possible, while fixing many outstanding problems with cvs(1). The perl bindings provide access to subversion API from perl.
Homepage:             http://subversion.apache.org/

Library Dependencies: expat, neon, apr, apr-util, db46, subversion, perl5, gettext, libiconv, serf1, cyrus-sasl2, sqlite3
Platforms:            darwin
License:              Apache-2
Maintainers:          dluke@geeklair.net, blair@macports.org

When I attempt port selfupdate, I get the following:

$ port selfupdate
--->  Updating MacPorts base sources using rsync
Error: /opt/local/bin/port: port selfupdate failed: Error synchronizing MacPorts sources: command execution failed

Is that pertinent?

[danielluke (Daniel J. Luke)]

Replying to dan@…:

Okay.. subversion-perlbindings @1.7.5_0+universal (active)

So the problem is (entirely) that you need to selfupdate and upgrade subversion-perlbindings

When I attempt port selfupdate, I get the following:

$ port selfupdate
--->  Updating MacPorts base sources using rsync
Error: /opt/local/bin/port: port selfupdate failed: Error synchronizing MacPorts sources: command execution failed

Is that pertinent?

It explains why you don't have the current version of the subversion-perlbindings port.

See ​https://trac.macports.org/wiki/FAQ#selfupdatefails

You can post to the users mailing list if you need additional help troubleshooting selfupdate.

[dan@…]

Replying to dluke@…:

Turned out to be a permissions issue - I needed to sudo port selfupdate - all sorted now

Thanks for spending the time to investigate and identify what turns out to be a pbcak issue.

[jan.pingel@…]

I'm encountering the same error, '===> Warning: SVN::Core missing or outdated.' on 10.8 with XCode 4.4.

Mikuru:oyster jpingel$ perl -MSVN::Core -e 'print $SVN::Core::VERSION."\n";' 1.7.5 Mikuru:oyster jpingel$ port info subversion-perlbindings subversion-perlbindings @1.7.5, Revision 1 (devel, perl)

Uninstalling subversion and subversion-perlbindings and then reinstalling has not helped and I encountered the same failure with subversion-perlbindings +universal when trying to install p5.12-svn-simple for git-core +svn.

I'm running the latest macports according to selfupdate and all outdated ports have been upgraded:

Mikuru:oyster jpingel$ sudo port selfupdate ---> Updating MacPorts base sources using rsync MacPorts base version 2.1.2 installed, MacPorts base version 2.1.2 downloaded. ---> Updating the ports tree ---> MacPorts base is already the latest version

[danielluke (Daniel J. Luke)]

Replying to jan.pingel@…:

I'm encountering the same error

You might be, but since this bug report was caused by a specific issue that was solved after selfupdate, you need to open a _new_ bug explaining what you did, what the error was, and attach the relevant data to it.

FYI though - this stuff installs fine on 10.8 with Xcode 4.4, so it's very likely something specific to your system.