Your message dated Sun, 14 Sep 2025 12:15:23 +0000
with message-id <[email protected]>
and subject line Bug#1115138: fixed in rust-gtk4-sys 0.10.0-3
has caused the Debian Bug report #1115138,
regarding rust-gtk4: FTBFS: error[E0425]: cannot find value
`GTK_PAD_ACTION_DIAL` in crate `ffi`
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.)
--
1115138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1115138
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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
--------------------------------------------------------------------------------
--- End Message ---
--- Begin Message ---
Source: rust-gtk4-sys
Source-Version: 0.10.0-3
Done: Jeremy Bícha <[email protected]>
We believe that the bug you reported is fixed in the latest version of
rust-gtk4-sys, 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-sys 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: Sun, 14 Sep 2025 06:28:50 -0400
Source: rust-gtk4-sys
Built-For-Profiles: noudeb
Architecture: source
Version: 0.10.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers
<[email protected]>
Changed-By: Jeremy Bícha <[email protected]>
Closes: 1115138
Changes:
rust-gtk4-sys (0.10.0-3) unstable; urgency=medium
.
* Team upload
* Package gtk4-sys 0.10.0 from crates.io using debcargo 2.7.10
* Stop ignoring cross_validate_constants_with_c test results
(Closes: #1115138)
* Build with gtk4 4.20
* Stop marking tests as broken
Checksums-Sha1:
6f4918e2ff2371b7900550f98f5f08cc86a4c5a8 3123 rust-gtk4-sys_0.10.0-3.dsc
850d18b62fdff8495cffe70745f964848ce6e1b6 5844
rust-gtk4-sys_0.10.0-3.debian.tar.xz
df5d1306b3becffd5106ccbc9eb323aa1171f838 17876
rust-gtk4-sys_0.10.0-3_source.buildinfo
Checksums-Sha256:
e83c50d4b2323cd9a08f4c72871343fe95cf0a72b3f3cd3ddb8bb5034199e8ec 3123
rust-gtk4-sys_0.10.0-3.dsc
5d996e90139604c838b851611f34934425ffe630c88feb31fd7a7ebdb7a66e12 5844
rust-gtk4-sys_0.10.0-3.debian.tar.xz
c923b9a91a39fab4990b2984063ccc7c964b5107a5671c30f876f7599e5deaae 17876
rust-gtk4-sys_0.10.0-3_source.buildinfo
Files:
cb34b4ddd646b52b6259d16b23cab34b 3123 rust optional rust-gtk4-sys_0.10.0-3.dsc
e9f4b2fe784f795f5bc3600fe95a4ff3 5844 rust optional
rust-gtk4-sys_0.10.0-3.debian.tar.xz
7a2fc1bd9c706fbb91af63d7e033da65 17876 rust optional
rust-gtk4-sys_0.10.0-3_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmjGnL0ACgkQ5mx3Wuv+
bH3XVBAAsBuctYSVG799S3Q0PragkQhsBpEhrFSWTIN/uQYUwRRJl2tBZwJffINk
WLPx39IxzVEDJgidPGfJyg6pAoiMZseMaSalqGK97I4mKCj4cwnG2O3tK9hfLlo2
00/t3Lm4/XIINbDXkJ1c+dDUhRyg62DPX16JY7IVMq+78xXxloVETd2lkZ5O2P7A
Z2ZQTJjjN+ivqrpv9qcvNlI64n0pbWtiB8HXok0jAgXybZbT5coX6RzTwSy0KknK
CT4zQvtXGosovY3ssL9bjBBjbPq/quelFuRZC7yMCfEs7Y/cSbrqeO5PL/IqZHcg
+nPKkZiPXMSOtUIhDDwPH1mMsq//JMyzQrbQkYOxeoRboMCbdCv0Tgrj6TYzNYwj
gOfKPBdfxtjOMNLGjbBi/HcOHtu0sN4Ow3+RFbe+VEJruNZpCdK0MNVKnjLNojpZ
C2fU/tf44xAUuxbpMPFLvdjEicqV/YR80EtkzfyDcT5iNTWvV7AEY7YDpLzI79Qy
exBJyJjbh6JzmIkKKO4BdubZdzJgJMAu4BJ3/wJHylJivh/J+0vzBgDpIMUzoQpe
Ht6/SofhqHdQblmEOoj8r/QWIC/LOaoqtrG7fOrD/mK5gxd8R6/bbdm1JHvqa8hO
vMkQJi5H1k9xZ/NNqKyJY3bCPjxv/uVS/u/M8lmZr+MwGbc7KkA=
=iPN7
-----END PGP SIGNATURE-----
pgpuX37VJ6Ib8.pgp
Description: PGP signature
--- End Message ---
