Re: Package with changed PLIST can't be updated?

[Thomas Klausner <wiz%NetBSD.org@localhost>]

On Sun, Jun 15, 2014 at 01:30:53AM +0000, Thomas Mueller wrote:
> Error messages look like
> 
> => Bootstrap dependency digest>=20010302: found digest-20121220
> ===> Building binary package for ruby200-subversion-1.8.9
> => Creating binary package /usr/packages/All/ruby200-subversion-1.8.9.tgz
> /bin/ln -f 
> /BETA1/pkgsrc/devel/ruby-subversion/work699.amd64/.packages/ruby200-subversion-1.8.9.tgz
>  /usr/packages/All/ruby200-subversion-1.8.9.tgz 2>/dev/null ||  /bin/cp -pf 
> /BETA1/pkgsrc/devel/ruby-subversion/work699.amd64/.packages/ruby200-subversion-1.8.9.tgz
>  /usr/packages/All/ruby200-subversion-1.8.9.tgz
> ===> Install binary package of ruby200-subversion-1.8.9
> pkg_add: Conflicting PLIST with ruby193-subversion-1.8.3nb1: 
> lib/libsvn_swig_ruby-1.la
> pkg_add: 1 package addition failed
> *** Error code 1

The problem here is that the default ruby version switch from 1.9.x to
2.0.x. ruby-subversion is now build against ruby200, but nothing
deleted the old version (since the update didn't understand that the
default changed and thus didn't knew that it should delete
ruby193-subversion).

> Same thing happened with lang/gcc48 (conflicting PLIST).

Some time ago, the gcc48 package was split into more packages, and the
updater didn't know that either.

Just delete ruby193-subversion or gcc48 and try again, and it should
be fine.
 Thomas