portupgrade fails to upgrade the package because the older version is installed

David Southwell david at vizion2000.net
Thu Jul 10 05:25:30 UTC 2008

On Wednesday 09 July 2008 15:09:25 Yuri wrote:
> I got the error below during portupgrade -aP.
> Why wouldn't portupgrade just upgrade neon?
> 'pkgdb -F' doesn;t find any problems.
> Yuri
> ===>  Installing for neon28-0.28.2_1
> ===>  neon28-0.28.2_1 conflicts with installed package(s):
>       neon26-0.26.4_1
>       They install files into the same place.
>       Please remove them first with pkg_delete(1).
> *** Error code 1
> Stop in /usr/ports/www/neon28.

Did you follow the instructions in UPDATING (see below)?

They may have some bearing on the problem.
  AFFECTS: users of devel/subversion*
  AUTHOR: Lev Serebryakov <lev at FreeBSD.org>

  subversion now uses neon-0.28.x (www/neon28) port, and automatic
  portupgrade will fail because neon26 will conflict with installed
  You should upgrade neon library tohgether with subversion with

  # portupgrade -o www/neon28 neon subversion


  Also, if you use special subversion port with bindings, you
  should upgrade your port to clean subversion port with

  # portupgrade -o devel/subversion subversion-\*

  and install needed bindings (p5-subversion, py-subversion and/or
  ruby-subversion) after that.

  If you use subversion with bindings, installed from devel/subversion
  with custom options, don't forget to install separate bindings ports
  after subversion upgrade.


More information about the freebsd-ports mailing list