Dear maintainer:

During a rebuild of all packages in unstable, this package failed to build.

Below you will find the last part of the build log (probably the most
relevant part, but not necessarily). If required, the full build log
is available here:

https://people.debian.org/~sanvila/build-logs/202609/

About the archive rebuild: The build was made on virtual machines from AWS,
using sbuild and a reduced chroot with only build-essential packages.

If you cannot reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and add an affects on src:python-proton-vpn-local-agent, so that this is still
visible in the BTS web page for this package.

Thanks.
--------------------------------------------------------------------------------
[...]
/usr/share/cargo/bin/cargo build --manifest-path python-proton-vpn-local-agent/Cargo.toml --offline --release
debian cargo wrapper: options = ['parallel=2'], profiles = [], parallel = ['-j2'], lto =
debian cargo wrapper: rust_type = x86_64-unknown-linux-gnu, gnu_type = x86_64-linux-gnu
debian cargo wrapper: unsetting RUSTFLAGS for rust-lang/cargo#6338; add them to .cargo/config.toml
debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1', '/usr/bin/cargo', '-Zavoid-dev-deps', 'build', '--verbose', '--verbose', '-j2', '--target', 'x86_64-unknown-linux-gnu', '--manifest-path', 'python-proton-vpn-local-agent/Cargo.toml', '--offline', '--release'],) {}
error: failed to select a version for the requirement `bincode = "^1.3.3"`
candidate versions found which didn't match: 2.0.1
location searched: directory source `/<<PKGBUILDDIR>>/debian/cargo_registry` (which is replacing registry `crates-io`)
required by package `local-agent-rs v0.10.1 (/<<PKGBUILDDIR>>/local_agent_rs)`
     ... which satisfies path dependency `local-agent-rs` of package `python-proton-vpn-local-agent v1.6.3 (/<<PKGBUILDDIR>>/python-proton-vpn-local-agent)`
perhaps a crate was updated and forgotten to be re-vendored?
As a reminder, you're using offline mode (--offline) which can sometimes cause surprising resolution failures, if this error is too confusing you may wish to retry without `--offline`.
make[1]: *** [debian/rules:33: override_dh_auto_build] Error 101
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:21: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess failed with exit status 2
--------------------------------------------------------------------------------