Date: Mon, 29 Sep 2014 19:10:42 +0000 From: bugzilla-noreply@freebsd.org To: gnome@FreeBSD.org Subject: maintainer-feedback requested: [Bug 194020] archivers/engrampa port broken by py-gobject Message-ID: <bug-194020-6497-ACLWPtgVnG@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-194020-6497@https.bugs.freebsd.org/bugzilla/> References: <bug-194020-6497@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
Dave <dcbdbis@comcast.net> 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 <dcbdbis@comcast.net> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-194020-6497-ACLWPtgVnG>