Your message dated Tue, 16 Dec 2025 19:36:20 +0000
with message-id <[email protected]>
and subject line Bug#1122980: fixed in rust-gio 0.21.5-2
has caused the Debian Bug report #1122980,
regarding rust-gio: autopkgtest regression
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.)


-- 
1122980: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1122980
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: rust-gio
Version: 0.21.5-1
Severity: serious

https://tracker.debian.org/pkg/rust-gio

Issues preventing migration:
∙ ∙ Autopkgtest for rust-gio/0.21.5-1: amd64: Regression ♻ (reference ♻), 
arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: 
Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)


https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-gio/67081998/log.gz

...
1105s failures:
1105s 
1105s ---- settings::test::bool_set_get stdout ----
1105s 
1105s thread 'settings::test::bool_set_get' panicked at src/settings.rs:245:71:
1105s called `Option::unwrap()` on a `None` value
1105s stack backtrace:
1105s    0: __rustc::rust_begin_unwind
1105s              at /usr/src/rustc-1.90.0/library/std/src/panicking.rs:697:5
1105s    1: core::panicking::panic_fmt
1105s              at /usr/src/rustc-1.90.0/library/core/src/panicking.rs:75:14
1105s    2: core::panicking::panic
1105s              at /usr/src/rustc-1.90.0/library/core/src/panicking.rs:145:5
1105s    3: core::option::unwrap_failed
1105s              at /usr/src/rustc-1.90.0/library/core/src/option.rs:2130:5
1105s    4: core::option::Option<T>::unwrap
1105s              at /usr/src/rustc-1.90.0/library/core/src/option.rs:1009:21
1105s    5: gio::settings::test::set_env::{{closure}}
1105s              at ./src/settings.rs:245:71
1105s    6: std::sync::poison::once::Once::call_once::{{closure}}
1105s              at 
/usr/src/rustc-1.90.0/library/std/src/sync/poison/once.rs:155:41
1105s    7: std::sys::sync::once::futex::Once::call
1105s              at 
/usr/src/rustc-1.90.0/library/std/src/sys/sync/once/futex.rs:178:21
1105s    8: std::sync::poison::once::Once::call_once
1105s              at 
/usr/src/rustc-1.90.0/library/std/src/sync/poison/once.rs:155:20
1105s    9: gio::settings::test::set_env
1105s              at ./src/settings.rs:244:14
1105s   10: gio::settings::test::bool_set_get::{{closure}}
1105s              at ./src/settings.rs:285:9
1105s   11: core::ops::function::FnOnce::call_once
1105s              at 
/usr/src/rustc-1.90.0/library/core/src/ops/function.rs:253:5
1105s   12: serial_test::serial_code_lock::local_serial_core
1105s              at 
/usr/share/cargo/registry/serial_test-2.0.0/src/serial_code_lock.rs:25:5
1105s   13: gio::settings::test::bool_set_get
1105s              at ./src/settings.rs:283:5
1105s   14: gio::settings::test::bool_set_get::{{closure}}
1105s              at ./src/settings.rs:284:22
1105s   15: core::ops::function::FnOnce::call_once
1105s              at 
/usr/src/rustc-1.90.0/library/core/src/ops/function.rs:253:5
1105s   16: core::ops::function::FnOnce::call_once
1105s              at 
/usr/src/rustc-1.90.0/library/core/src/ops/function.rs:253:5
1105s note: Some details are omitted, run with `RUST_BACKTRACE=full` for a 
verbose backtrace.
1105s 
1105s ---- settings::test::string_get stdout ----
1105s 
1105s thread 'settings::test::string_get' panicked at src/settings.rs:244:14:
1105s Once instance has previously been poisoned
1105s stack backtrace:
1105s    0: __rustc::rust_begin_unwind
1105s              at /usr/src/rustc-1.90.0/library/std/src/panicking.rs:697:5
1105s    1: core::panicking::panic_fmt
1105s              at /usr/src/rustc-1.90.0/library/core/src/panicking.rs:75:14
1105s    2: std::sys::sync::once::futex::Once::call
1105s              at 
/usr/src/rustc-1.90.0/library/std/src/sys/sync/once/futex.rs:150:21
1105s    3: std::sync::poison::once::Once::call_once
1105s              at 
/usr/src/rustc-1.90.0/library/std/src/sync/poison/once.rs:155:20
1105s    4: gio::settings::test::set_env
1105s              at ./src/settings.rs:244:14
1105s    5: gio::settings::test::string_get::{{closure}}
1105s              at ./src/settings.rs:277:9
1105s    6: core::ops::function::FnOnce::call_once
1105s              at 
/usr/src/rustc-1.90.0/library/core/src/ops/function.rs:253:5
1105s    7: serial_test::serial_code_lock::local_serial_core
1105s              at 
/usr/share/cargo/registry/serial_test-2.0.0/src/serial_code_lock.rs:25:5
1105s    8: gio::settings::test::string_get
1105s              at ./src/settings.rs:275:5
1105s    9: gio::settings::test::string_get::{{closure}}
1105s              at ./src/settings.rs:276:20
1105s   10: core::ops::function::FnOnce::call_once
1105s              at 
/usr/src/rustc-1.90.0/library/core/src/ops/function.rs:253:5
1105s   11: core::ops::function::FnOnce::call_once
1105s              at 
/usr/src/rustc-1.90.0/library/core/src/ops/function.rs:253:5
1105s note: Some details are omitted, run with `RUST_BACKTRACE=full` for a 
verbose backtrace.
1105s 
1105s 
1105s failures:
1105s     settings::test::bool_set_get
1105s     settings::test::string_get
1105s 
1105s test result: FAILED. 84 passed; 2 failed; 0 ignored; 0 measured; 0 
filtered out; finished in 0.72s
1105s 
1105s error: test failed, to rerun pass `--lib`
1106s autopkgtest [11:35:50]: test librust-gio-dev:: -----------------------]
1106s autopkgtest [11:35:50]: test librust-gio-dev::  - - - - - - - - - - 
results - - - - - - - - - -
1106s librust-gio-dev:     FAIL non-zero exit status 101
1106s autopkgtest [11:35:50]: @@@@@@@@@@@@@@@@@@@@ summary
1106s rust-gio:@           FAIL non-zero exit status 101
1106s librust-gio-dev:default FAIL non-zero exit status 101
1106s librust-gio-dev:v2_58 FAIL non-zero exit status 101
1106s librust-gio-dev:v2_60 FAIL non-zero exit status 101
1106s librust-gio-dev:v2_62 FAIL non-zero exit status 101
1106s librust-gio-dev:v2_64 FAIL non-zero exit status 101
1106s librust-gio-dev:v2_66 FAIL non-zero exit status 101
1106s librust-gio-dev:v2_68 FAIL non-zero exit status 101
1106s librust-gio-dev:v2_70 FAIL non-zero exit status 101
1106s librust-gio-dev:v2_72 FAIL non-zero exit status 101
1106s librust-gio-dev:v2_74 FAIL non-zero exit status 101
1106s librust-gio-dev:v2_76 FAIL non-zero exit status 101
1106s librust-gio-dev:v2_78 FAIL non-zero exit status 101
1106s librust-gio-dev:v2_80 FAIL non-zero exit status 101
1106s librust-gio-dev:v2_82 FAIL non-zero exit status 101
1106s librust-gio-dev:v2_84 FAIL non-zero exit status 101
1106s librust-gio-dev:v2_86 FAIL non-zero exit status 101
1106s librust-gio-dev:     FAIL non-zero exit status 101

--- End Message ---
--- Begin Message ---
Source: rust-gio
Source-Version: 0.21.5-2
Done: Peter Michael Green <[email protected]>

We believe that the bug you reported is fixed in the latest version of
rust-gio, 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.
Peter Michael Green <[email protected]> (supplier of updated rust-gio 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: SHA256

Format: 1.8
Date: Tue, 16 Dec 2025 18:57:02 +0000
Source: rust-gio
Architecture: source
Version: 0.21.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 
<[email protected]>
Changed-By: Peter Michael Green <[email protected]>
Closes: 1122980
Changes:
 rust-gio (0.21.5-2) unstable; urgency=medium
 .
   * Team upload.
   * Package gio 0.21.5 from crates.io using debcargo 2.7.11
   * Fix running tests with a read-only crate directory but a writable
     target directory, as is used in autopkgtests (Closes: #1122980)
Checksums-Sha1:
 64701efa9e91908f655a12aeb3e2febba0e51ac2 2919 rust-gio_0.21.5-2.dsc
 0481e92e103e4535cf6483a82280f1c9168ee394 4780 rust-gio_0.21.5-2.debian.tar.xz
 e15809569026bfb86e96b2035d0521e551828f2c 9063 
rust-gio_0.21.5-2_source.buildinfo
Checksums-Sha256:
 dfdce69850354c2d3287d4c1c409ca5451857fbf10d1afde3654157c7dcc05af 2919 
rust-gio_0.21.5-2.dsc
 734d165e4ff8dac7392ec677a03c213b3554f5c5f7a700892d3f88e85ace68c2 4780 
rust-gio_0.21.5-2.debian.tar.xz
 be4531ece2bf7830a7b9087df91e5e190f6939279214a631eafb1bb2be0f2f56 9063 
rust-gio_0.21.5-2_source.buildinfo
Files:
 5cb63a276a038727ea8d937486b94fed 2919 rust optional rust-gio_0.21.5-2.dsc
 50fa59e5f46ddf1129e317e7967cd6f3 4780 rust optional 
rust-gio_0.21.5-2.debian.tar.xz
 4e788dbcea76db39476a98dd8010d662 9063 rust optional 
rust-gio_0.21.5-2_source.buildinfo

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

iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmlBrnoUHHBsdWd3YXNo
QGRlYmlhbi5vcmcACgkQDEjqKnqP/Xt8vQ//d/nAtpXpmy7kvvJhnG1YziKKi90s
nLPaDhxDRfGB+10r4zs9cXV+cxk7X+g9NUQNrxfkNT2jdFsG01L+T1iMOTyGKFhE
+7I6MIsAAPk5Ps/geHiQKLZ72m322+rQqHWSWFkWGxTxJwGce2nSiOLEXUg6nWua
QH6Utkk1ZobqXl1djybrBjaEiul830AEQjBwSusQztwmEqqbI1WnlR36F6SNy8fR
9gB3f8TjMVQEHxC8JXO1Cm32fSHPtpey0yq7QuxMgry3eJW7Ns4d4cNUHbFQi52x
uXaV5gOr44QaMvUZi/BMyqHqEaUo/CyI0iT2f3UDE40Vrq5HWPQM4UjS2SJcSfjj
rP74XPp9v+sIQ5oM7zx7yb4JnkSU1rcd5pR6UMpWGkWRyQkRAHS8P6isn0oR3Ion
sRpwhO9E6og8+m9Gp2BXRh7Ls6RyeLrGau4YF6Q9ycVMlWjRu0flyDA7nWnFdN3r
DewGxhAY0ZqNQXV23/9refHkbOouI2kXsb6zYonqzjnhYnKxryqveH7NzBp5Gy6j
MowQfmzC5Eqio4zQ91WPgrx3CxeskhaYkt+9u+jPRuzuvHbGnO7vPWwfw7RcSd8Q
7NL+LfA7hj4MY45Ugn7ohtc68UtyM6Xl0usxFIB/tB5tVQWnKA1fXwn/A7f3eXU+
9035l4qLnaIDCpo=
=B3v6
-----END PGP SIGNATURE-----

Attachment: pgpdBV03ZjKxD.pgp
Description: PGP signature


--- End Message ---

Reply via email to