Your message dated Sat, 08 Dec 2018 22:01:50 +0000
with message-id <[email protected]>
and subject line Bug#910978: fixed in rust-yaml 0.3.0-2
has caused the Debian Bug report #910978,
regarding rust-yaml FTBFS on architectures where char is unsigned
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
910978: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910978
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: rust-yaml
Version: 0.3.0-1
Severity: important
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=rust-yaml&suite=sid

...
error[E0308]: mismatched types
  --> src/codecs.rs:16:43
   |
16 |             str::from_utf8(CStr::from_ptr(i8_str).to_bytes()).map(|s| 
s.to_string()).ok()
   |                                           ^^^^^^ expected u8, found i8
   |
   = note: expected type `*const u8`
              found type `*const i8`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0308`.
error: Could not compile `yaml`.

Caused by:
  process didn't exit successfully: `rustc --crate-name yaml src/lib.rs 
--crate-type lib --emit=dep-info,link -C debuginfo=2 -C 
metadata=b307be25685f0f02 -C extra-filename=-b307be25685f0f02 --out-dir 
/<<PKGBUILDDIR>>/target/aarch64-unknown-linux-gnu/debug/deps --target 
aarch64-unknown-linux-gnu -C 
incremental=/<<PKGBUILDDIR>>/target/aarch64-unknown-linux-gnu/debug/incremental 
-L dependency=/<<PKGBUILDDIR>>/target/aarch64-unknown-linux-gnu/debug/deps -L 
dependency=/<<PKGBUILDDIR>>/target/debug/deps --extern 
libc=/<<PKGBUILDDIR>>/target/aarch64-unknown-linux-gnu/debug/deps/liblibc-feeade22c917e78d.rlib
 --extern 
regex=/<<PKGBUILDDIR>>/target/aarch64-unknown-linux-gnu/debug/deps/libregex-a5768dd58bde0a88.rlib
 -C linker=aarch64-linux-gnu-gcc -C debuginfo=2 --cap-lints warn 
--remap-path-prefix /<<PKGBUILDDIR>>=/usr/share/cargo/registry/yaml-0.3.0 -C 
link-arg=-Wl,-z,relro` (exit code: 1)
dh_auto_test: cargo build --verbose --verbose -j3 --target 
aarch64-unknown-linux-gnu -Zavoid-dev-deps returned exit code 101
make: *** [debian/rules:3: build-arch] Error 101

--- End Message ---
--- Begin Message ---
Source: rust-yaml
Source-Version: 0.3.0-2

We believe that the bug you reported is fixed in the latest version of
rust-yaml, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Wolfgang Silbermayr <[email protected]> (supplier of updated rust-yaml 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Sat,  8 Dec 2018 21:36:21 CET
Source: rust-yaml
Binary: librust-yaml-dev
Architecture: amd64 source
Version: 0.3.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 
<[email protected]>
Changed-By: Wolfgang Silbermayr <[email protected]>
Description: 
 librust-yaml-dev - LibYAML binding for Rust - Rust source code
Closes: 910978
Changes:
 rust-yaml (0.3.0-2) unstable; urgency=medium
 .
   * Package yaml 0.3.0 from crates.io using debcargo 2.2.9
   * Patch for arch-dependent build failures (Closes: #910978)
Checksums-Sha256: 
 2591d42714cca01ccd3b44ea09235716ea4268a25f6f8ece5f870438fef5a579 20052 
librust-yaml-dev_0.3.0-2_amd64.deb
 a684918aa1f6256c8fc30f93e12d02eac54d760729219aa729f5976ba7ad8244 7095 
rust-yaml_0.3.0-2_amd64.buildinfo
 7ced9975573616bf7a7bc5fb7b335e198df06a7222e2321106b555df0324c2b8 2187 
rust-yaml_0.3.0-2.dsc
 8f3e836575769aa7afe82989d8e66e4a3aa501b2cdb34cf91fc3bbe2b46de80c 18788 
rust-yaml_0.3.0.orig.tar.gz
 8a83703b943f736fe358b89098bfd9d514e27a2dea370e6d6c0e2003e1ebcba2 3252 
rust-yaml_0.3.0-2.debian.tar.xz
Checksums-Sha1: 
 cb979d25b92d3009ec481f765a15bdd432d89e92 20052 
librust-yaml-dev_0.3.0-2_amd64.deb
 de8d8e20c500c67e0d707ef5c18025211cf716c0 7095 rust-yaml_0.3.0-2_amd64.buildinfo
 9bea03af95d29ede425dfc7a91af95d7df7ef8eb 2187 rust-yaml_0.3.0-2.dsc
 8c67157c1c232338c3f0c517dddf48f0c7e16c44 18788 rust-yaml_0.3.0.orig.tar.gz
 82fa76cef30c87f28d6465d02c8325288c5ed0e7 3252 rust-yaml_0.3.0-2.debian.tar.xz
Files: 
 d5c99e0fb92e6c098bd0cc09ce09c811 20052 rust optional 
librust-yaml-dev_0.3.0-2_amd64.deb
 606b8aee6e9d25bd07945e74afd12a38 7095 rust optional 
rust-yaml_0.3.0-2_amd64.buildinfo
 88c898552e85ed33b4508980d42e2fe7 2187 rust optional rust-yaml_0.3.0-2.dsc
 d32e488cad746a3b5e633f9c36bacae7 18788 - - rust-yaml_0.3.0.orig.tar.gz
 b2cd19f8be8d4d1c803d87ece6d79611 3252 - - rust-yaml_0.3.0-2.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQJLBAEBCgA1FiEEhWSUk7LYy5Yue0UiITeAY1BXOwQFAlwMK0YXHHdvbGZnYW5n
QHNpbGJlcm1heXIuYXQACgkQITeAY1BXOwROihAAj8x2Axj6a/RqjAvx2oPyhAQ0
jwb1TrF8XIZR1ZTZwfJCTm1GEnV7mezOoVk0JOnV+TJrXxcJNyfctsL2Je/rw2AO
KrjlxYHL7EhO+ZpsQEAnGgAAG25r65an/D/9CLtEKiwLpiBmK7DEg9cfA9pv9TzZ
Bt09r7MzRD8+GUVk0QJ/SjJhjsNfdX7Dk5t6qfVB6KG86UAnTQ0HNILBDnaqENVk
p7h+3ZEiDPttPLVOAvRpoh8zx2OgUZIPWOlE3xwY82Np5zDOKmChTiG0nbmOSoqX
0vpp4TCf0r9WfeGDosheZuqUQSBKdRz0pboK0o1Xt4kEh9Lm9sHkPPc/DYGoQQAx
1rh5krMOOD9/pFcjh1ChZd3JZOW2Xhvk81tfu2iVD/yQywloI93iorr5yk2GiV0s
CmvaUsLnqZVrMtPWz6x5wHIayeLdSpaY0kIGtaqWcjFvTXDSGpk3eqZZAKZ4oxYO
LzwUhUlmXTCjf9jr04loF/+pcWMulRBJ2UA27KB9zV4ChfshEK5QkUUwsIG1+6ga
yzE+ixciJYpB80a7ijcICsYli5miCNDQqgJeFCwuZi12w9lxbAubsrEC/iltlWir
GmPYjRLlLJ9n7tenT9Ai/ID1k7Ae0be21TvAUmDFFUCkySucBX+eyPTmKGkbxb7Q
r6y/GHLgHHm5fhC5CrE=
=+lg7
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to