Bug#1086450: src:pandoc-filter-diagram: unsatisfied build dependency in testing: librust-base64-0.21+default-dev

[Paul Gevers]

Source: pandoc-filter-diagram
Version: 0.2.1-5
Severity: serious
Tags: sid trixie
User: debian-***@lists.debian.org
Usertags: edos-uninstallable

Dear maintainer(s),

Dose [1] is reporting a build issue with your package, it's missing a
build dependency. Obviously your build dependencies shouldn't be
removed from testing, but unfortunately there are multiple scenarios
where that can happen nevertheless. To uphold our social contract,
Debian requires that packages can be rebuild from source in the suite
we are shipping them, so currently this is a serious issue with your
package in testing.

Can you please investigate the situation and figure out how to resolve
it? Regularly, if the build dependency is available in unstable,
helping the maintainer of your Build-Depends to enable migration to
testing is a great way to solve the issue. If your build dependency is
gone from unstable and testing, you'll have to fix the build process
in some other way.

Paul

Note: this bug report was sent after some quick manual checks using a
template. Please reach out to me if you believe I made a mistake in my
process.

[1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html

[Debian Bug Tracking System]

Your message dated Thu, 16 Jan 2025 16:01:23 +0000
with message-id <E1tYSJ9-00ED4C-***@fasolo.debian.org>
and subject line Bug#1086450: fixed in pandoc-filter-diagram 1.2.0-1
has caused the Debian Bug report #1086450,
regarding src:pandoc-filter-diagram: unsatisfied build dependency in testing: librust-base64-0.21+default-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 ***@bugs.debian.org
immediately.)