Date: Mon, 29 Sep 2014 20:22:25 +0000 From: bugzilla-noreply@freebsd.org To: gnome@FreeBSD.org Subject: [Bug 194020] archivers/engrampa port broken by py-gobject Message-ID: <bug-194020-6497-jlqxKXtDcp@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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194020 --- Comment #11 from Dave <dcbdbis@comcast.net> --- 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-194020-6497-jlqxKXtDcp>