Opened 7 years ago
Closed 7 years ago
#55821 closed defect (fixed)
jpeg @9c different checksum
Reported by: | maverickwoo (Maverick Woo) | Owned by: | ryandesign (Ryan Carsten Schmidt) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | ||
Port: | jpeg |
Description
The checksum in the port file appears to be different from the current download.
:info:checksum The correct checksum line may be: :info:checksum checksums rmd160 d097f5c4dbfe09d61b688fc1e20ea37e73e78a3f \ :info:checksum sha256 1f3a3f610f57e88ff3f1f9db530c605f3949ee6e78002552e324d493cf086ad4 \ :info:checksum size 1028200 :error:checksum Failed to checksum jpeg: Unable to verify file checksums
Attachments (1)
Change History (4)
Changed 7 years ago by maverickwoo (Maverick Woo)
comment:1 Changed 7 years ago by mf2k (Frank Schima)
Owner: | set to ryandesign |
---|---|
Status: | new → assigned |
comment:2 Changed 7 years ago by ryandesign (Ryan Carsten Schmidt)
Status: | assigned → accepted |
---|
Yes there does appear to have been a stealth update of jpegsrc.v9c.tar.gz. The only difference between the old and new files is that 2 references to jpeg 9b in the readme were changed to 9c:
$ diff -ru 0/jpeg-9c 1/jpeg-9c diff -ru 0/jpeg-9c/README 1/jpeg-9c/README --- 0/jpeg-9c/README 2018-01-14 03:06:18.000000000 -0600 +++ 1/jpeg-9c/README 2018-01-26 03:06:16.000000000 -0600 @@ -246,8 +246,8 @@ The "official" archive site for this software is www.ijg.org. The most recent released version can always be found there in directory "files". This particular version will be archived as -http://www.ijg.org/files/jpegsrc.v9b.tar.gz, and in Windows-compatible -"zip" archive format as http://www.ijg.org/files/jpegsr9b.zip. +http://www.ijg.org/files/jpegsrc.v9c.tar.gz, and in Windows-compatible +"zip" archive format as http://www.ijg.org/files/jpegsr9c.zip. The JPEG FAQ (Frequently Asked Questions) article is a source of some general information about JPEG.
I won't make everyone rebuild the port for such an inconsequential change, so I'll just tell the port to ignore the new upstream file. If you wait an hour, then sudo port clean --all jpeg
and sudo port selfupdate
, you should receive the fix and then be able to install the port.
comment:3 Changed 7 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → fixed |
---|---|
Status: | accepted → closed |
Note: See
TracTickets for help on using
tickets.
In the future, please Cc the port maintainers (
port info --maintainers jpeg
), if any.