New Ticket     Tickets     Wiki     Browse Source     Timeline     Roadmap     Ticket Reports     Search

Ticket #19382 (closed defect: duplicate)

Opened 4 years ago

Last modified 4 years ago

Failed dependency for subversion port

Reported by: david@… Owned by: dluke@…
Priority: Normal Milestone:
Component: ports Version: 1.7.1
Keywords: Cc:
Port: subversion

Description

When attempting to install subversion 1.6.1 on Leopard, I encountered the following:

warning: no debug map in executable (-arch i386)
/bin/sh /usr/local/var/macports/build/_usr_local_var_macports_sources_rsync.macports.org_release_ports_devel_subversion/work/subversion-1.6.0/libtool --tag=CC --silent --mode=compile /usr/bin/gcc-4.0 -I/usr/local/include   -DDARWIN -DSIGPROCMASK_SETS_THREAD_MASK -no-cpp-precomp  -I/usr/local/include/apr-1   -I/usr/local/include/apr-1 -I/usr/local/include  -O2     -I./subversion/include -I./subversion -I/usr/local/include/apr-1   -I/usr/local/include/apr-1 -I/usr/local/include -I/usr/local/include/neon -I/usr/local/include -I/usr/local/include/serf-0  -o subversion/libsvn_ra_serf/auth.lo -c subversion/libsvn_ra_serf/auth.c
In file included from subversion/libsvn_ra_serf/auth.c:23:
subversion/libsvn_ra_serf/ra_serf.h:40:2: error: #error Please update your version of serf to at least 0.3.0.
make: *** [subversion/libsvn_ra_serf/auth.lo] Error 1

Error: Status 1 encountered during processing.

In looking, I already had serf 0.2.0 installed for another port, and the subversion port did not correctly instruct port to upgrade serf as a part of the install process or prompt me to upgrade. I was able to upgrade serf manually and proceed with the install.

Change History

comment:1 Changed 4 years ago by macsforever2000@…

  • Owner changed from macports-tickets@… to dluke@…
  • Port changed from subversion 1.6.1 to subversion

comment:2 Changed 4 years ago by raimue@…

ports are never automatically upgraded before install.

comment:3 Changed 4 years ago by jmr@…

I'm inclined to dupe this to #126. It's specifically about variants rather than versions, but the mechanism for a fix would be mostly the same.

comment:4 Changed 4 years ago by dluke@…

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

I think there is another base ticket for adding version-specific dependencies, so yes, this is a duplicate.

Basically - the current ports tree is at best self-consistent per sync.

So, if you do a port sync, the next thing should be port upgrade outdated.

comment:5 Changed 4 years ago by anonymous

  • Milestone Port Bugs deleted

Milestone Port Bugs deleted

Note: See TracTickets for help on using tickets.