ifeffit - checksum org.macports.checksum for port ifeffit returned: Unable to verify file checksums

[laestudillowong]

I try to update my Macports but it returns some problems with ifeffit:

:info:checksum The correct checksum line may be:
:info:checksum checksums           rmd160  7b09aa5722a4aa638364c35e15d64b857cdb822b \
                    sha256  79fa938643a1417c5b01be4b6196bd0ea6bf40685448ba98546c7989b0f48a48
:error:checksum org.macports.checksum for port ifeffit returned: Unable to verify file checksums
:debug:checksum Error code: NONE
:debug:checksum Backtrace: Unable to verify file checksums
    while executing
"portchecksum::checksum_main org.macports.checksum"
    ("eval" body line 1)
    invoked from within
"eval $procedure $targetname"
:info:checksum Warning: targets not executed for ifeffit: org.macports.install org.macports.checksum org.macports.extract org.macports.patch org.macports.configure org.macports.build org.macports.destroot
:notice:checksum Please see the log file for port ifeffit for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_science_ifeffit/ifeffit/main.log

[laestudillowong]

main.log

[mf2k (Frank Schima)]

In the future, please use WikiFormatting and Cc the port maintainers (port info --maintainers ifeffit), if any.

main.log has the mirror downloaded.

[ryandesign (Ryan Carsten Schmidt)]

r138658 changed the file which the port fetches, without making the necessary corresponding change to the checksums.

[ryandesign (Ryan Carsten Schmidt)]

There was no need to make this change, since the contents of the files are substantially identical (the only difference is the name of the directory they extract to), but since the change was made, we need to fix it so it works correctly. We may as well at the same time fix the usage of the github portgroup. See attached patch.

[ryandesign (Ryan Carsten Schmidt)]

proposed patch

[joefowler (Joe Fowler)]

The proposed patch makes sense and works for me. Thanks to everyone for reporting and figuring out a fix.

Unfortunately, I am not a committer at MacPorts, so someone else will have to commit this.

[dbevans (David B. Evans)]

Replying to ryandesign@…:

There was no need to make this change, since the contents of the files are substantially identical (the only difference is the name of the directory they extract to), but since the change was made, we need to fix it so it works correctly. We may as well at the same time fix the usage of the github portgroup. See attached patch.

For the record, libpng's pkg-config file specifies -lpng16. Both libpng and libpng16 are provided so either will work but most packages (those that use pkgconfig) will use -lpng16.

$ pkg-config --libs libpng
-L/opt/local/lib -lpng16

Tested successfully and committed as proposed in r139316. Sorry for overlooking the checksum changes in the previous commit. Mea culpa. However, I'm still a bit confused about the rationale concerning the necessity for the rest of the changes in this commit.

[ryandesign (Ryan Carsten Schmidt)]

The rationale for changing -lpng16 to -lpng is compatibility with future versions of libpng. When, at some point in the future, libpng 1.7 or later is released, its library will, if the previous pattern holds, be named libpng17.dylib, and -lpng16 will no longer work, whereas -lpng works today and will continue to work in the future (because libpng also provides a libpng.dylib symlink pointing to whatever the current library name is). Most other projects handle their libraries in a similar way.