From owner-freebsd-ports@FreeBSD.ORG Wed Jun 4 11:07:37 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 A9EA1A2E; Wed, 4 Jun 2014 11:07:37 +0000 (UTC) Received: from fep17.mx.upcmail.net (fep17.mx.upcmail.net [62.179.121.37]) by mx1.freebsd.org (Postfix) with ESMTP id C29692429; Wed, 4 Jun 2014 11:07:36 +0000 (UTC) Received: from edge04.upcmail.net ([192.168.13.239]) by viefep17-int.chello.at (InterMail vM.8.01.05.05 201-2260-151-110-20120111) with ESMTP id <20140604110734.DCOZ4787.viefep17-int.chello.at@edge04.upcmail.net>; Wed, 4 Jun 2014 13:07:34 +0200 Received: from crashalot.kantoor.acservices.nl ([213.127.215.2]) by edge04.upcmail.net with edge id AB7Z1o02G03gjjH03B7au2; Wed, 04 Jun 2014 13:07:34 +0200 X-SourceIP: 213.127.215.2 Message-ID: <1401880051.79205.0.camel@crashalot.rainbow-runner.nl> Subject: Re: unable to install "devel/py27-dbus" From: Koop Mast To: FreeBSD Ports Date: Wed, 04 Jun 2014 13:07:31 +0200 In-Reply-To: <20140604064251.4f16a3a3@scorpio> References: <20140604064251.4f16a3a3@scorpio> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.12.2 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Cc: gnome@FreeBSD.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jun 2014 11:07:37 -0000 On wo, 2014-06-04 at 06:42 -0400, Jerry wrote: > FreeBSD 10.0-RELEASE-p3 amd64 > > I am unable to update the "devel/py-dbus" port. > > The build end with this error message: Please read ports/UPDATING entry 20140525 to resolve this problem. > ===> Staging for pydbus-common-1.1.1_4 > ===> Generating temporary packing list > /bin/mkdir -p /usr/ports/devel/pydbus-common/work/stage/usr/local/include/dbus-1.0/dbus/ > install -o root -g wheel -m 444 /usr/ports/devel/pydbus-common/work/dbus-python-1.1.1/include/dbus-python.h /usr/ports/devel/pydbus-common/work/stage/usr/local/include/dbus-1.0/dbus/dbus-python.h > install -o root -g wheel -m 444 /usr/ports/devel/pydbus-common/work/dbus-python-1.1.1/dbus-python.pc /usr/ports/devel/pydbus-common/work/stage/usr/local/libdata/pkgconfig/dbus-python.pc > /bin/mkdir -p /usr/ports/devel/pydbus-common/work/stage/usr/local/share/examples/py-dbus && install -o root -g wheel -m 444 /usr/ports/devel/pydbus-common/work/dbus-python-1.1.1/examples/*.py /usr/ports/devel/pydbus-common/work/stage/usr/local/share/examples/py-dbus > /bin/mkdir -p /usr/ports/devel/pydbus-common/work/stage/usr/local/share/doc/py-dbus && install -o root -g wheel -m 444 /usr/ports/devel/pydbus-common/work/dbus-python-1.1.1/doc/*.txt /usr/ports/devel/pydbus-common/work/stage/usr/local/share/doc/py-dbus && install -o root -g wheel -m 444 /usr/ports/devel/pydbus-common/work/dbus-python-1.1.1/README /usr/ports/devel/pydbus-common/work/stage/usr/local/share/doc/py-dbus && install -o root -g wheel -m 444 /usr/ports/devel/pydbus-common/work/dbus-python-1.1.1/NEWS /usr/ports/devel/pydbus-common/work/stage/usr/local/share/doc/py-dbus > ====> Compressing man pages (compress-man) > ====> Running Q/A tests (stage-qa) > ===> Installing for pydbus-common-1.1.1_4 > ===> Checking if devel/pydbus-common already installed > ===> Registering installation for pydbus-common-1.1.1_4 as automatic > Installing pydbus-common-1.1.1_4...pkg-static: pydbus-common-1.1.1_4 conflicts with py27-dbus-1.1.1 (installs files into the same place). Problematic file: /usr/local/include/dbus-1.0/dbus/dbus-python.h > *** Error code 70 > > Stop. > make[1]: stopped in /usr/ports/devel/pydbus-common > *** Error code 1 > > Stop. > make: stopped in /usr/ports/devel/py-dbus > > The entire build log is available here: > http://www.seibercom.net/logs/py27-dbus.txt > > There is nothing in "UPDATING" at least that I can find that deals with this. > Should I delete the problematic file manually? "Portupgrade" doesn't touch it. >