* rpcs3: 0.0.4-8032 -> 0.0.5-6884
* rpcs3: update hash
* rpcs3: 0.0.5-6884 -> 0.0.5-6925
* rpcs3: 0.0.5-6925 -> 0.0.5-6938
* rpcs3: 0.0.5-6938 -> 0.0.5-6980
Manually write version header instead of generating it with git, which required leaveDotGit to be enabled.
This caused some hash mismatches (see #8567) has thus been disabled.
This reverts commit 2624f9079617df6b1fffda8c10f6a7a35068ecdc, reversing
changes made to 37aab4cbb5552bf021b20cf05d64e8ded6f3538a.
See:
https://github.com/NixOS/nixpkgs/pull/42376#issuecomment-399789096
Basically this breaks at least some users of fetchgit,
so let's revert this until this is sorted out.
gopass tries to write a version number to it's configuaration, even when
just generating the shell completion scripts. This fails, as
/homeless-shelter is read-only inside the sandbox.
As error messages are printed to stdout instead of stderr
(see https://github.com/gopasspw/gopass/issues/877), the error message
lands inside the completion script, thus breaking it.
Workaround that by setting GOPASS_CONFIG to `/dev/null`
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/gdbm/versions.
These checks were done:
- built on NixOS
- /nix/store/gs61jjz7j3gii2zqm8f65qxpy4k9mybq-gdbm-1.15/bin/gdbmtool passed the binary check.
- /nix/store/gs61jjz7j3gii2zqm8f65qxpy4k9mybq-gdbm-1.15/bin/gdbm_load passed the binary check.
- /nix/store/gs61jjz7j3gii2zqm8f65qxpy4k9mybq-gdbm-1.15/bin/gdbm_dump passed the binary check.
- 3 of 3 passed binary check by having a zero exit code.
- 0 of 3 passed binary check by having the new version present in output.
- found 1.15 with grep in /nix/store/gs61jjz7j3gii2zqm8f65qxpy4k9mybq-gdbm-1.15
- directory tree listing: https://gist.github.com/6bd11a4334992f4b8f19331113c0daa3
- du listing: https://gist.github.com/14f6008edc7f1045329c1205500d1a1a
Both mariadb.com and mariadb.org appear to be canonical upstream sources, and
have identical sha256 hashes at these URLs.
For the third-party mirrors, if we are just going to provide one URL, it should
be an HTTPS url instead of FTP or SSH, which many users may not be able to
access due to network security configurations.
