Your message dated Wed, 23 Apr 2025 00:20:30 +0000
with message-id <e1u7nqo-00ahsy...@fasolo.debian.org>
and subject line Bug#1102593: fixed in lintian-brush 0.161
has caused the Debian Bug report #1102593,
regarding lintian-brush FTBFS: error: failed to select a version for the 
requirement `hyper = "^0.14"`
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 ow...@bugs.debian.org
immediately.)


-- 
1102593: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1102593
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lintian-brush
Version: 0.160
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=lintian-brush&arch=amd64&ver=0.160%2Bb3&stamp=1744284864&raw=0

...
running build_rust
error: failed to select a version for the requirement `hyper = "^0.14"`
candidate versions found which didn't match: 1.5.2
location searched: directory source `/usr/share/cargo/registry` (which is 
replacing registry `crates-io`)
required by package `debianize v0.158.0 
(/build/reproducible-path/lintian-brush-0.160+b3/debianize)`
perhaps a crate was updated and forgotten to be re-vendored?
error: `cargo metadata --manifest-path debianize/Cargo.toml --format-version 1` 
failed with code 101
...

--- End Message ---
--- Begin Message ---
Source: lintian-brush
Source-Version: 0.161
Done: Jelmer Vernooij <jel...@debian.org>

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

Debian distribution maintenance software
pp.
Jelmer Vernooij <jel...@debian.org> (supplier of updated lintian-brush 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 ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Sun, 22 Dec 2024 19:10:53 +0000
Source: lintian-brush
Architecture: source
Version: 0.161
Distribution: unstable
Urgency: medium
Maintainer: Jelmer Vernooij <jel...@debian.org>
Changed-By: Jelmer Vernooij <jel...@debian.org>
Closes: 1090998 1091929 1102593
Changes:
 lintian-brush (0.161) unstable; urgency=medium
 .
   * dep3-format-patch-author-or-from-is-better: Cope with commented out
     patches or missing patches in debian/patches/series.
     Closes: #1090998
   * rules-requires-root-missing: only set Rules-Requires-Root when
     dpkg < 1.22.13 needs to be supported, and delete it if only
     dpkg >= 1.22.13 is supported. Closes: #1091929
   * Update hyper used. Closes: #1102593
Checksums-Sha1:
 f25f1de6b5a7d1aaeb0613447da29a4f6577b09e 3301 lintian-brush_0.161.dsc
 377e51258ccf5bf8dc27090bcc6dcc97c0dc4bb9 1100300 lintian-brush_0.161.tar.xz
 8495ff4dfc7941a9a2b2c940f2ad28320b14508c 60139 
lintian-brush_0.161_source.buildinfo
Checksums-Sha256:
 c0263cc6f19c2bc5b6dda006e4ed7e1f42686830c46b315bf47b33b18b5f4687 3301 
lintian-brush_0.161.dsc
 4a175d6a29d17a893244cd6bd70260ed951a4cb708f15a73d1eff9c3ebab2ac6 1100300 
lintian-brush_0.161.tar.xz
 ce4e3e4a2bff366ff9674689eb185084149a90967f09c968bf0e18b01b0a114e 60139 
lintian-brush_0.161_source.buildinfo
Files:
 0ad84af812917a823bc34ab01e184bbb 3301 devel optional lintian-brush_0.161.dsc
 5038b90264e7cf14699558200b6acbcc 1100300 devel optional 
lintian-brush_0.161.tar.xz
 cd43853b096429473a563e1ad6eb712b 60139 devel optional 
lintian-brush_0.161_source.buildinfo

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

iQEzBAEBCgAdFiEEgIoEfJX3ae+y722SMG8hYYBCUGYFAmgILxEACgkQMG8hYYBC
UGZhIwf/YKu8+AV5EFUd8s5ztszt19jI+Fv7yXRsJUcEHFQTVLWzH2wPVB1xef46
q3xLHVLXPzttA6nKVL5HZ4yQ2XvWyMy+f1/+kMHGNO0ariYXS0+v28jYzfuii64O
DfvSyOaNzj61egCu6cwJhY5NiadpxI0vMVy/6bRE4zAPjLklniYSR6755pPKyw9Y
ijXZNFUtUQ0YKomutBcccG3vKRzmjiCVglxeHMXhvLQV6i5y+sotCn3rHSD7bEyb
BEf+/dusDZKQHHgK519mCt8015eFVOu7PzajzCPA5xdhP+H5OaRcibkCJFYWaDSM
Y0AWmFd0FxIA3fyLAKVLHlS5RoIDbA==
=i3Kb
-----END PGP SIGNATURE-----

Attachment: pgpvnh0x8QpEZ.pgp
Description: PGP signature


--- End Message ---

Reply via email to