bcprov: update tarball checksum of retagged release

Upstream retagged https://github.com/bcgit/bc-java/releases/tag/r1rv71 from
https://github.com/bcgit/bc-java/commit/1dcbde6d8761df7d88fc7432cb128533418adeca
to
https://github.com/bcgit/bc-java/commit/1349bb03cff0b0023ef3247690410441f33b05b0

The changes are harmless and do not affect the built package since they only
concern run_test.sh.

git-svn-id: file:///srv/repos/svn-community/svn@1191603 9fca08f4-af9d-4005-b8df-a31f2cc04f65

bcprov: use git-archive tarball instead of git sources

Neither the tag nor the corresponding commit are signed, so there is no real
point in using a full git checkout.

On the other hand using the source tarball from
https://www.bouncycastle.org/download/bcprov-jdk18on-171.tar.gz does not work
well because it does not contain any build system files, only the plain *.java
sources.

git-svn-id: file:///srv/repos/svn-community/svn@1177962 9fca08f4-af9d-4005-b8df-a31f2cc04f65

archrelease: copy trunk to community-any

git-svn-id: file:///srv/repos/svn-community/svn@1177921 9fca08f4-af9d-4005-b8df-a31f2cc04f65

upgpkg: bcprov 1.71-1: upstream release, build from source, change JAR location

According to the Java package guidelines JARs should be placed in
/usr/share/java/$pkgname/ instead of directly under /usr/share/java/.

git-svn-id: file:///srv/repos/svn-community/svn@1177920 9fca08f4-af9d-4005-b8df-a31f2cc04f65

archrelease: copy trunk to community-any

git-svn-id: file:///srv/repos/svn-community/svn@1065629 9fca08f4-af9d-4005-b8df-a31f2cc04f65

extra2community: Moving bcprov from extra to community

git-svn-id: file:///srv/repos/svn-community/svn@1065628 9fca08f4-af9d-4005-b8df-a31f2cc04f65