From owner-freebsd-ports@FreeBSD.ORG Tue Jul 28 14:36:40 2009 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9F0E810656B2 for ; Tue, 28 Jul 2009 14:36:40 +0000 (UTC) (envelope-from bennett@cs.niu.edu) Received: from mp.cs.niu.edu (mp.cs.niu.edu [131.156.145.41]) by mx1.freebsd.org (Postfix) with ESMTP id 735A98FC21 for ; Tue, 28 Jul 2009 14:36:39 +0000 (UTC) (envelope-from bennett@cs.niu.edu) Received: from mp.cs.niu.edu (bennett@localhost [127.0.0.1]) by mp.cs.niu.edu (8.14.3/8.14.3) with ESMTP id n6SEaNBe027340 for ; Tue, 28 Jul 2009 09:36:24 -0500 (CDT) Date: Tue, 28 Jul 2009 09:36:23 -0500 (CDT) From: Scott Bennett Message-Id: <200907281436.n6SEaNJh027339@mp.cs.niu.edu> To: freebsd-ports@freebsd.org Subject: cups build error needs warning placed into UPDATING X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Jul 2009 14:36:41 -0000 I ran into a problem with the cups update build failing with the following messages. ===> Installing for cups-base-1.3.10_3 ===> Generating temporary packing list ===> Checking if print/cups-base already installed if ! pw groupshow cups; then pw groupadd cups -g 193; fi pw: unknown group `cups' pw: gid `193' has already been allocated *** Error code 65 Stop in /usr/ports/print/cups-base. ===>>> A backup package for cups-base-1.3.10_2 should be located in /usr/ports/packages/portmaster-backup ===>>> Installation of cups-base-1.3.10_3 (print/cups-base) failed ===>>> Aborting update ===>>> Update for cups-base-1.3.10_2 failed ===>>> Aborting update ...and so forth. After much experimentation and head-scratching, it finally dawned on me that the problem was the result of having nscd(8) running and with cacheing enabled for "group" accesses. [eyeballs rolled...] Killing nscd and temporarily editing the "cache" operands out of the lines in /etc/nsswitch.conf solved the problem upon rerunning portmaster. A warning about this ought to be in UPDATING, not only for cups, but for any other builds and installs that alter any of the data typically cached by nscd(8). If these ports are being installed or updated, then nscd should first be taken out of the picture. Scott Bennett, Comm. ASMELG, CFIAG ********************************************************************** * Internet: bennett at cs.niu.edu * *--------------------------------------------------------------------* * "A well regulated and disciplined militia, is at all times a good * * objection to the introduction of that bane of all free governments * * -- a standing army." * * -- Gov. John Hancock, New York Journal, 28 January 1790 * **********************************************************************