[MacPorts] #47765: Scapy @ 2.3.1 Upgrade from existing 2.2.0 version
#47765: Scapy @ 2.3.1 Upgrade from existing 2.2.0 version -----------------------+-------------------------------- Reporter: msavory@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: haspatch | Port: scapy -----------------------+-------------------------------- Scary development has moved to BitBucket and new releases are zip not tar.gz, updating checksums and live check. -- Ticket URL: <https://trac.macports.org/ticket/47765> MacPorts <https://www.macports.org/> Ports system for OS X
#47765: Scapy @ 2.3.1 Upgrade from existing 2.2.0 version ------------------------+-------------------------------- Reporter: msavory@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: haspatch Port: scapy | ------------------------+-------------------------------- Old description:
Scary development has moved to BitBucket and new releases are zip not tar.gz, updating checksums and live check.
New description: Scapy development has moved to BitBucket and new releases are zip not tar.gz, updating checksums and live check. -- Comment (by ryandesign@…): Using `livecheck.md5` isn't really optimal because at best it tells you that a different version is available, but it does not tell you what version. The livecheck currently in the port is better in that regard. -- Ticket URL: <https://trac.macports.org/ticket/47765#comment:1> MacPorts <https://www.macports.org/> Ports system for OS X
#47765: Scapy @ 2.3.1 Upgrade from existing 2.2.0 version ------------------------+-------------------------------- Reporter: msavory@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: haspatch Port: scapy | ------------------------+-------------------------------- Comment (by msavory@…): Hi Ryan, Yes I agree live check.md5 is not optimal, it just tells you when an existing download fails to match... There used to be a "Latest release" link on the homepage http://www.secdev.org/projects/scapy/ but that doesn't exist any more. Is there a way of asking bitbucket what the latest tag is? A better solution would be to get the URL regex check to work on the http://scapy.net/ and not follow the redirect link, but I couldn't get this to work. {{{ curl http://scapy.net/ <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>302 Found</title> </head><body> <h1>Found</h1> <p>The document has moved <a href="http://www.secdev.org/projects/scapy/files/scapy-2.3.1.zip">here</a>.</p> </body></html> }}} -- Ticket URL: <https://trac.macports.org/ticket/47765#comment:2> MacPorts <https://www.macports.org/> Ports system for OS X
#47765: Scapy @ 2.3.1 Upgrade from existing 2.2.0 version ------------------------+-------------------------------- Reporter: msavory@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: | Keywords: haspatch Port: scapy | ------------------------+-------------------------------- Comment (by msavory@…): If a newer file was added to http://www.secdev.org/projects/scapy/files/ I don't believe the existing live check would show that there had been an update. -- Ticket URL: <https://trac.macports.org/ticket/47765#comment:3> MacPorts <https://www.macports.org/> Ports system for OS X
#47765: Scapy @ 2.3.1 Upgrade from existing 2.2.0 version ------------------------+-------------------------------- Reporter: msavory@… | Owner: macports-tickets@… Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Resolution: fixed | Keywords: haspatch Port: scapy | ------------------------+-------------------------------- Changes (by khindenburg@…): * status: new => closed * resolution: => fixed Comment: done - r137541 -- Ticket URL: <https://trac.macports.org/ticket/47765#comment:5> MacPorts <https://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts