Your message dated Wed, 1 Jan 2025 14:11:25 +0800
with message-id <[email protected]>
and subject line Re: mdbook: FTBFS: build-dependency not installable: 
librust-pulldown-cmark-escape-0.10+simd-dev
has caused the Debian Bug report #1091061,
regarding mdbook: FTBFS: build-dependency not installable: 
librust-pulldown-cmark-escape-0.10+simd-dev
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.)


-- 
1091061: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1091061
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: mdbook
Version: 0.4.40+ds-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: [email protected]
Usertags: ftbfs-20241222 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> +------------------------------------------------------------------------------+
> | Install package build dependencies                                          
>  |
> +------------------------------------------------------------------------------+
> 
> 
> Setup apt archive
> -----------------
> 
> Merged Build-Depends: debhelper-compat (= 13), cargo, rustc, 
> librust-anyhow-dev (>= 1.0.71-~~), librust-axum-dev (>= 0.6), 
> librust-chrono+clock-dev (>= 0.4.24-~~), librust-clap-dev (>= 4.3.12-~~), 
> librust-clap-complete-dev (>= 4.3.2-~~), librust-env-logger-dev (>= 0.10.0), 
> librust-futures-util-dev (>= 0.3.28-~~), librust-handlebars-dev, 
> librust-ignore-dev (>= 0.4.20-~~), librust-log-dev (>= 0.4.17-~~), 
> librust-memchr-dev (>= 2.5.0-~~), librust-notify-dev (>= 6.1.1-~~), 
> librust-notify-debouncer-mini-dev (>= 0.4.1-~~), librust-once-cell-dev (>= 
> 1.17.1-~~), librust-opener-dev, librust-pathdiff-dev (>= 0.2.1-~~), 
> librust-pulldown-cmark-dev (>= 0.9), librust-regex-dev (>= 1.8.1-~~), 
> librust-serde-dev (>= 1.0.163-~~), librust-serde+derive-dev, 
> librust-serde-json-dev (>= 1.0.96-~~), librust-shlex-dev (>= 1.3.0-~~), 
> librust-tempfile-dev (>= 3.4.0-~~), librust-tokio-dev (>= 1.28.1-~~), 
> librust-tokio+macros-dev, librust-tokio+rt-multi-thread-dev, 
> librust-toml-0.5-dev (>= 0.5.11-~~), librust-topological-sort-dev (>= 
> 0.2.2-~~), librust-walkdir-dev (>= 2.3.3), librust-assert-cmd-dev (>= 
> 2.0.11), librust-predicates-dev (>= 3.0.3), librust-semver-dev (>= 1.0.17), 
> librust-pretty-assertions-dev (>= 1.3.0), libjs-highlight.js, node-clipboard, 
> fonts-font-awesome, fonts-open-sans, fonts-firacode, fonttools, 
> build-essential, fakeroot
> Filtered Build-Depends: debhelper-compat (= 13), cargo, rustc, 
> librust-anyhow-dev (>= 1.0.71-~~), librust-axum-dev (>= 0.6), 
> librust-chrono+clock-dev (>= 0.4.24-~~), librust-clap-dev (>= 4.3.12-~~), 
> librust-clap-complete-dev (>= 4.3.2-~~), librust-env-logger-dev (>= 0.10.0), 
> librust-futures-util-dev (>= 0.3.28-~~), librust-handlebars-dev, 
> librust-ignore-dev (>= 0.4.20-~~), librust-log-dev (>= 0.4.17-~~), 
> librust-memchr-dev (>= 2.5.0-~~), librust-notify-dev (>= 6.1.1-~~), 
> librust-notify-debouncer-mini-dev (>= 0.4.1-~~), librust-once-cell-dev (>= 
> 1.17.1-~~), librust-opener-dev, librust-pathdiff-dev (>= 0.2.1-~~), 
> librust-pulldown-cmark-dev (>= 0.9), librust-regex-dev (>= 1.8.1-~~), 
> librust-serde-dev (>= 1.0.163-~~), librust-serde+derive-dev, 
> librust-serde-json-dev (>= 1.0.96-~~), librust-shlex-dev (>= 1.3.0-~~), 
> librust-tempfile-dev (>= 3.4.0-~~), librust-tokio-dev (>= 1.28.1-~~), 
> librust-tokio+macros-dev, librust-tokio+rt-multi-thread-dev, 
> librust-toml-0.5-dev (>= 0.5.11-~~), librust-topological-sort-dev (>= 
> 0.2.2-~~), librust-walkdir-dev (>= 2.3.3), librust-assert-cmd-dev (>= 
> 2.0.11), librust-predicates-dev (>= 3.0.3), librust-semver-dev (>= 1.0.17), 
> librust-pretty-assertions-dev (>= 1.3.0), libjs-highlight.js, node-clipboard, 
> fonts-font-awesome, fonts-open-sans, fonts-firacode, fonttools, 
> build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<<RESOLVERDIR>>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<<RESOLVERDIR>>/apt_archive ./ InRelease
> Get:2 copy:/<<RESOLVERDIR>>/apt_archive ./ Release [615 B]
> Ign:3 copy:/<<RESOLVERDIR>>/apt_archive ./ Release.gpg
> Get:4 copy:/<<RESOLVERDIR>>/apt_archive ./ Sources [1882 B]
> Get:5 copy:/<<RESOLVERDIR>>/apt_archive ./ Packages [1912 B]
> Fetched 4409 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> ----------------------------------------------------
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  librust-pulldown-cmark-dev : Depends: 
> librust-pulldown-cmark-escape-0.10+simd-dev but it is not installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2024/12/22/mdbook_0.4.40+ds-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20241222;[email protected]
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20241222&[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 ---
On 01/01/2025 01:46, Santiago Vila wrote:
> reopen 1091061
> thanks
> 
> Blair Noctis wrote:
>> it's due to pulldown-cmark{,-escape} being out of sync, not mdbook itself.
> 
> The error is like this:
> 
> error: failed to select a version for the requirement `pulldown-cmark = 
> "^0.9"`
> candidate versions found which didn't match: 0.10.3
> 
> So you are relying on an *older* version which is no longer available.
> 
> I don't see how this could be not a bug in mdbook.

(follow-up)
> My apologies. I didn't read the original bug report from Lucas Nussbaum.
> I detected that this package FTBFS, there was a closed FTBFS bug, so I 
> reopened.
> 
> When Lucas tried to build it, the dependencies could not be installed.
> 
> Now they can, but the build still fails, this time with a different
> error (which I quoted). In case it helps; I've put a full build log here:
> 
> https://people.debian.org/~sanvila/build-logs/202412/

Hi Santiago,

When Lucas filed this bug, pulldown-cmark{,-escape} were indeed out of sync: 
new version of the main thing started to depend on the "simd" feature of 
-escape, but this feature was provided by a newer version of -escape, which was 
only later uploaded, causing FTBFS for the main thing for a while.

I closed this bug in that while, thinking 1. it's caused by the FTBFS (not 
really, now revisiting the situation) which should untangle itself after a 
while; 2. binary packages of mdBook were already built and in the archive, they 
are programs so don't affect other packages; 3. mdBook had already been updated 
in the packaging repo, only waiting for the soon to be upgrade of another 
dependency (actually happened yesterday). In hindsight, these points probably 
weren't enough.

The updated version was uploaded a few moments ago. It builds fine (except on 
s390x, due to other reasons), so I'm now rightfully closing it.

-- 
Sdrager,
Blair Noctis

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


--- End Message ---

Reply via email to