[Bug 194020] New: archivers/engrampa port broken by py-gobject

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194020

            Bug ID: 194020
           Summary: archivers/engrampa port broken by py-gobject
           Product: Ports Tree
           Version: Latest
          Hardware: Any
                OS: Any
            Status: Needs Triage
          Severity: Affects Many People
          Priority: ---
         Component: Individual Port(s)
          Assignee: gnome at FreeBSD.org
          Reporter: dcbdbis at comcast.net
          Assignee: gnome at FreeBSD.org
             Flags: maintainer-feedback?(gnome at FreeBSD.org)

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

--- Comment #1 from Bugzilla Automation <bugzilla at FreeBSD.org> ---
Auto-assigned to maintainer gnome at FreeBSD.org

-- 
You are receiving this mail because:
You are the assignee for the bug.