New Ticket     Tickets     Wiki     Browse Source     Timeline     Roadmap     Ticket Reports     Search

Ticket #20107 (closed defect: invalid)

Opened 4 years ago

Last modified 4 years ago

Target for graphviz-devel no longer exists

Reported by: adam@… Owned by: ryandesign@…
Priority: Normal Milestone:
Component: ports Version: 1.6.0
Keywords: Cc:
Port: graphviz-devel

Description (last modified by macsforever2000@…) (diff)

The target for graphviz-devel had been deleted on the target server:

[adam@tester]$ sudo /opt/local/bin/port install graphviz-devel
--->  Fetching graphviz-devel
--->  Attempting to fetch graphviz-2.21.20081012.0445.tar.gz from http://www.graphviz.org/pub/graphviz/development/SOURCES/
Error: Target org.macports.fetch returned: fetch failed
Error: Status 1 encountered during processing.

The latest stable copy should be fetched - graphviz-working.tar.gz

Change History

comment:1 Changed 4 years ago by macsforever2000@…

  • Owner changed from macports-tickets@… to ryandesign@…
  • Description modified (diff)

You are way out of date. Run the following:

sudo port selfupdate
sudo port upgrade outdated
sudo port install graphviz-devel 

comment:2 in reply to: ↑ description Changed 4 years ago by ryandesign@…

  • Status changed from new to closed
  • Resolution set to invalid

Replying to adam@…:

The latest stable copy should be fetched - graphviz-working.tar.gz

Actually ports should not use a "latest" tarball, and should instead always use a versioned or dated tarball, as graphviz-devel does. Otherwise there would be no certainty that the tarball you got when you installed the port was the same one I got when I made the portfile. And we want that certainty, so much so that each portfile has checksums of the distfile so that if you get a different file, you get a checksum mismatch error and cannot proceed.

The Graphviz developers release a new development snapshot daily. I update the graphviz-devel port about weekly. To get these and all other updates, you do need to periodically run "sudo port selfupdate" or "sudo port sync" as Frank showed. Then you can use "port outdated" to see what's outdated, and "sudo port upgrade" to upgrade any or all of those ports.

Note: See TracTickets for help on using tickets.