doesn’t install the Apache module anymore: update your OPTIONS and build www/mod_php5 port instead

Another thing i came upon today, which happens to have an easy fix, is this:

When you upgraded your ports, and some option got changed, you will probably get:

doesn’t install the Apache module anymore: update your OPTIONS and build www/mod_php5 port instead

Now, since you already upgraded the ports tree, the option that you should uncheck and reconfigure the port is already gone, so you can’t fix it like that.

What you can do, is remove and reconfigure ports options, in my case being the php5-extensions

What i did was:

cd /usr/ports/lang/php5-extensions

make rmconfig-recursive

then:

make config-recursive

You will be prompted to reconfigure the options, and your upgrading will work just fine

Activate FreeBSD ipfw without recompiling the kernel

This has been bugging me quite a bit, i used to recompile the kernel every time just to add ipfw support.

In FreeBSD 10, you can do it without rebuilding the kernel:

net.inet.ip.fw.default_to_accept=”1″
ipfw_load=”YES”

Add the above to /boot/loader.conf – create the file if it’s not already there.

Reboot and you’re good to go!

FREEBSD_INSTALL failed with error 19

Finally i managed to sort this one out. I was installing a FreeBSD 10 box, and after the kernel loads, i got this error.

The fix is not really hard, all you need to do is wait about 10 – 20 seconds, and afterwards type in the correct boot sequence:

mountroot> cd9660:/iso9660/FREEBSD_INSTALL

Afterwards the kernel will load and the installation will start

cups-client-1.7.2 conflicts with cups-image-1.5.4_1 (installs files into the same place)

If you are getting the error below while trying to upgrade ports:

cups-client-1.7.2 conflicts with cups-image-1.5.4_1 (installs files into the same place)

This happens because of the cups-image dependencies have been changed. The fix is pretty easy:

pkg delete -f cups-image\*

Now you can upgrade the cups-client and ghostscript ports without issues.

Enjoy

py27-setuptools27-2.0.1 conflicts with py27-setuptools-2.0.1 (installs files into the same place)

If you’re getting :

py27-setuptools27-2.0.1 conflicts with py27-setuptools-2.0.1 (installs files into the same place).

when you are trying to upgrade ports on a FreeBSD installation, this happens because the dependencies were changed.

A quick easy fix is:

pkg set -o devel/py-setuptools:devel/py-setuptools27
cd /usr/ports/devel/py-setuptools27
make deinstall
make reinstall

Enjoy

Upgrade perl 5.12 / 5.14 to 5.16 or later on FreeBSD – How to

So if you’re me, and you’re using ports for everything on a FreeBSD server, you will notice pretty soon that the perl is kinda out of date, compared to current.

What can we do about it ? It’s fairly easy but it took a few trial and errors till i got the things rolling:

pkg set -o lang/perl5.14:lang/perl5.16 or pkg set -o lang/perl5.12:lang/perl5.16

portupgrade -o lang/perl5.16 -f perl-5.14.\* or  portupgrade -o lang/perl5.16 -f perl-5.12.\*

portupgrade -rf perl*

Do, did, done

FreeBSD pkgng how to

So as it seems, in 2014 a bunch of changes happened in FreeBSD:

First off we have the pkg_* system being deprecated. The switch to pkgng is pretty straightforward though, and i upgraded 2 servers without issues:

1 – cd /usr/ports/ports-mgmt/pkg && make install distclean

2 – mkdir -p /usr/local/etc/pkg/repos

3 – pico /usr/local/etc/pkg/repos/FreeBSD.conf

add the following to that file:

FreeBSD: {
url: “pkg+http://pkg.FreeBSD.org/${ABI}/latest”,
mirror_type: “srv”,
enabled: yes
}

4 – cp /usr/local/etc/pkg.conf.sample /usr/local/etc/pkg.conf

5 – run pkg2ng to convert the db: pkg2ng

6 – pico /etc/make.conf and add the following line:

WITH_PKGNG=yes

You’re done!

ld:/usr/src/sys/conf/ldscript.amd64:9: syntax error

So, with the previous BSD 8.3 to 9.1 upgrade botched, i did a second one, and this time it worked pretty much without issues, however:

1 – As usual, i had all ports upgraded and sorted out whatever pkgdb issues existed, or ports that did not want to build.

2 – REBUILD and INSTALL the GENERIC kernel. Usually works by doing freebsd-update fetch && freebsd-update install and reboot.

3 – run freebsd-update to upgrade to 9.1

4 – After all the install is finished, if you get: ld:/usr/src/sys/conf/ldscript.amd64:9: syntax error if you are trying to recompile the kernel to add ipfw capability for instance, then you need to do the following:

cd /usr/src;make buildworld && make buildkernel KERNCONF=katmai_amd64 && make installkernel KERNCONF=katmai_amd64
#reboot
make installworld

where katmai_amd64 is my custom kernel, but you should have your own.

It seems that doing buildworld actually builds the necessary “build toolchain” used for the buildkernel portion (the results are in /usr/obj).  Failure to do that results in the buildkernel its using the already-installed-on-the-system compiler/build toolchain (e.g. the stuff in /usr), which may not be compatible with the version of the kernel source you’re trying to build.

curl Unrecognized archive format

This usually happens on versions lower than 8.3 of FreeBSD due to some changes in the supported formats.

Easy fix is to do the following:

cd /usr/ports/archivers/libarchive
make install distclean

ln -sf /usr/local/bin/bsdtar /usr/bin/tar

snapshot corrupt – portsnap FreeBSD

If you encounter this error by any means, you can download a new snapshot file like this:

rm /var/db/portsnap/tag && portsnap fetch extract