From owner-freebsd-gnome@FreeBSD.ORG Mon Sep 29 20:22:25 2014 Return-Path: Delivered-To: gnome@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E8899DFD for ; Mon, 29 Sep 2014 20:22:25 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B7BEF157 for ; Mon, 29 Sep 2014 20:22:25 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s8TKMPNf075076 for ; Mon, 29 Sep 2014 20:22:25 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: gnome@FreeBSD.org Subject: [Bug 194020] archivers/engrampa port broken by py-gobject Date: Mon, 29 Sep 2014 20:22:25 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports Tree X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: dcbdbis@comcast.net X-Bugzilla-Status: In Discussion X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: gnome@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Sep 2014 20:22:26 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194020 --- Comment #11 from Dave --- The definition of "bringing a system out of the ground"...well at least how I do it! a) Customer sends me a brand new PC in box. b) I go into the BIOS and update it with the installed Windows OS. (if applicable) c) I modify the BIOS to use legacy mode and turn off the EFI. d) I boot from the FreeBSD 10.0 Release AMD64 DVD and go into a shell first thing. From the cli I issue "gpart destroy -F /dev/ada0". Then I exit the shell. e) I install FreeBSD normally from the DVD and reboot. I do not install any users at this stage. f) From the cli I issue "freebsd-update fetch install" Followed by a reboot g) On the next boot I rebuild the world following Warren Blocks excellent article: http://www.wonkity.com/~wblock/docs/html/buildworld.html h) Once the rebuilding world process is completed, then I "portsnap fetch extract" i) Then from the cli I "cd /usr/ports/ports-mgmt/portmaster". Followed by "make clean install clean (I know...an extra clean in there..but humor me please) j) I then navigate back into root's home dir and: "portmaster x11/xorg" k) Followed by "portmaster x11/mate" This is where the bug rears it's head. I want to make sure you understand...in my forensics...I am finding differing naming conventions for "py-gobject" vs "py27-gobject" These port name issues span the website, the "pkg search" and the "whereis" utilities. I think the issue is not so much with your build....as it is with inconsistent package naming conventions for py-gobject. The mate port is calling for "py27-gobject"...which doesn't exist in fresh ports that are recently installed from scratch. Instead the package is installed in the ports tree as "py-gobject" If I manually "portmaster devel/py-gobject"...Then after building this one port...I can continue mate's build with "portmaster -R x11/mate"...and all builds, installs, and runs perfectly. Hope this helps! Thanks again. Sincerely and respectfully, Dave -- You are receiving this mail because: You are the assignee for the bug.