autoconf & automake~pkg-renamed cruft in pkg db - how to fix?

[Baptiste Daroussin]

On Mon, Dec 15, 2014 at 04:38:02PM -0700, Mike Brown wrote:
> One of the ports on my system needs automake, but somehow its name has been 
> butchered in the pkg database.
> 
> ===>>> Launching 'make checksum' for net/GeoIP in background
> ===>>> Gathering dependency list for net/GeoIP from ports
> ===>>> Launching child to update automake~pkg-renamed~8513-1.14 to automake-1.14_1
> ===>>> GeoIP-1.6.2_1 >> automake~pkg-renamed~8513-1.14 (1/1)
> ===>>> No valid installed port, or port directory given
> ===>>> Try portmaster --help
> ===>>> Update for automake~pkg-renamed~8513-1.14 failed
> ===>>> Aborting update
> 
> # pkg info auto\*
> autoconf-wrapper-20130530
> autoconf~pkg-renamed~9939-2.69
> autoconf~pkg-renamed~CD89-2.13.000227_6
> automake-wrapper-20130530
> automake~pkg-renamed~8513-1.14
> automake~pkg-renamed~D475-1.4.6_6
> 
> How do I clean up this mess?
> 
You were having some very very old packages installed which have named collision
this has been fixed during the last years.

pkg 1.4 automatically renamed the collision to avoir upgrade failures.

To fix that you can pkg delete them and reinstall automake and autoconf which
will give you only the latest packages (where the name is fixed)

regards,
Bapt
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 181 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20141216/cc8ed99c/attachment.sig>