Solved orphaned: lang/perl5.14

formaltux

formaltux

Dear gurus,

Please help me resolve this issue with orphaned perl.
Code: 
root@somehost:/root # pkg version -vIL=
perl5.14-5.14.4_13                 ?   orphaned: lang/perl5.14

root@somehost:/usr/ports/lang/perl5.16 # pkg autoremove
Checking integrity... done (0 conflicting)
Nothing to do.
Thanks.
 
The default version of Perl is 5.18 and has been for quite some time. You even appear to have missed Perl 5.16. Please read /usr/ports/UPDATING:
Code: 
20141126:
  AFFECTS: users of lang/perl5.*
  AUTHOR: mat@FreeBSD.org

  The directories where Perl modules are installed has changed.  All
  affected ports' PORTREVISION have been bumped, so upgrading should
  be as painless as possible.  The old directories have been kept in
  the default Perl @INC to make it even more painless.

  The default Perl has been switched to lang/perl5.18.  These examples
  are for switching from lang/perl5.16, if you are running a different
  version, replace lang/perl5.16 with the origin of the Perl you have
  installed.

  Binary package users:

    # pkg upgrade -f

  Portupgrade users:
    0) Fix pkgdb.db (for safety):
        pkgdb -Ff

    1) Reinstall new version of Perl (5.18):
        portupgrade -o lang/perl5.18 -f lang/perl5.16

    2) Reinstall everything that depends on Perl:
        portupgrade -fr lang/perl5.18

  Portmaster users:
        portmaster -o lang/perl5.18 lang/perl5.16

        Conservative:
        portmaster p5-

        Comprehensive (but perhaps overkill):
        portmaster -r perl5-

  Note: If the "perl5-" glob matches more than one port you will need to specify
        the name of the installed Perl package explicitly.  You can get its name
        by running: pkg info perl5
 
I managed to get autoconf, I need to replace this renamed autoconf with real devel/autoconf. What is this sorcery?


Code: 
root@somehost:/usr/ports/devel/autoconf # pkg info | grep autoconf
autoconf~pkg-renamed~7D7F-2.69 Automatically configure source code on many Un*x platforms

root@somehost:/usr/ports/devel/autoconf # pkg info autoconf~pkg-renamed~7D7F-2.69
pkg: No package(s) matching autoconf~pkg-renamed~7D7F-2.69

root@somehost:/usr/ports/devel/autoconf # pkg info "autoconf~pkg-renamed~7D7F-2.69"
pkg: No package(s) matching autoconf~pkg-renamed~7D7F-2.69

root@somehost:/usr/ports/devel/autoconf # pkg info 'autoconf~pkg-renamed~7D7F-2.69'
pkg: No package(s) matching autoconf~pkg-renamed~7D7F-2.69

portupgrade -o devel/autoconf -f autoconf~pkg-renamed~7D7F-2.69
.
.
.
====> Compressing man pages (compress-man)
--->  Backing up the old version
pkg: No installed package matching "autoconf~pkg-renamed~7D7F-2.69" found

** Backup failed.
** Listing the failed packages (-:ignored / *:skipped / !:failed)
        ! devel/autoconf (autoconf~pkg-renamed~7D7F-2.69)       (backup error)
 
I'm solving the autoconf issue because:

Code: 
root@somehost:/usr/ports/devel/autoconf # pkg check -d
Checking all packages:   3%devel/automake14 has a missing dependency: devel/autoconf
Checking all packages: 100%

>>> Missing package dependencies were detected.
>>> Found 1 issue(s) in the package database.
 
Packages or ports will install needed dependencies. Something called autoconf~pkg-renamed~7D7F-2.69 should be deleted. autoconf is a build dependency anyway and will only be needed if building from a port.

pkg has an option to install missing dependencies, I think, but I've never used it.
 
How old is this system? It may just be easier to pkg delete -af and start with a fresh up to date system.
 
wblock@ said:
Packages or ports will install needed dependencies. Something called autoconf~pkg-renamed~7D7F-2.69 should be deleted. autoconf is a build dependency anyway and will only be needed if building from a port.

pkg has an option to install missing dependencies, I think, but I've never used it.
Click to expand...

pkg info reports it's there, how do I reference it?

Code: 
root@somehost:/usr/ports/devel/autoconf # pkg delete autoconf~pkg-renamed~7D7F-2.69
Updating database digests format: 100%
Checking integrity... done (0 conflicting)
Package(s) not found!

root@somehost:/usr/ports/devel/autoconf # pkg delete "autoconf~pkg-renamed~7D7F-2.69"
Checking integrity... done (0 conflicting)
Package(s) not found!

root@somehost:/usr/ports/devel/autoconf # pkg delete 'autoconf~pkg-renamed~7D7F-2.69'
Checking integrity... done (0 conflicting)
Package(s) not found!
 
formaltux said:
Don't want to reinstall everything.
Click to expand...
Well, you can spend a couple of days trying to fix everything, or you can spend 10 minutes removing and reinstalling packages. There's no need to reinstall everything, just the packages (not the OS).
 
For enyone else unable to reference ports in pkg delete or such commands that contain
~pkg-renamed~ string in the port name, I was able to reference and delete those by using: pkg delete autoconf\*
 
You must log in or register to reply here.
Back
Top