portupgrade fails to upgrade the package because the older
version is installed
sem at FreeBSD.org
Fri Jul 11 22:02:52 UTC 2008
Andriy Gapon wrote:
> on 10/07/2008 11:18 Yuri said the following:
>> David Southwell wrote:
>>> 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.
>> No, command "portupgrade -o www/neon28 neon subversion" causes the same
>> error message itself.
> Manually deinstall neon26 (you might want to create a backup with
> pkg_create -b) and then install neon28 and then proceed as usual with
> portupgrade -o seems to be broken.
Really? Are you sure you use 2.4.3_2 version?
Anyway using -o should be only with one port. It may work not as you
More information about the freebsd-ports