Port Install Troubleshooting

Latest revision as of 20:11, 20 November 2007

[edit] Common port install troubleshooting

[edit] Hosed port - can't install or deinstall

Sometimes a ports is 'hosed', that is not fully installed but not fully deinstalled either (usually as the result of interrupting a "make install").

After you verify that you're dealing with a port or package, not software you've installed outside the ports/packages system, you can try the following:

cd /var/db/pkg
ls -l | grep NameOfHosedPort

rm -rf NameOfHosedPort or rm -rf NameOfHosedPort-[version-number] as the ls command indicated.

then

pkgdb -F

Then you can build the port again.

If any port has NameOfHosedPort as a dependency, you should deinstall and reinstall them to make sure you don't stay with a hard-to-track bug later as you eventually forget about this install incident.

To know what the dependencies of NameOfHosedPort are, do THIS

[edit] Broken or forbidden ports

If the port is important for your work you should upgrade to a secure version, find an alternative port to do the job, or if you are feeling like taking a risk (usually on a non-internet-connected workstation) you can tolerate a forbidden port.

Ports that are too insecure for normal use or cause systemwide problems are listed HERE.

[edit] Lack of hard drive space after installing many ports

Think about backuping it first. Once it's done (or skipped at your own risk), use make distclean but if you ever have to build any of your ports again you'll have to fetch them again which can be time-consuming and occasionally frustrating as day-fresh ports are sometimes broken or unavailable.

Many people choose to archive their distfiles directory on CDs once in a while just in case an obscure dependency or a marginally supported port is unavailable/broken. The more ports you rely on, the more archiving them can be a timesaver when you need to get a workstation doing a certain task ASAP!

[edit] Advanced troubleshooting

...