From owner-freebsd-ports@FreeBSD.ORG Sun Mar 20 11:54:43 2011 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 7FB27106566C; Sun, 20 Mar 2011 11:54:43 +0000 (UTC) (envelope-from stb@lassitu.de) Received: from gilb.zs64.net (gilb.zs64.net [IPv6:2001:470:1f0b:105e::1ea]) by mx1.freebsd.org (Postfix) with ESMTP id 4AAFA8FC1A; Sun, 20 Mar 2011 11:54:43 +0000 (UTC) Received: by gilb.zs64.net (Postfix, from stb@lassitu.de) id A30681025A2; Sun, 20 Mar 2011 12:54:41 +0100 (CET) From: Stefan Bethke Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Sun, 20 Mar 2011 12:54:40 +0100 Message-Id: To: freebsd-ports@freebsd.org, Alex Dupre Mime-Version: 1.0 (Apple Message framework v1082) X-Mailer: Apple Mail (2.1082) Cc: Subject: mysql-client-5.5.10 fails to install properly, breaking all dependant ports 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: Sun, 20 Mar 2011 11:54:43 -0000 Since last year, updates to mysql-client-5.5.x kept breaking all = dependant ports, including the server itself. Apparently, the client = library could not be located, thus triggering a re-install of the = client, which failed because the client was already installed. At the = same time, the old binaries would not be able to find the client = library, because the so version had been bumped. I finally found the culprit, after trying to replicate the situation in = a sandbox (instead of on my main mail server): the ${PREFIX)/lib/mysql = dir is created with the standard umask, instead of overriding the bits. In my particular case, the umask is set to 0002 instead of the default = 0022, leaing to a lib dir with rwxrwxr-x. ldconfig(8) refuses to take = libs from group-writable directories. It appears that the mkdir for this dir is somewhere inside the install = target of MySQL, so I'n not certain what the easiest way would be to fix = the permission bits. I've updated my portupgrade script to reset the umask to avoid similar = problems Stefan --=20 Stefan Bethke Fon +49 151 14070811