Your message dated Sat, 03 Oct 2026 07:19:05 +0000
with message-id <[email protected]>
and subject line Bug#1149782: fixed in rust-gtk4-macros 0.11.5-2
has caused the Debian Bug report #1149782,
regarding warp: FTBFS: error[E0308]: mismatched types
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.)
--
1149782: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1149782
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:warp
Version: 1.0.0-3
Severity: serious
Tags: ftbfs forky sid
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/202610/
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:warp, so that this is still
visible in the BTS web page for this package.
Thanks.
--------------------------------------------------------------------------------
[...]
help: consider adding a leading `b`
|
105 | if name == QName("object") || name == QName(b"template") {
| +
error[E0308]: mismatched types
-->
/<<PKGBUILDDIR>>/debian/cargo_registry/gtk4-macros-0.11.5/src/composite_template_derive.rs:108:71
|
108 | .find_map(|a| a.ok().and_then(|a| (a.key ==
QName("id")).then_some(a)));
| -----
^^^^ expected `&[u8]`, found `&str`
| |
| arguments
to this struct are incorrect
|
= note: expected reference `&[u8]`
found reference `&'static str`
note: tuple struct defined here
--> /<<PKGBUILDDIR>>/debian/cargo_registry/quick-xml-0.38.4/src/name.rs:87:12
|
87 | pub struct QName<'a>(pub &'a [u8]);
| ^^^^^
help: consider adding a leading `b`
|
108 | .find_map(|a| a.ok().and_then(|a| (a.key ==
QName(b"id")).then_some(a)));
| +
error[E0277]: the trait bound `String: Borrow<[u8]>` is not satisfied
-->
/<<PKGBUILDDIR>>/debian/cargo_registry/gtk4-macros-0.11.5/src/composite_template_derive.rs:111:37
|
111 | ids_left.remove(id);
| ------ ^^ the trait `Borrow<[u8]>` is not
implemented for `String`
| |
| required by a bound introduced by this call
|
help: the trait `Borrow<[u8]>` is not implemented for `String`
but trait `Borrow<str>` is implemented for it
--> /usr/src/rustc-1.96.1/library/alloc/src/str.rs:189:0
= help: for that trait implementation, expected `str`, found `[u8]`
note: required by a bound in `HashMap::<K, V, S, A>::remove`
--> /usr/src/rustc-1.96.1/library/std/src/collections/hash/map.rs:1383:4
warning: unexpected `cfg` condition name: `poly1305_force_soft`
--> /usr/share/cargo/registry/poly1305-0.8.0/src/lib.rs:67:9
|
67 | not(poly1305_force_soft),
| ^^^^^^^^^^^^^^^^^^^
|
= help: expected names are: `docsrs`, `feature`, and `test` and 31 more
= help: consider using a Cargo feature instead
= help: or consider adding in `Cargo.toml` the `check-cfg` lint config for
the lint:
[lints.rust]
unexpected_cfgs = { level = "warn", check-cfg =
['cfg(poly1305_force_soft)'] }
= help: or consider adding
`println!("cargo::rustc-check-cfg=cfg(poly1305_force_soft)");` to the top of
the `build.rs`
= note: see
<https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for
more information about checking conditional configuration
= note: `#[warn(unexpected_cfgs)]` on by default
warning: unexpected `cfg` condition name: `fuzzing`
--> /usr/share/cargo/registry/poly1305-0.8.0/src/lib.rs:69:9
|
69 | any(fuzzing, test)
| ^^^^^^^
|
= help: consider using a Cargo feature instead
= help: or consider adding in `Cargo.toml` the `check-cfg` lint config for
the lint:
[lints.rust]
unexpected_cfgs = { level = "warn", check-cfg = ['cfg(fuzzing)'] }
= help: or consider adding
`println!("cargo::rustc-check-cfg=cfg(fuzzing)");` to the top of the `build.rs`
= note: see
<https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for
more information about checking conditional configuration
warning: unexpected `cfg` condition name: `poly1305_force_soft`
--> /usr/share/cargo/registry/poly1305-0.8.0/src/lib.rs:75:9
|
75 | not(poly1305_force_soft)
| ^^^^^^^^^^^^^^^^^^^
|
= help: consider using a Cargo feature instead
= help: or consider adding in `Cargo.toml` the `check-cfg` lint config for
the lint:
[lints.rust]
unexpected_cfgs = { level = "warn", check-cfg =
['cfg(poly1305_force_soft)'] }
= help: or consider adding
`println!("cargo::rustc-check-cfg=cfg(poly1305_force_soft)");` to the top of
the `build.rs`
= note: see
<https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for
more information about checking conditional configuration
warning: unexpected `cfg` condition name: `poly1305_force_soft`
--> /usr/share/cargo/registry/poly1305-0.8.0/src/lib.rs:81:9
|
81 | not(poly1305_force_soft)
| ^^^^^^^^^^^^^^^^^^^
|
= help: consider using a Cargo feature instead
= help: or consider adding in `Cargo.toml` the `check-cfg` lint config for
the lint:
[lints.rust]
unexpected_cfgs = { level = "warn", check-cfg =
['cfg(poly1305_force_soft)'] }
= help: or consider adding
`println!("cargo::rustc-check-cfg=cfg(poly1305_force_soft)");` to the top of
the `build.rs`
= note: see
<https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for
more information about checking conditional configuration
warning: unexpected `cfg` condition name: `poly1305_force_soft`
--> /usr/share/cargo/registry/poly1305-0.8.0/src/lib.rs:167:9
|
167 | not(poly1305_force_soft),
| ^^^^^^^^^^^^^^^^^^^
|
= help: consider using a Cargo feature instead
= help: or consider adding in `Cargo.toml` the `check-cfg` lint config for
the lint:
[lints.rust]
unexpected_cfgs = { level = "warn", check-cfg =
['cfg(poly1305_force_soft)'] }
= help: or consider adding
`println!("cargo::rustc-check-cfg=cfg(poly1305_force_soft)");` to the top of
the `build.rs`
= note: see
<https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for
more information about checking conditional configuration
warning: unexpected `cfg` condition name: `fuzzing`
--> /usr/share/cargo/registry/poly1305-0.8.0/src/lib.rs:169:9
|
169 | any(fuzzing, test)
| ^^^^^^^
|
= help: consider using a Cargo feature instead
= help: or consider adding in `Cargo.toml` the `check-cfg` lint config for
the lint:
[lints.rust]
unexpected_cfgs = { level = "warn", check-cfg = ['cfg(fuzzing)'] }
= help: or consider adding
`println!("cargo::rustc-check-cfg=cfg(fuzzing)");` to the top of the `build.rs`
= note: see
<https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for
more information about checking conditional configuration
warning: unexpected `cfg` condition name: `poly1305_force_soft`
--> /usr/share/cargo/registry/poly1305-0.8.0/src/backend.rs:5:9
|
5 | not(poly1305_force_soft)
| ^^^^^^^^^^^^^^^^^^^
|
= help: consider using a Cargo feature instead
= help: or consider adding in `Cargo.toml` the `check-cfg` lint config for
the lint:
[lints.rust]
unexpected_cfgs = { level = "warn", check-cfg =
['cfg(poly1305_force_soft)'] }
= help: or consider adding
`println!("cargo::rustc-check-cfg=cfg(poly1305_force_soft)");` to the top of
the `build.rs`
= note: see
<https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for
more information about checking conditional configuration
warning: unexpected `cfg` condition name: `poly1305_force_soft`
--> /usr/share/cargo/registry/poly1305-0.8.0/src/backend.rs:11:9
|
11 | not(poly1305_force_soft)
| ^^^^^^^^^^^^^^^^^^^
|
= help: consider using a Cargo feature instead
= help: or consider adding in `Cargo.toml` the `check-cfg` lint config for
the lint:
[lints.rust]
unexpected_cfgs = { level = "warn", check-cfg =
['cfg(poly1305_force_soft)'] }
= help: or consider adding
`println!("cargo::rustc-check-cfg=cfg(poly1305_force_soft)");` to the top of
the `build.rs`
= note: see
<https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for
more information about checking conditional configuration
Some errors have detailed explanations: E0277, E0308.
For more information about an error, try `rustc --explain E0277`.
error: could not compile `gtk4-macros` (lib) due to 4 previous errors
Caused by:
process didn't exit successfully: `CARGO=/usr/bin/cargo CA
[too-long-redacted] ap-lints warn` (exit status: 1)
warning: build failed, waiting for other jobs to finish...
warning: `poly1305` (lib) generated 8 warnings
[70/71] /usr/bin/msgfmt -o po/zh_TW/LC_MESSAGES/warp-gtk.mo ../po/zh_TW.po
FAILED: [code=101] src/warp-gtk
/usr/bin/env /usr/share/cargo/bin/cargo build --manifest-path
/<<PKGBUILDDIR>>/Cargo.toml --target-dir
/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/src --no-default-features --release
--features meson,qr_code_scanning && cp
src/x86_64-unknown-linux-gnu/release/warp-gtk src/warp-gtk
ninja: build stopped: subcommand failed.
dh_auto_build: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j2 -v
returned exit code 101
make: *** [debian/rules:13: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess failed with exit
status 2
--------------------------------------------------------------------------------
--- End Message ---
--- Begin Message ---
Source: rust-gtk4-macros
Source-Version: 0.11.5-2
Done: Jeremy Bícha <[email protected]>
We believe that the bug you reported is fixed in the latest version of
rust-gtk4-macros, 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.
Jeremy Bícha <[email protected]> (supplier of updated rust-gtk4-macros 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, 3 Oct 2026 08:35:30 +0200
Source: rust-gtk4-macros
Built-For-Profiles: derivative.ubuntu noudeb
Architecture: source
Version: 0.11.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers
<[email protected]>
Changed-By: Jeremy Bícha <[email protected]>
Closes: 1149782
Changes:
rust-gtk4-macros (0.11.5-2) unstable; urgency=medium
.
* Team upload
* Package gtk4-macros 0.11.5 from crates.io using debcargo 2.8.4
* Fix relax-quick-xml patch (Closes: #1149782)
Checksums-Sha1:
eb73e208ba1957cc28aee901b216f7512091a8d1 2720 rust-gtk4-macros_0.11.5-2.dsc
e2bfc2dcf6bdb6f5652fc22170f9d27b3ef63ee0 5048
rust-gtk4-macros_0.11.5-2.debian.tar.xz
2eae92c20f8d70bf6ecd254ba3fb27e9bd3d376f 8327
rust-gtk4-macros_0.11.5-2_source.buildinfo
Checksums-Sha256:
67b4c58d5c5141a5edd3442684d8dcd8202a92f33502f8d4cfed0ce5ed818168 2720
rust-gtk4-macros_0.11.5-2.dsc
009a584420e59a95832ebd7c265786873b130a58481db96b04d56c3a00baa443 5048
rust-gtk4-macros_0.11.5-2.debian.tar.xz
5d04441d82d13a217f0b87e37d28f276061627869f23bb0c74a1998cfc87ea49 8327
rust-gtk4-macros_0.11.5-2_source.buildinfo
Files:
2f8bcca0b00b4c71d61cc39f005b03f1 2720 rust optional
rust-gtk4-macros_0.11.5-2.dsc
723cb77e66b68f3e85b5111e7188ed18 5048 rust optional
rust-gtk4-macros_0.11.5-2.debian.tar.xz
1b1d86ced179a65a2fedad992f257810 8327 rust optional
rust-gtk4-macros_0.11.5-2_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmrAp/EACgkQ5mx3Wuv+
bH2Vrw/+MTzmjJk59ShXKA/vpC2R/RQ2QuxuztqvR0zJ4cM7oovQTK6720t8Xv3w
yDETD7hoYtnnZirgSWokkA24GB85YU8jcBLZodhTfMciU7UhjRksMi3LXQyIrgT7
1HpC0ZpZn5qKKR42Wu4SkdE16cNcBqyLKMGwTasx/Lmv6uk7n7sz64kw70A6KUHA
zXhJnd9+deJu1GCW3eCj6aDzQlnP9gVyE3QuloAZH/crifUle9mCmZk0xbpGdeHz
l6Uvob951JV7pMPoEZPR8NTxV/UOi6nPeHXTypxWzwirtTQuwbNe1htGNRuuW4Kq
RS2UuLc5z6lID1jLamkEwjDHL8HvbJvjQ8M7Y+YIPTonCCaWR0dnmDbFNp6dA7wB
aiCIzK80wfgApVqOQIWhMYWEklsbChEqWdKXeel8wIiM4d9JZDOeYwuZB6UyYlBU
BiL0lKoZ9KlPKIX8kYENCa6CS3gAI/UuDXh1XziqJ2RT57+T9ckq6XWJVelvL3yu
Iu4JdvRZVv6OPKPMMiCcTHNbbp/97NtlSiPc6ho5rj4cTtr2q+Hfdbhthl94R7Er
HcrSK15MdgNnrGe0aZfDBsG9kduh1iW44opoqYDV9RlNsRTIPAMkNz3K6O693cZB
noMvXUPdMWVwA12lZSRh549tP8WoeHUKrvtX6R29tV8yBt8YzpU=
=7/v1
-----END PGP SIGNATURE-----
pgplKqYsWjAt6.pgp
Description: PGP signature
--- End Message ---
