Your message dated Sun, 02 Feb 2025 18:19:03 +0000
with message-id <[email protected]>
and subject line Bug#1094093: fixed in hippotat 1.2.0
has caused the Debian Bug report #1094093,
regarding hippotat: FTBFS: make[1]: *** [Makefile:52: stamp/cargo-build] Error 
101
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.)


-- 
1094093: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1094093
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: hippotat
Version: 1.1.12
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: [email protected]
Usertags: ftbfs-20250124 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[1]: Entering directory '/build/reproducible-path/hippotat-1.1.12'
> cargo build --release  --workspace
> rm -rf docs/html
> m=hippotat-setup-permissions.8; pod2man --section=${m##*.} --date="Hippotat" \
>       --center=" " --name=${m%.*} \
>       hippotat-setup-permissions.8.pod hippotat-setup-permissions.8
> sphinx-build -M html docs docs 
> debian cargo wrapper: options, profiles, parallel, lto: ['parallel=8'] [] 
> ['-j8'] 
> debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu, 
> x86_64-linux-gnu
> debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1', 
> '/usr/bin/cargo', '-Zavoid-dev-deps', 'build', '--verbose', '--verbose', 
> '-j8', '--target', 'x86_64-unknown-linux-gnu', '--release', '--workspace'],) 
> {}
> warning: a `-j` argument was passed to Cargo but Cargo is also configured 
> with an external jobserver in its environment, ignoring the `-j` parameter
> error: failed to select a version for the requirement `hyper = "^0.14.7"`
> 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 `hippotat v1.1.12 
> (/build/reproducible-path/hippotat-1.1.12)`
> perhaps a crate was updated and forgotten to be re-vendored?
> make[1]: *** [Makefile:52: stamp/cargo-build] Error 101


The full build log is available from:
http://qa-logs.debian.net/2025/01/24/hippotat_1.1.12_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20250124;[email protected]
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20250124&[email protected]&allbugs=1&cseverity=1&ctags=1&caffected=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

--- End Message ---
--- Begin Message ---
Source: hippotat
Source-Version: 1.2.0
Done: Ian Jackson <[email protected]>

We believe that the bug you reported is fixed in the latest version of
hippotat, 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.
Ian Jackson <[email protected]> (supplier of updated hippotat 
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, 02 Feb 2025 16:59:18 +0000
Source: hippotat
Architecture: source
Version: 1.2.0
Distribution: unstable
Urgency: medium
Maintainer: Ian Jackson <[email protected]>
Changed-By: Ian Jackson <[email protected]>
Closes: 1094093
Changes:
 hippotat (1.2.0) unstable; urgency=medium
 .
   HTTP implementation changed:
   * Client now uses reqwest (and thus hyper 1)
   * Server now uses hyper 1
   * Closes: #1094093.  [Report from Lucas Nussbaum]
 .
   Build system:
   * Makefile: Add + sigil before cargo invocations.
     Fixes compatibility with recent GNU make.
   * autopkgtests: Declare isolation-machine restriction,
     rather than x-hippotat-adt-broken-in-debci.
 .
   Dependency updates:
   * New deps: http-body 1.0.1, http-body-util 0.1.2, hyper-util 0.1.10
   * Require backtrace 0.3.74, tokio 1.43
   * Allow educe 0.6, itertools 0.14, thiserror 2
   * cargo update (upstream Cargo.lock)
 .
   Internal tidying up:
   * HACKING.md: New file with some notes in.
   * Clarifications to config item defaulting traits.
Checksums-Sha1:
 f48182c0615054564ea74602b2ed46141a1c4961 3890 hippotat_1.2.0.dsc
 071b42e582e7018e09aa9049e2b0fe2f66c8e069 119930 hippotat_1.2.0.tar.gz
Checksums-Sha256:
 dd32a8fad024141b0af5ef1330dbc7b392cf6406a70fb191bff3cd9a84ce422c 3890 
hippotat_1.2.0.dsc
 136a9c68f34e8ef37b605efd1c9f3f4ebb1c7845d7c962098d9ea4fcb86c3281 119930 
hippotat_1.2.0.tar.gz
Files:
 2c44c3e1e55f3656fe77f1cbb2ce917d 3890 net optional hippotat_1.2.0.dsc
 a0631c8180e51663c7f7e5bb66ff9535 119930 net optional hippotat_1.2.0.tar.gz

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

iQEzBAEBCgAdFiEEVZrkbC1rbTJl58uh4+M5I0i1DTkFAmeftJoACgkQ4+M5I0i1
DTliowgAsgLee7vZhGJ5yAR7q2kLZkTqeI0dHCWH6QSCGL2J4/+T2+59wgqMju9K
7YO7F1JwOqU8mLbVvDibxujhc6d+UXbHYjm9ThX42cCGIDx949fYSuwQnQaREO9H
kw/78pqIz2ElxukqFrRIv0OBxwWq0drJ1PP+doBBNVhMwPoaRYCCSfwYuh8pusGe
lqT2+LRATeiV9m/DiFZJLFa5lvd8WXSC9n8iwlvH7kBbTMt1qBqMc6OcLgOXH4t6
av06BWzVfSRlKZMca5fiBH1NtCrkAZjmEXJbFevL9SWgcfRIr/Ms6j2WnnE3XgzW
sfEDLdGCLhe94d4P7bDgO+zfvrStsQ==
=rrQL
-----END PGP SIGNATURE-----

Attachment: pgpFF9ZRVOGVt.pgp
Description: PGP signature


--- End Message ---

Reply via email to