From owner-freebsd-gnome@FreeBSD.ORG Mon Sep 29 19:10:42 2014 Return-Path: Delivered-To: gnome@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 17DDAE23 for ; Mon, 29 Sep 2014 19:10:42 +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 05215880 for ; Mon, 29 Sep 2014 19:10:42 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s8TJAf0U049342 for ; Mon, 29 Sep 2014 19:10:41 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: gnome@FreeBSD.org Subject: maintainer-feedback requested: [Bug 194020] archivers/engrampa port broken by py-gobject Date: Mon, 29 Sep 2014 19:10:42 +0000 X-Bugzilla-Type: request Message-ID: In-Reply-To: References: X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" 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 19:10:42 -0000 Dave has asked gnome@FreeBSD.org for maintainer-feedback: Bug 194020: archivers/engrampa port broken by py-gobject https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194020 ------- Additional Comments from Dave The engrampa port is broken, which by extension also breaks the mate meta port. The issue is a bad package name. And I have a solution. The build stops at "gobject-introspection". Specifically "py27-gobject-2.*...This package is in reality named "py-gobject"...sans the "27" prefix. Here is what is weird. "pkg search" shows up the very name of the package this port is calling for spelled with "py27-gobject". While "whereis py-gobject" fails stating that this port is not found. Yet in reality, once I cd into /usr/ports/devel....I see that "py-gobject" does indeed exist...just not under the name of "py27-gobject". If I manually build py-gobject first, then build engrampa...the build of engrampa proceeds flawlessly, then I can build the rest of Mate. So "pkg" shows it under the old name of "py27-gobject", but in reality it isn't there.....Seems like there may be a package naming problem between the ports, packages, and the build script for engrampa, or a combination of all of the above. Sincerely and respectfully, Dave