[Pkg-rust-maintainers] Bug#1115138: rust-gtk4: FTBFS: error[E0425]: cannot find value `GTK_PAD_ACTION_DIAL` in crate `ffi`
Santiago Vila
sanvila at debian.org
Sat Sep 13 17:29:26 BST 2025
Package: src:rust-gtk4
Version: 0.10.0-2
Severity: serious
Tags: ftbfs forky sid
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build.
Below you will find how the build ends (probably the most relevant part,
but not necessarily). If required, the full build log is available here:
https://people.debian.org/~sanvila/build-logs/202509/
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 could not 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:rust-gtk4, so that this is still
visible in the BTS web page for this package.
Thanks.
--------------------------------------------------------------------------------
[...]
debian/rules clean
dh clean --buildsystem cargo
dh_auto_clean -O--buildsystem=cargo
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: running subprocess (['env', 'RUST_BACKTRACE=1', '/usr/bin/cargo', 'clean', '--verbose', '--verbose'],) {'check': True}
Removed 0 files
dh_autoreconf_clean -O--buildsystem=cargo
dh_clean -XCargo.toml.orig -O--buildsystem=cargo
debian/rules binary
dh binary --buildsystem cargo
dh_update_autotools_config -O--buildsystem=cargo
dh_autoreconf -O--buildsystem=cargo
dh_auto_configure -O--buildsystem=cargo
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
[... snipped ...]
|
125 | #[cfg(allow_clippy)]
| ^^^^^^^^^^^^
|
= 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(allow_clippy)'] }
= help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_clippy)");` 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: `allow_clippy`
--> /usr/share/cargo/registry/memoffset-0.8.0/src/raw_field.rs:141:11
|
141 | #[cfg(not(allow_clippy))]
| ^^^^^^^^^^^^
|
= 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(allow_clippy)'] }
= help: or consider adding `println!("cargo::rustc-check-cfg=cfg(allow_clippy)");` 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: `tuple_ty`
--> /usr/share/cargo/registry/memoffset-0.8.0/src/raw_field.rs:183:7
|
183 | #[cfg(tuple_ty)]
| ^^^^^^^^
|
= 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(tuple_ty)'] }
= help: or consider adding `println!("cargo::rustc-check-cfg=cfg(tuple_ty)");` 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: `maybe_uninit`
--> /usr/share/cargo/registry/memoffset-0.8.0/src/offset_of.rs:23:7
|
23 | #[cfg(maybe_uninit)]
| ^^^^^^^^^^^^
|
= 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(maybe_uninit)'] }
= help: or consider adding `println!("cargo::rustc-check-cfg=cfg(maybe_uninit)");` 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: `maybe_uninit`
--> /usr/share/cargo/registry/memoffset-0.8.0/src/offset_of.rs:37:11
|
37 | #[cfg(not(maybe_uninit))]
| ^^^^^^^^^^^^
|
= 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(maybe_uninit)'] }
= help: or consider adding `println!("cargo::rustc-check-cfg=cfg(maybe_uninit)");` 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: `stable_const`
--> /usr/share/cargo/registry/memoffset-0.8.0/src/offset_of.rs:49:39
|
49 | #[cfg(any(feature = "unstable_const", stable_const))]
| ^^^^^^^^^^^^
|
= 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(stable_const)'] }
= help: or consider adding `println!("cargo::rustc-check-cfg=cfg(stable_const)");` 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: `stable_const`
--> /usr/share/cargo/registry/memoffset-0.8.0/src/offset_of.rs:61:43
|
61 | #[cfg(not(any(feature = "unstable_const", stable_const)))]
| ^^^^^^^^^^^^
|
= 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(stable_const)'] }
= help: or consider adding `println!("cargo::rustc-check-cfg=cfg(stable_const)");` 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: `tuple_ty`
--> /usr/share/cargo/registry/memoffset-0.8.0/src/offset_of.rs:121:7
|
121 | #[cfg(tuple_ty)]
| ^^^^^^^^
|
= 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(tuple_ty)'] }
= help: or consider adding `println!("cargo::rustc-check-cfg=cfg(tuple_ty)");` 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: `memoffset` (lib) generated 17 warnings
Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=field_of [too-long-redacted] it --cfg fieldoffset_has_alloc`
warning: unexpected `cfg` condition name: `fieldoffset_assert_in_const_fn`
--> /usr/share/cargo/registry/field-offset-0.3.6/src/lib.rs:2:13
|
2 | #![cfg_attr(fieldoffset_assert_in_const_fn, feature(const_panic))]
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
= 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(fieldoffset_assert_in_const_fn)'] }
= help: or consider adding `println!("cargo::rustc-check-cfg=cfg(fieldoffset_assert_in_const_fn)");` 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: `fieldoffset_has_alloc`
--> /usr/share/cargo/registry/field-offset-0.3.6/src/lib.rs:8:17
|
8 | #[cfg(all(test, fieldoffset_has_alloc))]
| ^^^^^^^^^^^^^^^^^^^^^
|
= 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(fieldoffset_has_alloc)'] }
= help: or consider adding `println!("cargo::rustc-check-cfg=cfg(fieldoffset_has_alloc)");` 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: `fieldoffset_maybe_uninit`
--> /usr/share/cargo/registry/field-offset-0.3.6/src/lib.rs:73:11
|
73 | #[cfg(fieldoffset_maybe_uninit)]
| ^^^^^^^^^^^^^^^^^^^^^^^^
|
= 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(fieldoffset_maybe_uninit)'] }
= help: or consider adding `println!("cargo::rustc-check-cfg=cfg(fieldoffset_maybe_uninit)");` 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: `fieldoffset_maybe_uninit`
--> /usr/share/cargo/registry/field-offset-0.3.6/src/lib.rs:81:15
|
81 | #[cfg(not(fieldoffset_maybe_uninit))]
| ^^^^^^^^^^^^^^^^^^^^^^^^
|
= 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(fieldoffset_maybe_uninit)'] }
= help: or consider adding `println!("cargo::rustc-check-cfg=cfg(fieldoffset_maybe_uninit)");` 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: `fieldoffset_assert_in_const_fn`
--> /usr/share/cargo/registry/field-offset-0.3.6/src/lib.rs:124:15
|
124 | #[cfg(fieldoffset_assert_in_const_fn)]
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
= 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(fieldoffset_assert_in_const_fn)'] }
= help: or consider adding `println!("cargo::rustc-check-cfg=cfg(fieldoffset_assert_in_const_fn)");` 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: field `0` is never read
--> /usr/share/cargo/registry/field-offset-0.3.6/src/lib.rs:60:25
|
60 | struct PhantomContra<T>(fn(T));
| ------------- ^^^^^
| |
| field in this struct
|
= help: consider removing this field
= note: `#[warn(dead_code)]` on by default
warning: `field-offset` (lib) generated 6 warnings
Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=gtk4_sys [too-long-redacted] .0 --cfg system_deps_have_gtk4`
Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=gio CARG [too-long-redacted] stry=/usr/share/cargo/registry`
Compiling cairo-rs v0.21.1
Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=cairo CA [too-long-redacted] stry=/usr/share/cargo/registry`
warning: unexpected `cfg` condition value: `win32-surface`
--> /usr/share/cargo/registry/cairo-rs-0.21.1/src/lib.rs:290:20
|
290 | #[cfg(all(windows, feature = "win32-surface"))]
| ^^^^^^^^^^^^^^^^^^^^^^^^^
|
= note: expected values for `feature` are: `default`, `freetype`, `freetype-rs`, `glib`, `pdf`, `png`, `ps`, `quartz-surface`, `script`, `svg`, `use_glib`, `v1_16`, `v1_18`, `xcb`, and `xlib`
= help: consider adding `win32-surface` as a feature in `Cargo.toml`
= 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 value: `win32-surface`
--> /usr/share/cargo/registry/cairo-rs-0.21.1/src/lib.rs:293:20
|
293 | #[cfg(all(windows, feature = "win32-surface"))]
| ^^^^^^^^^^^^^^^^^^^^^^^^^
|
= note: expected values for `feature` are: `default`, `freetype`, `freetype-rs`, `glib`, `pdf`, `png`, `ps`, `quartz-surface`, `script`, `svg`, `use_glib`, `v1_16`, `v1_18`, `xcb`, and `xlib`
= help: consider adding `win32-surface` as a feature in `Cargo.toml`
= note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
warning: `cairo-rs` (lib) generated 2 warnings
Compiling graphene-rs v0.21.1
Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=graphene [too-long-redacted] stry=/usr/share/cargo/registry`
Compiling gtk4-macros v0.10.0
Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=gtk4_mac [too-long-redacted] rn proc_macro --cap-lints warn`
Compiling gdk-pixbuf v0.21.1
Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=gdk_pixb [too-long-redacted] stry=/usr/share/cargo/registry`
Compiling pango v0.21.1
Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=pango CA [too-long-redacted] stry=/usr/share/cargo/registry`
Compiling gdk4 v0.10.0
Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=gdk4 CAR [too-long-redacted] stry=/usr/share/cargo/registry`
Compiling gsk4 v0.10.0
Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=gsk4 CAR [too-long-redacted] stry=/usr/share/cargo/registry`
Compiling gtk4 v0.10.0 (/<<PKGBUILDDIR>>)
Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=gtk4 CAR [too-long-redacted] stry=/usr/share/cargo/registry`
error[E0412]: cannot find type `GtkIconPaintableClass` in crate `ffi`
--> src/auto/icon_paintable.rs:27:65
|
27 | pub struct IconPaintable(Object<ffi::GtkIconPaintable, ffi::GtkIconPaintableClass>) @implements gdk::Paintable;
| ^^^^^^^^^^^^^^^^^^^^^ help: a struct with a similar name exists: `GtkIconPaintable`
|
::: /usr/share/cargo/registry/gtk4-sys-0.10.0/src/lib.rs:6938:1
|
6938 | pub struct GtkIconPaintable {
| --------------------------- similarly named struct `GtkIconPaintable` defined here
error[E0425]: cannot find value `GTK_PAD_ACTION_DIAL` in crate `ffi`
--> src/auto/enums.rs:7511:32
|
7511 | Self::Dial => ffi::GTK_PAD_ACTION_DIAL,
| ^^^^^^^^^^^^^^^^^^^ help: a constant with a similar name exists: `GTK_PAD_ACTION_RING`
|
::: /usr/share/cargo/registry/gtk4-sys-0.10.0/src/lib.rs:611:1
|
611 | pub const GTK_PAD_ACTION_RING: GtkPadActionType = 1;
| ----------------------------------------------- similarly named constant `GTK_PAD_ACTION_RING` defined here
error[E0531]: cannot find unit struct, unit variant or constant `GTK_PAD_ACTION_DIAL` in crate `ffi`
--> src/auto/enums.rs:7527:18
|
7527 | ffi::GTK_PAD_ACTION_DIAL => Self::Dial,
| ^^^^^^^^^^^^^^^^^^^ help: a constant with a similar name exists: `GTK_PAD_ACTION_RING`
|
::: /usr/share/cargo/registry/gtk4-sys-0.10.0/src/lib.rs:611:1
|
611 | pub const GTK_PAD_ACTION_RING: GtkPadActionType = 1;
| ----------------------------------------------- similarly named constant `GTK_PAD_ACTION_RING` defined here
error[E0277]: the trait bound `auto::popover::Popover: glib::translate::ToGlibPtr<'_, *mut GtkWidget>` is not satisfied
--> src/auto/menu_button.rs:270:97
|
270 | ffi::gtk_menu_button_set_popover(self.to_glib_none().0, popover.map(|p| p.as_ref()).to_glib_none().0);
| ^^^^^^^^^^^^ the trait `glib::translate::ToGlibPtr<'_, *mut GtkWidget>` is not implemented for `auto::popover::Popover`
|
= help: the following other types implement trait `glib::translate::ToGlibPtr<'a, P>`:
`auto::popover::Popover` implements `glib::translate::ToGlibPtr<'_, *const GtkPopover>`
`auto::popover::Popover` implements `glib::translate::ToGlibPtr<'_, *mut GtkPopover>`
= note: required for `&auto::popover::Popover` to implement `glib::translate::ToGlibPtr<'_, *mut GtkWidget>`
= note: 1 redundant requirement hidden
= note: required for `Option<&auto::popover::Popover>` to implement `glib::translate::ToGlibPtr<'_, *mut GtkWidget>`
Some errors have detailed explanations: E0277, E0412, E0425, E0531.
For more information about an error, try `rustc --explain E0277`.
error: could not compile `gtk4` (lib) due to 4 previous errors
Caused by:
process didn't exit successfully: `CARGO=/usr/bin/cargo CA [too-long-redacted] argo/registry` (exit status: 1)
dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101
make: *** [debian/rules:4: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--------------------------------------------------------------------------------
More information about the Pkg-rust-maintainers
mailing list