This file documents some of the problems you may encounter when

upgrading your ports. We try our best to minimize these disruptions,

but sometimes they are unavoidable.

You should get into the habit of checking this file for changes each

time you update your ports collection, before attempting any port

upgrades.

20050224:

AFFECTS: users of lang/ruby18 and any apps that depend on ruby18

AUTHOR: mezz@FreeBSD.org

The theads support has been disabled again. It causes the more trouble, so

it now builds with ${PTHREAD_CFLAGS} and ${PTHREAD_LIBS}. It is recommend

you to rebuild any apps that depend on lang/ruby18. Do something like this:

portupgrade -rf ruby-1.8.2\*

20050224:

AFFECTS: users of www/apache21

AUTHOR: clement@FreeBSD.org

When upgrading from 2.1.2, you need to rebuild all apache modules.

20050215:

AFFECTS: users of databases/mysql41-server

AUTHOR: ale@FreeBSD.org

The base database directory can now be set and changed in rc.conf (default:

/var/db/mysql). If you used to set DB_DIR to a different value during port

compilation, you must specify it via the new "mysql_dbdir" rc variable.

In addition, the "mysqllimits_enable" and "mysqllimits_args" variables

have been replaced by "mysql_limits" for consistency.

20050214:

AFFECTS: users of net-mgmt/nagios

AUTHOR: blaz@si.FreeBSD.org

Nagios has been upgraded to 2.0.b2. Native support for storing various types

of data (status, retention, comment, downtime, etc.) in MySQL and PostgreSQL

has been dropped. There are also multiple changes to the format of

configuration files. Carefully read

http://nagios.sourceforge.net/docs/2_0/whatsnew.html before upgrading.

20050213:

AFFECTS: users of print/teTeX-*

AUTHOR: hrs@FreeBSD.org

print/teTeX-* are now based on teTeX 3.0. Although some

reliability fixes are also added, here are several common problems

which you might fall on.

1) $PREFIX/bin/pdftex is missing:

Probably your system has old files included teTeX 2.x which can

prevent the new version from working. Please remove the old

files first (see 20050206 in this file) and reinstall.

2) Some formats are still corrupted (for example, "Fatal format file error;

I'm stymied" is displayed) or not updated even after a clean install:

You might have old or corrupted *.fmt and/or *.map files

under /root/.texmf-* or $HOME/.texmf-* directories. Typically

these directories are generated when you invoke the updmap(1),

texconfig(1), or fmtutil(1) utility manually. However, for a period

after the first revision of the teTeX-base port erroneously used

fmtutil(1) to regenerate *.fmt files, you could have these directories

without your intent. In such a case, please remove these directories

and reinstall the ports (it is not needed to rebuild ports/packages).

Just for your information, $HOME/.texmf-config and $HOME/.texmf-var

can be used for your personal configuration.

If you have other problems, please contact hrs@FreeBSD.org.

20050212:

AFFECTS: users of x11-fonts/mkbold, mkitalic and mkbold-mkitalic

AUTHOR: koma2@ms.u-tokyo.ac.jp

The dependency on x11-fonts/mkbold and x11-fonts/mkitalic has been

switched over to x11-fonts/mkbold-mkitalic, which is written in C

and has far better performance than the old ones. There is no

functional difference between the two, but they will conflict with

each other. Since other ports which depend on x11-fonts/mkbold or

x11-fonts/mkitalic will be updated to depend on x11-fonts/mkbold-mkitalic,

you might get an error during upgrading such ports. In such a case,

please pkg_delete the old ones first.

20050206:

AFFECTS: users of print/teTeX and japanese/teTeX

AUTHOR: hrs@FreeBSD.org

print/teTeX is now based on a teTeX 3.0 release candidate

(2.99.13.20050204) and the other related ports are also updated.

Since upgrading from previous versions should be done at a time,

you may want to use the portupgrade utility or reinstall

print/teTeX after deinstalling all of the related ports.

If your teTeX environment became broken during the upgrade,

please see the following URL which explains how to fix it.

http://people.freebsd.org/~hrs/tetex-upgrade.txt

This file also includes notes for people who are familiar

with the teTeX distribution to explain structure of the ports.

20050205:

AFFECTS: users of lang/ruby16_r, lang/ruby18_r and lang/ruby18

AUTHOR: knu@FreeBSD.org

The slippery pthread support for systems prior to 502102 has been

dropped and lang/ruby16_r and lang/ruby18_r ports have been removed,

since no one seems to appreciate the partially working solution.

Good news is that the pthread support of lang/ruby18 is now enabled

by default for newer systems, which means the ruby interpreter is

linked with libpthread. This will allow threaded extension

libraries to run and work properly on those systems.

20050201:

AFFECTS: users of lang/perl5 and lang/perl5.8

AUTHOR: tobez@FreeBSD.org

lang/perl5 has been updated to 5.6.2, and lang/perl5.8 has been

updated to 5.8.6. you should update everything depending on perl, that

is:

* first, upgrade your perl installation (use either lang/perl5 or

lang/perl5.8, the latter being recommended);

* for FreeBSD 4.X, run "use.perl port", so that the system knows you

have 5.8.6 or 5.6.2; this step is not needed on FreeBSD 5.X and

FreeBSD -CURRENT;

* run some magic incantations to upgrade all ports depending on perl,

that is run something like :

portupgrade -f `(pkg_info -R perl-5\* |tail +4; \

find /usr/local/lib/perl5/site_perl/5.[68].[1245] -type f -print0 \

| xargs -0 pkg_which -fv | sed -e '/: ?/d' -e 's/.*: //')|sort -u`

This is likely to fail for a few ports, you'll have to upgrade them

afterwards by hand.

20050130:

AFFECTS: users of PostgreSQL

AUTHOR: girgen@FreeBSD.org

Each of the PostgreSQL ports have been split into a server and a

client part. Please use postgresqlNN-server and/or

postgresqlNN-client as needed. Versions currently supported are 7.3,

7.4 and 8.0.

To start the PostgreSQL server at boot time, add the following to

/etc/rc.conf:

postgresql_enable=yes

The maintainance script is installed in etc/periodic/daily, and is

controlled by a set of new knobs in periodic.conf. Use it for

vacuuming your databases and get daily backups. Note that daily

vacuuming is on by default. See the script for details.

20050130:

AFFECTS: users of net/howl

AUTHOR: marcus@FreeBSD.org

Howl now installs an rcNG script for starting mDNSResponder. To enable

mDNSResponder to start at boot time, add the following to /etc/rc.conf:

mdnsresponder_enable="YES"

You can also pass flags to mDNSResponder by setting the rc.conf variable

mdnsresponder_flags to the appropriate value. See the mDNSResponder(8)

man page for the list of supported flags. The default is not to pass

any flags to mDNSResponder.

20050126:

AFFECTS: users of x11-wm/xfce4

AUTHOR: oliver@FreeBSD.org

If you use Xorg 6.8.1: Make shure there is an /tmp/.ICE-unix with propper

rights. For further informations about that, please refer to 20041229

Please update all your plugins as well when you update from 4.0.6 to 4.2

They all need recompiling to link against the new xfce libraries

20050122:

AFFECTS: users of PostgreSQL

AUTHOR: seanc@FreeBSD.org

The -devel port has been updated to contain 8.0 release since

postgresql80-server can not be updated until 4.11 is released and the

changes in PR ports/75344 are committed. Users who need 8.0 now can

use the -devel port, however, once postgresql80-server has been

committed, -devel will begin tracking 8.1. Please be smart about

tracking ports and if used in production, update to

databases/postgresql80-server as soon as it becomes available. No

dump/reload will be required when changing from -devel to

postgresql80-server.

20050117:

AFFECTS: users of mail/spambnc

AUTHOR: thierry@FreeBSD.org

The SpamBouncer has been upgraded from version 1.9 to 2.0-RC3, and you

have to modify your ~/.procmailrc files. Please read upgrading.html in

/usr/local/share/doc/spambnc.

20050117:

AFFECTS: users of astk-client

AUTHOR: thierry@FreeBSD.org

ASTK has been moved; if there exists files $HOME/.astkrc/config_serveurs,

you have to update the entry rep_serv from /usr/local/ASTK/ASTK_SERV/bin

to /usr/local/aster/ASTK/ASTK_SERV/bin (or you can remove $HOME/.astkrc).

20050114:

AFFECTS: users of security/libgnomesu, esp. on FreeBSD 4.x.

AUTHOR: adamw@FreeBSD.org

If you installed libgnomesu the day it was added to the ports tree,

you have a malformed PAM control file in /etc/pam.d/. All libgnomesu

users should remove /etc/pam.d/gnomesu-pam, and 5.x users should

replace it with the version in the updated libgnomesu port (ensure

that you're using the most current revision of the libgnomesu port).

4.x users: listen up! The presence of the /etc/pam.d/ directory (and

anything in that directory) presents a Very Bad Thing. Unless you've

manually tweaked your PAM settings, you must run:

# rm /etc/pam.d/gnomesu-pam

# rmdir /etc/pam.d/

or all users will be locked out of your system!

20050110:

AFFECTS: users of irc/iip

AUTHOR: lioux@FreeBSD.org

iip has been updated to the new network servers. Therefore, both

old configuration files and node reference keys no longer apply.

Therefore, you need to update the configuration files for each

user running the iip isproxy daemon:

1) Backup configuration files

cp ~/.iip/isproxy.ini ~/.iip/isproxy.ini.backup

cp ~/.iip/node.ref ~/.iip/node.ref.backup

2) Remove configuration files

rm ~/.iip/isproxy.ini

rm ~/.iip/node.ref

3) Create new configuration. Fill information as requested. This

creates the updated isproxy.ini file

isproxy -C

4) Start iip isproxy. This will initialize your updated node.ref

file. This file will be automatically updated when you connect

to the iip network

isproxy

20050110:

AFFECTS: users of sysutils/nautilus-cd-burner

AUTHOR: gnome@FreeBSD.org

Nautilus-cd-burner now requires cdrtools built with UTF-8 encoding

support. The default sysutils/cdrtools port does not support this

encoding, and that will cause nautilus-cd-burner to enter an infinite

loop when trying to create CD images. To workaround this, the cdrtools

dependency was changed in nautilus-cd-burner to point to the

sysutils/cdrtools-cjk port instead.

Since sysutils/cdrtools and sysutils/cdrtools-cjk conflict, you must

uninstall cdrtools so that the nautilus-cd-burner update can properly

pull in cdrtools-cjk.

20050108:

AFFECTS: users of mail/courier-imap, mail/sqwebmail

AUTHOR: oliver@FreeBSD.org

Courier-imap and sqwebmail are now dependent on courier-authlib. If

you've changed the default authentication config for courier-imap or

sqwebmail, you will have to redo the changes for courier-authlib.

You may wish to deinstall courier-imap and/or sqwebmail before you

install courier-authlib. Since courier-authlib replaces parts of both

ports, some of courier-authlib's files are listed as sqwebmail and

courier-imap files and deinstalling old courier-imap and/or sqwebmail

port may cause the deinstallation of the freshly installed

courier-authlib files.

20050108:

AFFECTS: users of mail/sqwebmail

AUTHOR: oliver@FreeBSD.org

Sqwebmail now installs it's files directly under PREFIX. That means for

instance that files that were formerly found under

PREFIX/share/sqwebmail/etc/ are now located under PREFIX/etc/sqwebmail.

Furthermore you need to set sqwebmaild_enable=YES in your rc.conf

because the rc.d script has been migrated to use the rc.subr Subsystem

20050108:

AFFECTS: users of mail/courier-imap

AUTHOR: oliver@FreeBSD.org

The variable courier_imap_imapdssl_enable have been renamed to

courier_imap_imapd_ssl_enable.

The variable courier_imap_pop3dssl_enable have been renamed to

courier_imap_pop3d_ssl_enable.

userdb stuff is now located in LOCALBASE/etc/authlib instead of

LOCALBASE/etc.

20041231:

AFFECTS: users of www/awstats

AUTHOR: webmaster@lightningfire.net

Location of awstats changed from /usr/local/www to /usr/local/www/awstats.

Please update configuration according instructions in pkg-message.

20041231:

AFFECTS: users of the linux compatibility environment

AUTHOR: netchild@FreeBSD.org

The default linux_base was changed from v7 to v8. You need to update from

v7 to v8 and rebuild every linux port. To update run:

portupgrade -rf -o emulators/linux_base-8 emulators/linux_base

In case you already use linux_base-8 you have to run:

portupgrade -rf emulators/linux_base-8

20041229:

AFFECTS: users of x11/kdebase3, x11-servers/xorg-server

AUTHOR: lofi@freebsd.org

If KDE does not start anymore after upgrading Xorg to version 6.8.1

(X restarts when the KDE splash screen has reached the third icon),

please check whether the directory /tmp/.ICE-unix exists, is owned by root

and has permissions 1777 (read/write/access for everybody + sticky bit).

To make sure everything is in working order, do (as root):

mkdir -p /tmp/.ICE-unix && chmod 1777 /tmp/.ICE-unix &&

chown root:wheel /tmp/.ICE-unix

Also, make sure you do NOT have clear_tmp_enable="YES" set in /etc/rc.conf,

as it will remove the directory on every reboot and applications will re-

create it with the wrong ownership.

Users of daily_clean_tmps_enable in /etc/periodic.conf should make sure

daily_clean_tmps_ignore contains /tmp/.ICE-unix.

20041227:

AFFECTS: users of lang/gambas

AUTHOR: thierry@FreeBSD.org

As of this update, the password of your databases connections are crypted.

If you were using the database manager, please remove

~/.gambas/gambas-database-manager.conf before launching the new version.

20041226:

AFFECTS: users of Horde and the related ports (Turba, IMP, Nag, Kronolith,

Mnemo, Chora)

AUTHOR: thierry@FreeBSD.org

As of this update, the configuration files are generated by the application,

with no support for configuration files used in previous versions.

All data saved in the database, LDAP or MCAL backends will be preserved,

considering that you run specific scripts to migrate to this new scheme.

Affected ports are www/horde, mail/turba, deskutils/nag, deskutils/kronolith,

and deskutils/mnemo. See the UPGRADING documentation of the ports in question

for more details.

The filter system of IMP 3.x has been replaced by a separate application:

check the port mail/ingo. Ingo provides a script to migrate the existing

filter rules from IMP 3.x, see Ingo's documentation.

20041224:

AFFECTS: users of x11-servers/XFree86-4-Server and graphics/dri

AUTHOR: lesi@FreeBSD.org

As of version 4.4.0_6, XFree86-4-Server now depends on

graphics/xfree86-dri. This is due to incompatibilities between

XFree86 and the new xorg 6.8.1 DRI.

Users of XFree86-4-Server are strongly encouraged to switch to

the xfree86-dri port as follows:

portupgrade -fo graphics/xfree86-dri graphics/dri

which will also fix dependencies.

20041224:

AFFECTS: users of sysutils/portupgrade and lang/ruby18

AUTHOR: knu@FreeBSD.org

Please upgrade sysutils/portupgrade prior to lang/ruby18, or

pkgdb(1) may coredump with a double free() problem from a misuse (or

a "feature") of the DL module.

In that case, you can reinstall sysutils/portupgrade manually.

20041222:

AFFECTS: users of security/clamav, security/clamav-devel

AUTHOR: jylefort@brutele.be

The ClamAV database path has changed from /usr/local/share/clamav to

/var/db/clamav. You should update the DatabaseDirectory keyword in

/usr/local/etc/clamd.conf and /usr/local/etc/freshclam.conf.

20041221

AFFECTS: users of security/gpgme03

AUTHOR: clement@FreeBSD.org

security/gpgme03 has been modified to not conflicts with gpgme 1.x

After upgrade, you need to rebuild all ports that depend on it.

You should upgrade security/gpgme (if installed) to avoid nasty

compile time failures, due to original location of gpgme.h.

20041219:

AFFECTS: users of textproc/jdictionary

AUTHOR: hq@FreeBSD.org

The location for JDictionary port installed files has changed. This also

affects the various plugins. Hence, users should upgrade all jdictionary

related ports at once to avoid inconsistencies:

$ portupgrade jdictionary\*

20041214:

AFFECTS: users of net/freenet6

AUTHOR: edwin@FreeBSD.org

The FreeNet6 Service must now be enabled / disabled in rc.conf:

freenet6_enable="YES"

20041213:

AFFECTS: users of security/cryptplug, deskutils/kdepim3

AUTHOR: lofi@freebsd.org

The cryptplug port is not compatible with recent versions of gpgme

and has been changed to depend on gpgme03 (the last version of gpg-

me compatible with cryptplug).

Users who have been using cryptplug in order to enable PGP/MIME support

in KMail should DEINSTALL BOTH cryptplug and gpgme03 before updating

KDE to version 3.3.2. Cryptplug is NOT necessary anymore to enable

PGP/MIME support in KMail and will cause the kdepim3 build to fail due

to conflicting dependencies.

20041213:

AFFECTS: users of databases/postgresql-relay

AUTHOR: edwin@FreeBSD.org

The PostgreSQL Relay must now be enabled / disabled in rc.conf:

postgresqlrelay_enable="YES"

20041212:

AFFECTS: users of sysutils/bacula

AUTHOR: lkoeller@FreeBSD.org

The port was split into a -server and -client component.

The -server part contains the storage and director daemon, the -client

part the console, file daemon and the documentation.

For migration delete the bacula port and install the -server and/or

-client port afterwards.

20041208:

AFFECTS: users of mail/getmail

AUTHOR: question+fbsdports@closedsrc.org

There is a known quirk when using mail/getmail with Python 2.4

where the DeprecationWarning is printed regarding the use of

the 'strict' keyword when a message is being retrieved.

You can redirect stdout/stderr to /dev/null to quelch the warning.

The quirk may be fixed in a future version of getmail.

20041205:

AFFECTS: users of multimedia/ffmpeg

AUTHOR: lioux@FreeBSD.org

multimedia/ffmpeg will not work if previous versions of the port

are installed. Also, there is a shared library version bump on

this update. Therefore:

1) Remove old ffmpeg

pkg_delete -f /var/db/pkg/ffmpeg*

2) Install updated ffmpeg

3) Rebuild all ports that depend on ffmpeg due to the shared

library version bump

cd /var/db/pkg && portupgrade -rf ffmpeg* -x ffmpeg*

20041202:

AFFECTS: users of any ports which have dependency on lang/python

AUTHOR: perky@FreeBSD.org

After upgrading of lang/python, you must rebuild all its consumer

ports to make them get ready to Python 2.4.

To do this, you will need to:

pkgdb -uf && cd /usr/ports/lang/python && make upgrade-site-packages

20041128:

AFFECTS: users of mail/dspam and mail/dspam-devel

AUTHOR: itetcu@people.tecnik93.com

When upgradng from previous version, read mail/dspam/files/UPDATING

and adjust your options.

20041121:

AFFECTS: users of news/rawdog

AUTHOR: tim@bishnet.net

Rawdog 2.x changes the format of the state file used in 1.x. To

upgrade from 1.x to 2.x the rawdog author recommends the following:

cp -R ~/.rawdog ~/.rawdog-old

rm ~/.rawdog/state

rawdog -u

rawdog --upgrade ~/.rawdog-old ~/.rawdog

rawdog -w

Once you're happy with the new version:

rm -r ~/.rawdog-old

20041118:

AFFECTS: users of sysutils/portupgrade

AUTHOR: lofi@freebsd.org

portsdb(1) is part of the portupgrade suite and is used to convert a ports

INDEX file to a binary INDEX.db database. By default, it uses the

libc-builtin berkeley db to do so, which has a buggy btree implementation.

If you see errors like "[BUG] Segmentation fault" while a portsdb update is

in progress, adjust the PORTS_DBDRIVER variable (in your environment or in

pkgtools.conf) to either bdb1_hash or dbm_hash.

This problem was fixed in 5.3-RELEASE, but users of 4.10-RELEASE and

5.2.1-RELEASE (and older releases) will find fixes by updating to the

latest (at least after Sep 20) of RELENG_4 or RELENG_5.

20041116:

AFFECTS: users of www/bricolage

AUTHOR: ports@rbt.ca

Bricolage may now be run on mod_perl compiled as a DSO for Apache

when following these guidelines:

http://perl.apache.org/docs/1.0/guide/install.html#When_DSO_can_be_Used

To do this, you will need to:

pkg_delete -f apache-mod_perl

pkg_delete -f p5-libapreq-static

portupgrade -rR bricolage

Bricolage will rebuild mod_perl, apache and libapreq using their standard

versions.

20041115:

AFFECTS: users of sysutils/portupgrade

AUTHOR: lofi@FreeBSD.org

Due to the recent removal of INDEX and INDEX-5 from FreeBSD's CVS,

portupgrade with default configuration will run 'make index' if started

after cvsup'ing the ports-collection. This may take an undesirably long

time.

There are several ways to work around this, for example:

- Run 'make fetchindex' after cvsup'ing ports.

or

- Adjust the PORTS_INDEX variable in your environment or in

pkgtools.conf (see portupgrade(1) or the default pkgtools.conf) to

a different value than the default.

Also remember that 'make index' is only supported on _complete_

ports-trees. If you are currently refusing whole categories by means

of a cvsup refuse file, use 'make fetchindex' instead (or consider

keeping an extra machine/jail with a complete ports-tree around to

do INDEX builds on).

20041111:

AFFECTS: users of audio/faad, multimedia/mpeg4ip

AUTHOR: lioux@FreeBSD.org

mpeg4ip has been updated and broken down into 2 separate ports:

mpeg4ip and mpeg4ip-libmp4v2. Furthermore, mpeg4ip now depends

on faad. Moreover, faad now depends on mpeg4ip-libmp4v2 rather

than on mpeg4ip which avoids a cyclic dependency (mpeg4ip depends

on faad which depends on mpeg4ip).

If any of the old ports are installed, mpeg4ip will not compile.

Therefore,

1) Remove old faad and mpeg4ip ports which conflict with new

mpeg4ip

pkg_delete -f /var/db/pkg/mpeg4ip*

pkg_delete -f /var/db/pkg/faad*

2) Install faad, mpeg4ip and mpeg4ip-libmp4v2 in the following

order

cd /usr/ports/multimedia/mpeg4ip-libmp4v2 && make install clean

cd /usr/ports/audio/faad && make install clean

cd /usr/ports/multimedia/mpeg4ip && make install clean

20041111:

AFFECTS: users of java

AUTHOR: glewis@FreeBSD.org

javavmwrapper has been rewritten. It now creates symbolic links for

all executables of the Java VMs that have been registered with it.

These symbolic links may impact which version of Java you are using,

depending on your PATH, which may need to be adjusted.

For example, if your path is:

${LOCALBASE}/bin:${LOCALBASE}/jdk1.4.2/bin

then previously "java" would resolve to ${LOCALBASE}/jdk1.4.2/bin/java.

With the new javavmwrapper it will resolve to ${LOCALBASE}/bin/java.

Depending upon the Java VMs that are registered and various environment

variables, it may or may not be ${LOCALBASE}/jdk1.4.2/bin/java that is

run by javavmwrapper via the symbolic link ${LOCALBASE}/bin/java.

20041107:

AFFECTS: users of x11/kdebase3

AUTHOR: kde@freebsd.org

To use GMail in konqueror, you need to set the browser identification for

gmail.google.com to 'Safari 1.2.3 on Mac OS X', otherwise you will not be

able to click on any links in GMail after logging in.

You can set site-specific browser identifications via the Settings menu in

Konqueror (Configure Konqueror/Browser Identification) or in the KDE Control

Center, Internet & Network/Web Browser/Browser Identification.

20041107:

AFFECTS: all users who have any GNOME libraries installed

AUTHOR: adamw@FreeBSD.org and the rest of the FreeBSD/GNOME crew

Hey, 2.6! You don't have to be 2.6 anymore!

Do NOT use portupgrade(1) to update your GNOME 2.6 desktop to 2.8:

it won't work, and you'll have to recompile bunches of ports by hand

as a result. Use the gnome_upgrade.sh script to automate the upgrade

process. The script is available from

http://www.FreeBSD.org/gnome/gnome_upgrade.sh

20041104:

AFFECTS: users of security/clamav-devel

AUTHOR: rob@debank.tv

The configuration file was renamed from clamav.conf to clamd.conf,

make sure to move your configuration before restarting the server.

20041104:

AFFECTS: users of japanese/rskkserv

AUTHOR: rushani@FreeBSD.org

The format of PREFIX/etc/rskkserv.conf has changed in version 2.95.

Please update your configuration file before restarting the server

using PREFIX/share/examples/rskkserv/conf-o2n.rb and referring to

PREFIX/share/examples/rskkserv/rskkserv.conf.sample.

20041031:

AFFECTS: users of databases/mysql40-server

AUTHOR: ale@FreeBSD.org

The MySQL Daemon must now be enabled / disabled in rc.conf.

See the script for details.

20041028:

AFFECTS: users of net/netatalk

AUTHOR: marcus@FreeBSD.org

Please note that the handling of the default type/creator has changed with

2.0.1. As a side effect, users upgrading from earlier versions, including

2.0.0, will have to remove the default type/creator from the

AppleVolumes.System file. The install process will not modify this file

automatically. Please remove the line starting with '. "????"'

manually.

This text was taken from the Netatalk 2.0.1 release notes at

https://sourceforge.net/project/shownotes.php?release_id=278320.

20041027:

AFFECTS: users of games/pcgen

AUTHOR: hq@FreeBSD.org

The launcher script for PCGen has been renamed to 'pcgen' (formerly

'pcgen.sh').

20041024:

AFFECTS: users of databases/mysql50-server

AUTHOR: ale@FreeBSD.org

The MySQL Daemon must now be enabled / disabled in rc.conf.

See the script for details.

20041024:

AFFECTS: users of mail/popfile

AUTHOR: matusita@FreeBSD.org

Since there is a known problem that popfile doesn't work with DBD::SQLite 1.x

at this time, you'll be in trouble after upgrading databases/p5-DBD-SQLite

to the latest one. A workaround is commited to 0.22.0_1 which uses

databases/p5-DBD-SQLite2 by default. However, if already installed popfile,

please check ${HOME}/.popfile/popfile.cfg, and change the line

"bayes_dbconnect dbi:SQLite:dbname=$dbname" to

"bayes_dbconnect dbi:SQLite2:dbname=$dbname" then restart popfile.

20041023:

AFFECTS: users of mail/dbmail

AUTHOR: seanc@FreeBSD.org

When upgrading from 1.X to 2.X, read the upgrading instructions.

The structure of the database has changed, please use the migration

scripts provided. Many of the programs have been renamed and arguments

have been changed as well.

20041020:

AFFECTS: users of security/antivir-milter

AUTHOR: marius@FreeBSD.org

When updating from previous versions of security/antivir-milter to

antivir-milter-1.1 and you had changed PREFIX/etc/avmilter.conf you

have to bring over your changes to PREFIX/etc/avmilter/avmilter.conf

after installing the new version of this port. Note, however, that

some variables have been renamed.

If you used AntiVir Milter ignore, scan and/or warn files in /etc

you can now move them to PREFIX/etc/avmilter.

20041019:

AFFECTS: users of databases/mysql41-server

AUTHOR: ale@FreeBSD.org

The MySQL Daemon must now be enabled / disabled in rc.conf.

See the script for details.

20041018:

AFFECTS: users of mail/courier-imap

AUTHOR: oliver@FreeBSD.org

The courier-imap port must now be enabled / disabled in rc.conf.

See the script for details.

20041015

AFFECTS: users of www/apache2 with devel/apr

AUTHOR: clement@FreeBSD.org

WITH_APR_FROM_PORTS knob is no longer supported, since apr > 1.0

doesn't conflict with apache2's one. If you use apr 0.9.x you

won't be able to upgrade apache2 anymore.

20041014:

AFFECTS: users of security/clamav

AUTHOR: eik@FreeBSD.org

The configruration file for the clamd daemon has changed from

/usr/local/etc/clamav.conf to /usr/local/etc/clamd.conf.

20041013:

AFFECTS: users of mail/getmail

AUTHOR: question+fbsdports@closedsrc.org

If you are using a version of mail/getmail earlier than 4.x and

are planning to upgrade to 4.2.2, please note that the configuration file

syntax has changed and the existing configuration file(s) will not work.

Please refer to the online documentation available at:

(http://www.qcc.ca/~charlesc/software/getmail-4/documentation.html)

If you already upgraded to the latest version of getmail, you can refer

to the installed documentation under:

${PREFIX}/share/docs/getmail

The 4.x branch of getmail also requires Python 2.3.3 or newer.

Some mail delivery agents require that the unixfrom parameter to be set to

either "true" or "false" in the configuration file.

A "quick and dirty" guide on setting up, configuring and using getmail is

available at:

(http://qnd-guides.net/qnd-getmail.html)

20041012:

AFFECTS: users of devel/perforce

AUTHOR: marshall@chezmarshall.com

Upgrading from 2003.2 to 2004.2 is straightforward, it is highly

recommended to checkpoint and backup your server as follows:

p4 verify //...

p4 verify -u //... # possibly redundant

p4 admin checkpoint

p4 admin stop

<backup repository>

If you are upgrading from a version earlier than 2003.2, you should

consult the Perforce documentation

(http://www.perforce.com/perforce/technical.html)

before proceeding.

Also, it looks as though Perforce has stopped updating the man pages,

so they are no longer included in the port.

20041012:

AFFECTS: users of www/firefox

AUTHOR: freebsd-gnome@FreeBSD.org

After upgrading to firefox-1.0.1.p, certain things such as extension/theme

[de]installation, and "Find On Page" may no longer work. You may also

notice an infinite loop when starting Firefox. If this happens, backup

~/.mozilla/firefox/*/bookmarks.html, and remove ~/.mozilla/firefox.

Afterward, Firefox should start up. You can then restore the bookmarks.html

file to the new ~/.mozilla/firefox/*.default directory.

20041012:

AFFECTS: users of net/netatalk

AUTHOR: marcus@FreeBSD.org

Netatalk has been upgraded to 2.0.0. There are some important

instructions for upgrading from 1.6.x. Please see

http://netatalk.sourceforge.net/2.0/htmldocs/upgrade.html on how

to make the transition.

20041011:

AFFECTS: users of www/linuxpluginwrapper who are running FreeBSD

5.3-BETA7 or later (including -current)

AUTHOR: nork@freebsd.org

According to UPDATING(20041001), /etc/libmap.conf should be fixed

libm.so.2 to libm.so.3.

20041001:

AFFECTS: users of ports that require several base system libraries who

are running FreeBSD 5.3-BETA7 or later (including -current)

AUTHOR: kensmith@freebsd.org

As part of the FreeBSD-5.3 release the following system libraries

had their version number incremented:

/lib/libm.so.2 -> libm.so.3

/lib/libreadline.so.4 -> libreadline.so.5

/usr/lib/libhistory.so.4 -> libhistory.so.5

/usr/lib/libopie.so.2 -> libopie.so.3

/usr/lib/libpcap.so.2 -> libpcap.so.3

This should have no effect unless you are using FreeBSD 5.3-BETA7 or

higher, or if you are a -current user who upgraded after this date.

Assuming you did a from-source upgrade new versions of these libraries

will be created but the old versions will be left behind (for example

/lib/libm.so.2 will be the old one, /lib/libm.so.3 will be the new one).

Any ports or pre-built packages you have currently installed will

continue to use the old library, any ports you install after the upgrade

will begin to use the new library. You will need to have all your

ports recompiled before the old library goes away. To help with the

migration you could also use /etc/libmap.conf to map libm.so.2 to

libm.so.3.

20040903:

AFFECTS: users of net/kdenetwork3

AUTHOR: kde@freebsd.org

The lanbrowsing facility of KDE has been removed from the main

kdenetwork3 port and is now available via the net/lanbrowsing

port.

20040901:

AFFECTS: users of www/squid

AUTHOR: tmseck@netcologne.de

www/squid now installs an rcNG script by default. This means you

need to explicitly enable squid by setting squid_enable=yes in

/etc/rc.conf.

The squid.sh script uses the following variables:

squid_chdir

squid_flags

squid_user

Please see the squid.sh script for further details.

If you want to install an old style rc-script, build the port with

"WITHOUT_SQUID_RCNG=YES" or by rerunning "make config" and disabling this

option.

20040830:

AFFECTS: users of x11/kde3, x11/kdelibs3, x11/kdebase3

AUTHOR: kde@freebsd.org

In KDE 3.3, a number of files were moved between ports and some ports

were removed. This means that you will have to take some precautions

to update your KDE installation. A simple portupgrade -a will not work.

portupgrade -R kde can fail as well, depending on what parts of KDE you

have currently installed. We therefore recommend sticking to the following

procedure. The procedure requires you to have sysutils/portupgrade installed

and you to be the superuser (or using sudo). We recommend not being logged in

to a KDE session on the machine you're performing the upgrade on. If you

choose to perform the update while being logged in to KDE, expect erratic

behaviour and crashes from applications launched during the update.

1.) First, make sure your ports index is up to date.

cd /usr/ports && make index

or, if you're using the sysutils/portindex port

portindex

2.) Delete installed packages which conflict with the updated KDE

ports.

pkg_deinstall -f kdeaddons-kontact-plugins-\* \

kdeaddons-kaddressbook-plugins-\* kdepim-\* kdeutils-\* \

kdeaddons-\[0-9\]\* kde-\[0-9\]\*

kdegraphics now conflicts with the kolourpaint package and kdeedu now

conflicts with the kwordquiz package. If you have kwordquiz and/or

kolourpaint installed on your system and you want to use the kdegraphics/

kdeedu ports, you should first deinstall the conflicting packages:

pkg_deinstall -f kolourpaint\* kwordquiz\*

3.) Now update the remaining KDE ports.

portupgrade arts\* kde\* quanta\*

or, if you want to update KDE along with other updated ports:

portupgrade -a

Note that the quanta port has been renamed to kdewebdev. The commands

above will automatically replace quanta with kdewebdev, if you have

quanta installed.

4.) Reinstall any KDE ports you deleted in step 2. Note that the kdeaddons-

kontact-plugins (net/kontact-plugins), kdepim-kpilot (palm/kpilot) and

quanta (www/quanta) ports/packages do not exist anymore and cannot be

reinstalled.

Known post-updating issues:

- If you're missing acoustic notifications (system sounds) after the update:

rm ~/.kde/share/config/knotifyrc

Then log out of KDE and back in again.

- KMail has been heavily modified since KDE 3.2.x. Testing shows that KMail

can display erratic behaviour and crashes after the update. If you see any

such behaviour, it is recommended to simply close KMail and start it again

until it resumes normal operation.

The integration of GnuPG and KMail for signing, encrypting and verifying

PGP/MIME mail has also changed. A quick howto is available at

http://freebsd.kde.org/howtos/gnupg-kmail.php.

- kdm users might get warnings from kdm about obsolete lines in kdmrc.

You can migrate your configuration while preserving your customizations

by running

genkdmconf

Make sure to backup your old kdmrc (usually found in

/usr/local/share/config/kdm) beforehand in case the merge produces an

invalid configuration.

- Extensive information about changes from KDE 3.2.x can be found at

http://www.kde.org/announcements/changelogs/changelog3_2_3to3_3.php

20040829:

AFFECTS: users of mail/mutt-devel

AUTHOR: udo.schweigert@siemens.com

The defaults of the port have been changed from WITH_MUTT_NCURSES to

WITH_MUTT_SLANG to be in sync with the mail/mutt port. If you really have

problems with slang (which should be a very rare case) be sure to have set

COLORTERM=yes and COLORFGBG="color1;color2" in your environment, or recompile

the port with the WITH_MUTT_NCURSES knob set (e.g. by adding

WITH_MUTT_NCURSES=yes to your /etc/make.conf).

20040828:

AFFECTS: users of security/samba-vscan

AUTHOR: jmelo@freebsdbrasil.com.br

The default location of the configuration files has been changed

from /etc/ to /usr/local/etc and from /etc/samba/ to

/usr/local/etc/samba-vscan/; the default location of the data files

has been changed from /var/run/clamd to /var/run/clamav/clamd and

from /var/opt/f-secure/fsav/databases to /var/db/fsav/databases.

20040820: