The file was changed in upstream.
File pkg/box2d-2.3.1.tar.gz
(or https://github.com/erincatto/Box2D/archive/v2.3.1.tar.gz):
Old sha256: 2c61505f03ef403b54cf0e510d83d6f567e37882ad79b5b2d486acbc7d5eedea
New sha256: 75d62738b13d2836cd56647581b6e574d4005a6e077ddefa5d727d445d649752
Changes:
$ diff -r old/ new
Only in old/Box2D-2.3.1/Contributions/Platforms: Box2D.XNA.zip
Only in old/Box2D-2.3.1/Contributions/Platforms: Tizen.zip
Files Box2D.XNA.zip and Tizen.zip are not used in build, according to logs.
Removing them them seems to be safe.
fix#1319
From the warning produced by "git add ." after removing a file with "rm":
> warning: You ran 'git add' with neither '-A (--all)' or '--ignore-removal',
> whose behaviour will change in Git 2.0 with respect to paths you removed.
> Paths like 'foo.txt' that are
> removed from your working tree are ignored with this version of Git.
>
> * 'git add --ignore-removal <pathspec>', which is the current default,
> ignores paths you removed from your working tree.
>
> * 'git add --all <pathspec>' will let you also record the removals.
>
> Run 'git status' to check the paths you removed from your working tree.
$ git status --porcelain
D foo.txt
$ git add --all .
$ git status --porcelain
D foo.txt
$ git --version
git version 1.9.1
The second pass is done after the first one. During the second pass,
an item is built in tree of files from all other items. It checks that:
* packages can be built in any order satisfying dependencies;
* a package can be rebuilt after its dependee.
For both cases, not only build status is checked but also two sets of
files are compared. Currently content of files is not checked, only
their existance in both passes.
See #1111