www/uzbl: Update checksum

[joneum]

Summary

• Upstream rerolled the distfiles

PR: 219824
Reported by: xmj
Approved by: Klaus Aehlig (maintainer) xxx (mentor)
#Differential Revision: https://reviews.freebsd.org/Dxxxxx

Test Plan

:~/dev/ports/www/uzbl % portlint -AC
WARN: Makefile: Consider adding support for a NLS knob to conditionally disable gettext support.
WARN: Makefile: for new port, make $FreeBSD$ tag in comment section empty, to make SVN happy.
WARN: Makefile: new ports should not set PORTREVISION.
WARN: /usr/home/joneum/dev/ports/www/uzbl/files/patch-examplesdatascriptsinstance-select-wii.sh: patch was not generated using `make makepatch''. It is recommended to use `make makepatch'' when you need to [re-]generate a patch to ensure proper patch format.
WARN: /usr/home/joneum/dev/ports/www/uzbl/files/patch-examplesdatascriptsload_url_from_history.sh: patch was not generated using `make makepatch''. It is recommended to use `make makepatch'' when you need to [re-]generate a patch to ensure proper patch format.
0 fatal errors and 5 warnings found.

poudriere testport:

10amd64
10i386
11amd64
11i386
12.0-CURRENT r318899 amd64
12.0-CURRENT r318400 i386

[miwi]

Please explain what upstream have change, thats quiet imported to explain why it was rerolled.

[joneum]

In D11214#232543, @miwi wrote:

Please explain what upstream have change, thats quiet imported to explain why it was rerolled.

Hi miwi, see the PR:

The difference between the old and the new tar ball is literally one additional hex digit in the embedded git version. In other words

$ diff -ruN old new
diff -ruN old/uzbl-0.9.1/misc/hash.sh new/uzbl-0.9.1/misc/hash.sh

• old/uzbl-0.9.1/misc/hash.sh 2016-10-27 09:57:35.000000000 +0200

+++ new/uzbl-0.9.1/misc/hash.sh 2016-10-27 09:57:35.000000000 +0200
@@ -15,7 +15,7 @@

if [ -n "$tarball_tag" ]; then
    echo "$tarball_tag"
else

• echo '981a45e'

+ echo '981a45e8'

fi

else

echo >&2 "Commit hash detection fail. Dear packager, please figure out what goes wrong or get in touch with us"

$

Such rerolls happen whenever github decides to change how long a prefix of a git hash is a good version name for a commit. Because the actual upstream source, https://github.com/uzbl/uzbl/blob/981a45e848c779a3f7b49ce157e3f6df2f561099/misc/hash.sh, of course, only contains a place holder for the hash at that place that automatically gets replaced when github constructs the tarball for a given release commit.

And the keyword-expansion scheme has changed (let's take 8 instead of 7 hex digits to name a git commit), hence all tarballs containing this keyword expansion have changed. But it certainly is not a functional change of the resulting package.

[miwi]

Please make a notes in the commit log about that.