#39259 closed defect (fixed)
graphviz @2.30.1_0: pkg-config files refer to nonexistent libgraph
Reported by: | Michael.Wybrow@… | Owned by: | ryandesign (Ryan Carsten Schmidt) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.1.3 |
Keywords: | Cc: | cooljeanius (Eric Gallager), angelo.graziosi@… | |
Port: | graphviz |
Description
The installed pkg-config file for libgvc (/opt/local/lib/pkgconfig/libgvc.pc) contains "-lgraph" but there is no libgraph.dylib installed by graphviz-2.30.1_0.
Change History (7)
comment:1 Changed 11 years ago by larryv (Lawrence Velázquez)
Owner: | changed from macports-tickets@… to ryandesign@… |
---|---|
Summary: | graphviz @2.30.1_0 pkg-config files refer to no-existent libgraph → graphviz @2.30.1_0: pkg-config files refer to nonexistent libgraph |
comment:3 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
Status: | new → assigned |
---|
This was fixed upstream in February, so it's fixed in the graphviz-devel port, but there hasn't been a new stable release since then. I'll apply their patch.
comment:4 follow-up: 5 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
comment:5 Changed 11 years ago by angelo.graziosi@…
Replying to ryandesign@…:
I have upgraded a few minutes ago:
$ sudo port selfupdate Password: ---> Updating MacPorts base sources using rsync MacPorts base version 2.1.3 installed, MacPorts base version 2.1.3 downloaded. ---> Updating the ports tree ---> MacPorts base is already the latest version The ports tree has been updated. To upgrade your installed ports, you should run port upgrade outdated $ sudo port outdated The following installed ports are outdated: cctools 836_0 < 839_0 cctools-headers 836_1 < 839_0 glib2 2.36.2_0 < 2.36.2_1 graphviz 2.30.1_0 < 2.30.1_1 ld64 134.9_1 < 136_1 xorg-libXau 1.0.7_0 < 1.0.8_0 xorg-xproto 7.0.23_0 < 7.0.24_0
but graphviz upgrade produces versy strange "Warnings":
$ sudo port upgrade outdated [...] ---> Computing dependencies for graphviz ---> Fetching archive for graphviz ---> Attempting to fetch graphviz-2.30.1_1+pangocairo+ruby+x11.darwin_11.x86_64.tbz2 from http://lil.fr.packages.macports.org/graphviz ---> Attempting to fetch graphviz-2.30.1_1+pangocairo+ruby+x11.darwin_11.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/graphviz ---> Attempting to fetch graphviz-2.30.1_1+pangocairo+ruby+x11.darwin_11.x86_64.tbz2 from http://packages.macports.org/graphviz ---> Fetching distfiles for graphviz ---> Verifying checksum(s) for graphviz ---> Extracting graphviz ---> Applying patches to graphviz ---> Configuring graphviz ---> Building graphviz ---> Staging graphviz into destroot Warning: violation by /System Warning: graphviz violates the layout of the ports-filesystems! Warning: Please fix or indicate this misbehavior (if it is intended), it will be an error in future releases! ---> Installing graphviz @2.30.1_1+pangocairo+ruby+x11 ---> Cleaning graphviz ---> Computing dependencies for graphviz ---> Deactivating graphviz @2.30.1_0+pangocairo+ruby+x11 ---> Cleaning graphviz ---> Activating graphviz @2.30.1_1+pangocairo+ruby+x11 ---> Cleaning graphviz ---> Updating database of binaries: 100.0% ---> Scanning binaries for linking errors: 100.0% ---> No broken files found.
These
Warning: violation by /System Warning: graphviz violates the layout of the ports-filesystems! Warning: Please fix or indicate this misbehavior (if it is intended), it will be an error in future releases!
don't seem good to me...
What do they mean?
Do we need to worry?
Ciao, Angelo.
comment:6 follow-up: 7 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | angelo.graziosi@… added |
---|
That shouldn't happen, but it's a separate issue. I suspect something with the language bindings. Please file a new ticket.
comment:7 Changed 11 years ago by cooljeanius (Eric Gallager)
Replying to ryandesign@…:
That shouldn't happen, but it's a separate issue. I suspect something with the language bindings. Please file a new ticket.
That new ticket is #39265 for other's reference, btw
Thanks for the ticket. In the future, please Cc relevant port maintainers.