From owner-freebsd-ports@FreeBSD.ORG Sun Feb 16 04:28:28 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0AE8256B for ; Sun, 16 Feb 2014 04:28:28 +0000 (UTC) Received: from mail.egr.msu.edu (dauterive.egr.msu.edu [35.9.37.168]) by mx1.freebsd.org (Postfix) with ESMTP id C9AF11A94 for ; Sun, 16 Feb 2014 04:28:27 +0000 (UTC) Received: from dauterive (localhost [127.0.0.1]) by mail.egr.msu.edu (Postfix) with ESMTP id 20BB54162C for ; Sat, 15 Feb 2014 23:19:04 -0500 (EST) X-Virus-Scanned: amavisd-new at egr.msu.edu Received: from mail.egr.msu.edu ([127.0.0.1]) by dauterive (dauterive.egr.msu.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jtsytJU4Qvr3 for ; Sat, 15 Feb 2014 23:19:04 -0500 (EST) Received: from EGR authenticated sender Message-ID: <53003C36.9010900@egr.msu.edu> Date: Sat, 15 Feb 2014 23:19:02 -0500 From: Adam McDougall User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: freebsd-ports@freebsd.org Subject: Re: Why would a port use its own existence as an excuse to fail install? References: <20140216033119.GR22007@albert.catwhisker.org> In-Reply-To: <20140216033119.GR22007@albert.catwhisker.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Feb 2014 04:28:28 -0000 On 02/15/2014 22:31, David Wolfskill wrote: > Silly me -- I thought today might be a good day to upgrade X.org on my > laptop to the NEW_XORG. > > Laptop is running: > > FreeBSD g1-251.catwhisker.org 9.2-STABLE FreeBSD 9.2-STABLE #670 r261880M/261884:902506: Fri Feb 14 04:50:27 PST 2014 root@g1-251.catwhisker.org:/usr/obj/usr/src/sys/CANARY i386 > > I would have updated it this morning, but there were to updates to > stable/9 as of r261913 (which is the current state of my local > private mirror). > > Ports is at r344370; I've been using pkgng on the machine for about > a week (though I still build ports, usually using portmaster. > > > Here's an example of the Subject.... > > One of the ports to be updated (based on the process documented in > ports/UPDATING 20131216) was textproc/clucene-qt4. > > So (cut/paste from typescript): > > ===>>> textproc/clucene-qt4 3/5 > 0;portmaster: textproc/clucene-qt4 3/5^G > ===>>> Port directory: /usr/ports/textproc/clucene-qt4 > > ===>>> Starting check for build dependencies > ===>>> Gathering dependency list for textproc/clucene-qt4 from ports > ===>>> Dependency check complete for textproc/clucene-qt4 > > ===>>> textproc/clucene-qt4 3/5 > 0;portmaster: textproc/clucene-qt4 3/5^G > ===> Cleaning for qt4-clucene-4.8.5 > ===> License LGPL21 accepted by the user > ===> qt4-clucene-4.8.5 depends on file: /usr/local/sbin/pkg - found > ===> Fetching all distfiles required by qt4-clucene-4.8.5 for building > ===> Extracting for qt4-clucene-4.8.5 > ===> Patching for qt4-clucene-4.8.5 > ===> Applying extra patch /common/ports/devel/qt4/files/extrapatch-configure > ===> Applying FreeBSD patches for qt4-clucene-4.8.5 > ===> qt4-clucene-4.8.5 depends on file: /usr/local/lib/qt4/libQtCore.so - found > ===> qt4-clucene-4.8.5 depends on file: /usr/local/bin/qmake-qt4 - found > ===> Configuring for qt4-clucene-4.8.5 > /bin/mkdir -p /common/ports/textproc/clucene-qt4/work/qt-everywhere-opensource-src-4.8.5/mkspecs > /bin/ln -sf /usr/local/bin/qmake-qt4 /common/ports/textproc/clucene-qt4/work/qt-everywhere-opensource-src-4.8.5/bin/qmake > > This is the Open Source Edition. > ... > > Build type: /common/local/share/qt4/mkspecs/freebsd-g++ > Architecture: i386 > ... > Finding project files. Please wait... > WARNING: /common/ports/textproc/clucene-qt4/work/qt-everywhere-opensource-src-4.8.5/projects.pro:46: Unable to find file for inclusion doc/doc.pri > Reading /common/ports/textproc/clucene-qt4/work/qt-everywhere-opensource-src-4.8.5/assistant > ... > ===>>> Starting check for runtime dependencies > ===>>> Gathering dependency list for textproc/clucene-qt4 from ports > ===>>> Dependency check complete for textproc/clucene-qt4 > > ===>>> textproc/clucene-qt4 3/5 > 0;portmaster: textproc/clucene-qt4 3/5^G > ===> Staging for qt4-clucene-4.8.5 > ===> Generating temporary packing list > install -m 755 -p "../../../../lib/libQtCLucene.so.4.8.5" "/common/ports/textproc/clucene-qt4/work/stage/usr/local/lib/qt4/libQtCLucene.so.4.8.5" > ... > sed -e "s,/common/ports/textproc/clucene-qt4/work/qt-everywhere-opensource-src-4.8.5/include,/usr/local/include/qt4,g" -e "s,/common/ports/textproc/clucene-qt4/work/qt-everywhere-opensource-src-4.8.5/lib,/usr/local/lib/qt4,g" -e "s,/common/ports/textproc/clucene-qt4/work/qt-everywhere-opensource-src-4.8.5,/usr/local,g" "../../../../lib/pkgconfig/QtCLucene.pc" >"/common/ports/textproc/clucene-qt4/work/stage/usr/local/libdata/pkgconfig/QtCLucene.pc" > ====> Compressing man pages (compress-man) > ===> Installing ldconfig configuration file > ===> Installing for qt4-clucene-4.8.5 > ===> Registering installation for qt4-clucene-4.8.5 > Installing qt4-clucene-4.8.5...pkg-static: qt4-clucene-4.8.5 conflicts with qt4-clucene-4.8.5 (installs files into the same place). Problematic file: /usr/local/lib/qt4/libQtCLucene.la > *** [fake-pkg] Error code 70 > > Stop in /common/ports/textproc/clucene-qt4. > > ===>>> Installation of qt4-clucene-4.8.5 (textproc/clucene-qt4) failed > ===>>> Aborting update > > ===>>> Update for textproc/clucene-qt4 failed > ===>>> Aborting update > > ===>>> Killing background jobs > Terminated > > > So that "Installing qt4-clucene-4.8.5...pkg-static: qt4-clucene-4.8.5 > conflicts with qt4-clucene-4.8.5 (installs files into the same > place). Problematic file: /usr/local/lib/qt4/libQtCLucene.la" is what > I was going on about. That really seems like about the lamest excuse > for failing an install that I could imagine.... > > Eventually, it will probably become moot, as I'll (eventually) > migrate to stable/10, and go through the deinstall-all-ports, then > reinstall-all-ports exercise.... but, seriously...? What's causing this? > > How do I make it stop? > > Peace, > david > I know you mentioned UPDATING 20131216, but I suspect you are tripping over the 20140107 entry. The quick pkg set commands will probably solve this. Sometimes it is hard to determine the right combination of actions to take from UPDATING if some time has passed; most entries are written assuming your installed ports match the ports tree by that date.