From owner-freebsd-questions Fri Jul 26 10:27: 8 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5A3B537B400 for ; Fri, 26 Jul 2002 10:27:05 -0700 (PDT) Received: from mailout10.sul.t-online.com (mailout10.sul.t-online.com [194.25.134.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E00143E42 for ; Fri, 26 Jul 2002 10:27:04 -0700 (PDT) (envelope-from timewax@web.de) Received: from fwd07.sul.t-online.de by mailout10.sul.t-online.com with smtp id 17Y8rd-00022i-06; Fri, 26 Jul 2002 19:26:53 +0200 Received: from worldinashell.worldinashell.2y.net (520060406082-0001@[80.128.180.29]) by fmrl07.sul.t-online.com with smtp id 17Y8rS-28PK52C; Fri, 26 Jul 2002 19:26:42 +0200 Date: Fri, 26 Jul 2002 19:26:44 +0200 From: Bauer To: Darren Crotchett Cc: freebsd-questions@FreeBSD.ORG Subject: Re: portupgrade aftermath Message-Id: <20020726192644.51794926.timewax@web.de> In-Reply-To: <200207260833.10965.backdoc@crotchett.com> References: <200207260833.10965.backdoc@crotchett.com> X-Mailer: Sylpheed version 0.8.0 (GTK+ 1.2.10; i386-portbld-freebsd4.6) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Sender: 520060406082-0001@t-dialin.net Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, On Fri, 26 Jul 2002 08:33:10 -0500 Darren Crotchett wrote: > Quick background: > I'm trying to transition from complete newbie to newbie-admin. In > other words, I can handle most of the basics of getting a system up > and going. Now I want to learn how properly admin a FreeBSD box. I'm > running 4.6-RELEASE. Due to the recent security issues involving php, > apache and openssh, I thought that I would try to upgrade all of my > installed ports/packages. Things went OK but, not great. I have a > couple of questions. Here's how I did what I did: > > cvsup -g -L 2 /path/to/ports-supfile You should always run portsdb -uU after you updated your ports to rebuild the INDEX > After running portupgrade, I was greeted with the following message: > > ** The following packages were not installed or upgraded (*:skipped > /!:failed) > ! databases/mysql323-server (mysql-server-3.23.49) (install > error)! devel/ruby-fnmatch (ruby-fnmatch-1.1b_1) (port > directory error)* sysutils/portupgrade (portupgrade-20020429) > > The first question I have is what to do about those messages? > mysql-server 3.23.51is the version I have in /usr/ports. I wonder why > portupgrade had trouble installing? Should I try manually installing > it? What command line options should I use with portupgrade for that? I don't know if this is the best way, but I always try a portupgrade -r port and look at the exact error make gives. > I don't know how important ruby-fnmatch is. But, I don't know of any > specific reason why I need it. So, I'm not too worried about it. > But, I don't care to have loose ends. So, I do want to deal with it > properly. What should I do with it? Try to run portsdb -uU and then upgrade this port again. > Finally, this last part is more a comment than a question. After > upgrading, phpBB and mailman quit working. I discovered that mysql > was no longer set to start on boot (which is why phpBB wouldn't work). > And, mailman is back to > giving me UID/GID problems (I always have to edit my Makefile and > recompile it). I think I can take care of both of these problems. > But, why would portupgrade leave my services unusable? It seems like > if it had problems, it would be smart enough to back out and give you > a message. Run make options in mail/mailman. You can set some options at build time including UID/GID . Also look at the -M option with portinstall/portupgrade. Then have a look at man make.conf . You can set permanent variables for ports there to make sure they are always used on your upgrades. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message