blake3-deb

Fork

update depending crate + release

add dependency on new lib

rm

patches

* delete patches related to '--check' option
* patch refresh

gbp.conf: sign-tags

changelog: new upstream

Update upstream source from tag 'upstream/0.3.4'

Update to upstream version '0.3.4'
with Debian dir 240c93896830021d21ccc4d9ad9ead1c629cd761

pristine-tar data for blake3_0.3.4.orig.tar.gz

New upstream version 0.3.4

version 0.3.4

Changes since 0.3.3:
- `b3sum` now supports the `--check` flag. This is intended to be a
drop-in replacement for e.g. `md5sum --check` from Coreutils. The
behavior is somewhat stricter than Coreutils with respect to invalid
Unicode in filenames. For a complete description of how `--check`
works, see the file `b3sum/what_does_check_do.md`.
- To support the `--check` feature, backslashes and newlines that appear
in filenames are now escaped in the output of `b3sum`. This is done
the same way as in Coreutils.
- To support `--check` interoperability between Unix and Windows,
backslashes in filepaths on Windows are now replaced with forward
slashes in the output of `b3sum`. Note that this is different from
Coreutils.

remove an extra space in some help text

use wild::args_os to support globbing on Windows

add support for --quiet to `b3sum --check`

Suggested by @llowrey:
https://github.com/BLAKE3-team/BLAKE3/issues/33#issuecomment-629853747

some more clarifications in the --check docs

clarify the replacement character example

small typo

finish the --check documentation

link to the test vectors from the README

start documenting the --check flag

enable clap default features

These are nice to have. I used to think this would increase build times,
but in practice it doesn't.

clarify that --no-mmap disables threading

print per-file errros more gracefuly in --check

print more compiler version info in CI

refactor b3sum to support --check

This is an overall cleanup of everything that b3sum is doing, especially
file opening and memory mapping, which makes it easier for the regular
hashing mode to share code with the checking mode.

switch from assert_cmd to CARGO_BIN_EXE_*

add parse_check_line

As part of this, reorganize b3sum tests into src/unit_tests.rs and
tests/cli_tests.rs.

stop printing the lossy warning

Rather than breaking the check parse with more output, we'll have a rule
that a Unicode replacement character (�) in a path name automatically
fails the check.

add newline and backslash escaping to b3sum output

As proposed in
https://github.com/BLAKE3-team/BLAKE3/issues/33#issuecomment-623153164

This brings b3sum behavior close to md5sum. All occurrences of backslash
are replaced with "\\", and all occurrences of (Unix) newline are
replaced with "\n". In addition, any line containing these escapes has a
single "\" prepended to the front.

Filepaths were already being converted to UTF-8 with to_string_lossy(),
but this commit adds an extra warning when that conversion is in fact
lossy (because the path is not valid Unicode). This new warning is
printed to stdout, with the goal of deliberately breaking --check (which
is not yet implemented) in this case.

lower our required version of `cc`

I've tested manually and found that 1.0.4 is the oldest version of `cc`
that builds successfully for us. (Version 1.0.3 is missing the
`is_flag_supported` method.)

This change might help with
https://github.com/BLAKE3-team/BLAKE3/issues/83. That said, the
underlying issue there is related to "minimum supported Rust versions",
and `blake3` does not yet have an MSRV other than latest stable.

version 0.3.3

Changes since 0.3.2:
- `b3sum` binaries are built in CI and attached to new GitHub tags.