mickey said:
Looks like you didn't upgrade your perl installation properly, as is suggested in
/usr/ports/UPDATING:
Code:
20090328:
AFFECTS: users of lang/perl*
AUTHOR: skv@FreeBSD.org
lang/perl5.10 is out. If you want to switch to it from, for example
lang/perl5.8, that is:
Portupgrade users:
0) Fix pkgdb.db (for safety):
pkgdb -Ff
1) Reinstall perl with new 5.10:
env DISABLE_CONFLICTS=1 portupgrade -o lang/perl5.10 -f perl-5.8.\*
2) Reinstall everything that depends on Perl:
portupgrade -fr perl
Portmaster users:
env DISABLE_CONFLICTS=1 portmaster -o lang/perl5.10 lang/perl5.8
portmaster -r perl-
Note: If the "perl-" glob matches more than one port you will need to
specify the name of the perl directory in /var/db/pkg explicitly.
That actually just failed, literally just now, on my machine. I got tired of having all my ports with security holes mailed to me each day, so I decided to try an update. Ran Portsnap to get everything, and then thought about how to do the rest.
freebsd-update works like apt-get and doesn't have any issues at all. Ports not being included in security patches, which is like 95% of what most people actually use anyway, means using cvsup, or portsnap, THEN once that is done, using either portupgrade, which has broken my boxes more than I care to count, (Heh, I remember reading "just do portupgrade -af" and having an unusable machine after that) so I decided pormanager and portmaster might be worth a try.
I'm on round 3 now, because it's broke and terminated twice.
I've been using Debian and SUSE for almost 10 years, and I'm a little shocked that someone said something has broken. I've literally not seen SUSE crash, ever. And I've used it as a desktop, a server, and everything else, and rebooting is only for Kernel updates, so, I had pretty good uptime.
And of course updating non base install software doesn't take a week on slower machines. I did ONE have an Nvidia driver update screw up X for me. I told Marcus Meissner, who went into work early that day and fixed it for me. That's the one time I've actually had an issue with SUSE, and the person who wrote the Kernel patch, came in early to take care of it for me.
Right now, portmaster -a is running on my machine. I always install security patches except for ports because it takes so long, and the machine isn't exactly usable while it's happening. And being that I don't code, I don't actually want to sit here telling it how to compile something. But, I'm trying again. It's the reason my server runs Slackware; I can type one line of commands, and everything is upgraded and working. If a Kernel update was there, I reboot, and I'm done. If there wasn't one... I type the command (Like swaret --update && swaret --upgrade or slaptget, or slackpkg, whichever I want to use) and then, it runs, and finishes, and I'm done. No down time.
My Debian machine has been running for about 2 years. It has a lot of stuff running on it, and has about....12,000 things installed? And apt-get update && apt-get upgrade once a day or so, and if there are any, the get installed and I'm done.
I literally not seen much in crashes. And I push hardware pretty hard.
Third party repos exist for basically everything, but be it SUSE, Debian, or whatever, I haven't had any issues. Adding a line of text to sources.list is a lot easier than tarballs ever were.