Opened 2 years ago

Last modified 8 months ago

#65941 assigned defect

Dependency missing for upgrading to graphviz @6.0.1_1+gdk_pixbuf+java+pangocairo+perl+poppler+python27+tcl+x11

Reported by: Gandoon (Erik Hedlund) Owned by: ryandesign (Ryan Carsten Schmidt)
Priority: Normal Milestone:
Component: ports Version: 2.7.2
Keywords: Cc: mascguy (Christopher Nielsen)
Port: graphviz

Description

I spent some time trying to upgrade graphviz @2.50.0_0 to graphviz @6.0.1_1 as per the normal route.

However, I kept running into the same wall (see attached log if interest exist). I browsed through other tickets trying to find a potential solution. The closest I found was the closed #64323. It is not identical, but the effects were close enough that I started digging through the log with a different focus. I figured out that what seemed to trigger the failure was an: Error: Unable to find 'go.swg'

So, I checked whether swig-go port was installed, and it wasn't. So after building that port I tried again upgrading graphviz and it worked as expected and the build finished without errors.

So a simple solution for this would be to add swig-go as a dependency (I am unclear if this is applicable to all variants or just a subset).

Attachments (1)

GND20221006-main.log (1.6 MB) - added by Gandoon (Erik Hedlund) 2 years ago.
Upgrade of graphviz sans swig-go - failed build

Download all attachments as: .zip

Change History (3)

Changed 2 years ago by Gandoon (Erik Hedlund)

Attachment: GND20221006-main.log added

Upgrade of graphviz sans swig-go - failed build

comment:1 Changed 2 years ago by jmroot (Joshua Root)

Cc: mascguy added
Owner: set to ryandesign
Status: newassigned

comment:2 Changed 2 years ago by Gandoon (Erik Hedlund)

I did just find an earlier ticket with similar content: #64106 so maybe this guy is a duplicate after all…

And that tickets author, outis, did even provide a patch that could be used as a template for fixing this issue.

Last edited 8 months ago by ryandesign (Ryan Carsten Schmidt) (previous) (diff)
Note: See TracTickets for help on using tickets.