> But surely the correct md5sum to a download is a remote test, therefore the > slackbuild needs to be updated (no matter when the download changes, so does > the md5sum) - not trying to match the md5sum to what is the download is > wrong: if it changes, it's an update and slackbuild needs changes too.
Yeah, sure, but upstream didn't notify any of this -- they did it silently, as upstreams usually do. I noticed less than two weeks ago (when looking to see whether 4.3.1 was out). So I care about the md5sum more than upstream cares about the md5sum. But when there's also the probability of an imminent new release upstream, it becomes a question of timing, and avoiding (if possible) two updates in quick succession - especially when everyone is recovering from the 14.1 release. Anyway, thanks to Willy for zapping it with his fifteen terawatt md5sum zapper :-) -D. _______________________________________________ SlackBuilds-users mailing list [email protected] http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/
