From owner-freebsd-ports Sat Jan 4 19:14:49 2003 Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C261337B405; Sat, 4 Jan 2003 19:14:47 -0800 (PST) Received: from mail.dt.e-technik.uni-dortmund.de (krusty.dt.e-technik.Uni-Dortmund.DE [129.217.163.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C2A043E4A; Sat, 4 Jan 2003 19:14:44 -0800 (PST) (envelope-from ma@dt.e-technik.uni-dortmund.de) Received: from m2a2.dyndns.org (krusty.dt.e-technik.uni-dortmund.de [129.217.163.1]) by mail.dt.e-technik.uni-dortmund.de (Postfix) with ESMTP id B9921A381A; Sun, 5 Jan 2003 04:14:35 +0100 (CET) Received: by merlin.emma.line.org (Postfix, from userid 500) id 8A3F172924; Sun, 5 Jan 2003 04:14:32 +0100 (CET) To: freebsd-ports@freebsd.org Cc: re@freebsd.org Subject: WAKE UP _NOW_: BUILD FAILures due to db 4 update From: Matthias Andree Date: Sun, 05 Jan 2003 04:14:32 +0100 Message-ID: User-Agent: Gnus/5.090008 (Oort Gnus v0.08) Emacs/21.2 (i586-suse-linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Dear ports committers, SHORT VERSION: The recent db4 update to 4.1.25 assassinates most of the ports that depend on db4. PR #46755 contains all necessary information, patches and shars to fix the problem. Act now. Please. This has already been broken for too long. LONG VERSION: Throughout December, there was a long ports tree freeze in order to stabilize FreeBSD-5 build failures. Recently, the databases/db4 port was updated to 4.1.25, which is INCOMPATIBLE with the previous 4.0.14 version, at build time (changed function arguments and count) and at link time (different version number libdb4.so.1), and which BREAKS existing installed applications as well as the compile of other ports, look at cfengine2 for an example that failed for me. (The db4 port doesn't even allow itself to be packaged because the pkg-plist is broken, but nevermind.) I filed a PR, ports/46755, which contains: 1. the problem description and a catchy Synopsis/Subject 2. a patch to revert db4 back to 4.0.14 but keeps the fixes that were made 3. a shar with a new databases/db41 port Here, have a short cut to the PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/46755 I REPEAT: the current db4 port BREAKS THE BUILD OF OTHER PORTS that depend on db4. NOW is the time to treat ports/46755, not in an hour, not in a day, but NOW. I'm sure that the db4 ->4.1.25 upgrade is NOT covered by the partial ports thaw. Waiting for the next "unbuildable ports" list... What else does it take to drag ports committers back to life and treat the CRITICAL issue that MUST be fixed on short notice rather than offering them a ready-made bug-fixing feast? Thanks in advance. Yours faithfully, -- Matthias Andree To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message