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/202605/

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:reform-setup-wizard, 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
   debian/rules execute_after_dh_auto_clean
make[1]: Entering directory '/<<PKGBUILDDIR>>'
/usr/share/cargo/bin/cargo clean
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
rm -rf /<<PKGBUILDDIR>>/debian/cargo_home
rm -rf /<<PKGBUILDDIR>>/debian/cargo_registry
rm -f debian/cargo-checksum.json
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
   dh_autoreconf_clean -O--buildsystem=cargo
   dh_clean -O--buildsystem=cargo
 debian/rules binary
dh binary --buildsystem=cargo
   dh_update_autotools_config -O--buildsystem=cargo
   dh_autoreconf -O--buildsystem=cargo
   debian/rules execute_before_dh_auto_configure
make[1]: Entering directory '/<<PKGBUILDDIR>>'
/usr/share/cargo/bin/cargo prepare-debian /<<PKGBUILDDIR>>/debian/cargo_registry --link-from-system
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: linking /usr/share/cargo/registry/* into /<<PKGBUILDDIR>>/debian/cargo_registry/
rm -f Cargo.lock
touch debian/cargo-checksum.json
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
   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
debian cargo wrapper: linking /usr/share/cargo/registry/* into /<<PKGBUILDDIR>>/debian/cargo_registry/
   dh_auto_build -O--buildsystem=cargo
   dh_auto_test -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', '-Zavoid-dev-deps', 'build', '--verbose', '--verbose', '-j2', '--target', 'x86_64-unknown-linux-gnu'],) {}
error: failed to select a version for the requirement `libadwaita = "^0.8.0"`
candidate versions found which didn't match: 0.9.1
location searched: directory source `/<<PKGBUILDDIR>>/debian/cargo_registry` (which is replacing registry `crates-io`)
required by package `reform-setup v0.1.0 (/<<PKGBUILDDIR>>)`
perhaps a crate was updated and forgotten to be re-vendored?
dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101
make: *** [debian/rules:18: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess failed with exit status 2
--------------------------------------------------------------------------------

Dear maintainer,

I've prepared an NMU for reform-setup-wizard (versioned as 1.0-14.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I should cancel it.

cu
Adrian

Hi,

Quoting Adrian Bunk (2026-06-11 06:59:53)

whoops, these two issues slipped out of my TODO list. Sorry for that!

Thanks a lot for preparing the NMU. Since I'm on the LowThreshNMU list, you
could've uploaded without delay right from the start and if you are in a rush,
you can still do that.

Thank you for your work and for your NMU! Please don't cancel it. :)

cheers, josch

We believe that the bug you reported is fixed in the latest version of
reform-setup-wizard, 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 1137408@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Adrian Bunk <bunk@debian.org> (supplier of updated reform-setup-wizard 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 ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Thu, 11 Jun 2026 07:51:34 +0300
Source: reform-setup-wizard
Architecture: source
Version: 1.0-14.2
Distribution: unstable
Urgency: medium
Maintainer: Debian Reform Team <team+reform@tracker.debian.org>
Changed-By: Adrian Bunk <bunk@debian.org>
Closes: 1136404 1137408
Changes:
 reform-setup-wizard (1.0-14.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Patch for newer deps. (Closes: #1136404, #1137408)
Checksums-Sha1:
 693fb51f8020c59fd6677c85e11e9df64e67f902 2377 reform-setup-wizard_1.0-14.2.dsc
 3c5457d465eb9e9016524695807e2157ea7c7847 31296 reform-setup-wizard_1.0-14.2.debian.tar.xz
Checksums-Sha256:
 ac5196bbb33f02961958e9af133a7afd2d1d1fe990acd7e02e0420ba3351b642 2377 reform-setup-wizard_1.0-14.2.dsc
 d0edc333147382bb0664045aa789013b76f494e8cd680a8bc61493aaef0053cb 31296 reform-setup-wizard_1.0-14.2.debian.tar.xz
Files:
 0d70d923c25c4e5c701cd4dd7d31dfb1 2377 utils optional reform-setup-wizard_1.0-14.2.dsc
 f6a057a43bae2cf774b5bdb311efd514 31296 utils optional reform-setup-wizard_1.0-14.2.debian.tar.xz
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmoqQEQACgkQiNJCh6LY
mLGKVw/+K3gioQFBwNvNbloVtC78YfYmQA6GOcnuS064lCR0NmxrCq8A7RlzufEz
HVf3ktb2iF5GAOvugaBs0IMhkL15GbmqK5Om3zkiW3bCmsfV65ZWIQ3p6DS7CeZJ
p9jVPuBQDJT//dxTI2hAEvQtbxblEwAJfuzVb8HhbiOKz6YPaHmH2iRdVpJXuGCk
TD1rdAyGPx13rZi4w/pcuoH1wBCvLq/mkCyWwTRms/QJfVbWXW4lu5bzxko7V4oj
R5eTfGP54D+806tvqoRWXs1yUw2tu97sLTljrHDBE2cFueKRVdhZj0Fgw/sEpWOs
b6HS8rr5nHBcsVYUpcMylKJqGL9Ids9vPTahMRXmVv2qaqj/IwRwMMmDV0hqIlnq
dYT9cZxNiJM0N1I1xHPFbK8b/8Z/LxEmMlqEP/o3QSxMIMf6Gb0eW4Zjubntk6lv
S42n8O0EIefhRszqELFLFmIDimAdsAjPdso94UpxOXFGwu18IwW8qfgytBRIu6g7
xrj+GYVe3DoAOk0CizOrou8L/tUtgXzkI0EzqpDJNg3lkqQfwf1EaWpvA1iYk+Ll
2GoWjTuXd43+Akp3rOMe1heWiC1FiBr2QQ7MpQFORgd3EPIJoZeLQHxsvmYu3PsG
cE3PWD7P98viRRUMD0Xn41MyUu3bLDLyEXA9kGU/UM6yGLfAvPQ=
=YHpg
-----END PGP SIGNATURE-----

Hi,

I try to avoid doing anything in my NMU workflow package/maintainer-specific,
there is nothing bad about giving maintainers a few days to review my
changes or even making a maintainer upload (which happens frequently).

I've had some bad experiences with unhappy maintainers after 0-day NMUs,
uploading to delayed avoids a lot of hassle for me.

I've also mostly stopped submitting patches to the BTS, for less trivial
fixes an upload to DELAYED/14 is my default way of sending the maintainer
a patch - and avoids me having to touch the package again for an NMU
later when there is no maintainer reaction.

I'm sometimes uploading > 100 NMUs with RC bug fixes in a week,
that's why I have my own workflows to minimize work and hassle
for me.

Thanks, done.

cu
Adrian

Hi,

Quoting Adrian Bunk (2026-06-11 08:52:22)

that makes sene — thank you for your extensive explanation!

And thank you for fixing bugs in my package. Much appreciated. :)

cheers, josch