Opened 12 years ago

Closed 12 years ago

#32439 closed defect (fixed)

BrowserLauncher2: checksum mismatch

Reported by: ryandesign (Ryan Carsten Schmidt) Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 2.0.3
Keywords: Cc: singingwolfboy@…
Port: BrowserLauncher2

Description

$ sudo port install BrowserLauncher2
--->  Computing dependencies for BrowserLauncher2
--->  Fetching archive for BrowserLauncher2
--->  Attempting to fetch BrowserLauncher2-1.3_0+universal.darwin_10.i386-x86_64.tbz2 from http://packages.macports.org/BrowserLauncher2
--->  Fetching BrowserLauncher2
--->  Attempting to fetch BrowserLauncher2.tar.gz from http://browserlaunch2.cvs.sourceforge.net/viewvc/browserlaunch2/BrowserLauncher2/?view=tar&revision=1.3&x
--->  Verifying checksum(s) for BrowserLauncher2
Error: Checksum (rmd160) mismatch for BrowserLauncher2.tar.gz
Error: Checksum (sha256) mismatch for BrowserLauncher2.tar.gz
Error: Target org.macports.checksum returned: Unable to verify file checksums
Log for BrowserLauncher2 is at: /opt/local/var/macports/logs/_Users_rschmidt_macports_dports_java_BrowserLauncher2/BrowserLauncher2/main.log
Error: Status 1 encountered during processing.
To report a bug, see <http://guide.macports.org/#project.tickets>

By the look of the URL, it's an automatically-generated file, that they might cache for a time, but then throw away, and regenerate later, which will have a different checksum. So a URL like that is unsuitable for a port's master_sites location. It's also an unversioned distfile, which should be avoided.

Change History (1)

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

Resolution: fixed
Status: newclosed

Technically fixed in r87838 by switching to cvs fetching, with all the drawbacks that entails. Is there actually any reason to build this from source though, given that it's just a couple of .jar files?

Note: See TracTickets for help on using tickets.