From owner-freebsd-ports Fri Jun 7 16:50:10 2002 Delivered-To: freebsd-ports@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 5A65737B404 for ; Fri, 7 Jun 2002 16:50:02 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g57No2020546; Fri, 7 Jun 2002 16:50:02 -0700 (PDT) (envelope-from gnats) Received: from altair.mukappabeta.net (altair.mukappabeta.net [194.145.150.157]) by hub.freebsd.org (Postfix) with ESMTP id 08CF137B407 for ; Fri, 7 Jun 2002 16:49:01 -0700 (PDT) Received: by altair.mukappabeta.net (Postfix, from userid 1001) id DBB876D0; Sat, 8 Jun 2002 01:49:32 +0200 (CEST) Message-Id: <20020607234932.DBB876D0@altair.mukappabeta.net> Date: Sat, 8 Jun 2002 01:49:32 +0200 (CEST) From: Matthias Buelow Reply-To: Matthias Buelow To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Subject: ports/39015: ORBit 0.5.17 ports build craps itself 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 >Number: 39015 >Category: ports >Synopsis: ORBit 0.5.17 ports build craps itself >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-ports >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Jun 07 16:50:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Matthias Buelow >Release: FreeBSD 4.5-20020326-STABLE i386 >Organization: >Environment: System: FreeBSD altair.mukappabeta.net 4.5-20020326-STABLE FreeBSD 4.5-20020326-STABLE #4: Sat May 4 17:48:05 CEST 2002 mkb@altair.mukappabeta.net:/usr2/src/sys/compile/ALTAIR i386 >Description: The ORBit 0.5.17 build from a cvsup of about 30 minutes ago bombs out due to a failing patch: ===> Applying FreeBSD patches for ORBit-0.5.17 1 out of 1 hunks failed--saving rejects to src/ORBitutil/orbit-os-config.h.rej >> Patch patch-src::ORBitutil::orbit-os-config.h failed to apply cleanly. >> Patch(es) patch-ab patch-ac patch-ad patch-ae patch-configure.in patch-libIDL::configure patch-libIDL::libIDL-config.in patch-popt::configure patch-src::IIOP::connection.c patch-src::IIOP::giop-msg-buffer.c applied cleanly. *** Error code 1 Is it really necessary that a port gets updated twice within just two days? Especially when it's not done carefully enough to make it actually work? I cvsupped the ports tree on another machine today for building mozilla 1.0, saw, oh well, it needs ORBit 0.5.16, put it on a ZIP, transported it home, only to find out that in the meantime, after cvsupping at home, that ORBit was updated again. Only to find out that it now doesn't build. Such things are really annoying. Why can't a certain version of a port be left alone for at least one or two weeks if there aren't any really serious bugs in it? >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message