Your message dated Fri, 26 Sep 2025 15:10:39 +0200
with message-id <[email protected]>
and subject line Re: [Pkg-rust-maintainers] Bug#1116365: librust-font-kit-dev:
impossible to install: depend on missing
librust-yeslogic-fontconfig-sys-5+default-dev
has caused the Debian Bug report #1116365,
regarding librust-font-kit-dev: impossible to install: depend on missing
librust-yeslogic-fontconfig-sys-5+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 [email protected]
immediately.)
--
1116365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1116365
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: librust-font-kit-dev
Version: 0.14.2-2
Severity: grave
X-Debbugs-Cc: [email protected], [email protected]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Crate librust-font-kit-dev version 0.14.2-2 is impossible to install in
unstable, currently: It depends on
librust-yeslogic-fontconfig-sys-5+default-dev which is unavailable.
Cc'ing Rust team list and [email protected] as an example of why I
request to please upload known broken packages to experimental, not to
unstable:
A newer rust-font-kit 0.14.3-1 was released earlier today, directly to
unstable despite it changes to tighten a build-dependency from
librust-pathfinder-simd-0.5+default-dev,
to
librust-pathfinder-simd-0.5+default-dev (>= 0.5.5-~~),
librust-pathfinder-simd-0.5+default-dev version 0.5.5 is not in unstable
so is what I call "known broken". That package is currently at version
0.5.2, last updated in November 2023.
To clarify, since I cannot read minds I do not claim that anyone in
parcilular knew what they were doing here, only that it was known
systematically - i.e. that it *would be* known to anyone actually
looking. And in case the former sounds like I have low expectations on
whether or not the Rust team is running blindfolded then no, I don't
know if they knew or could know - when I looked now, the git-tracked
source for the package apparently does not include a debian/control file
so it *seems* possible that they are "blindfolded" by way of their
choice of tooling. But let me emphasize that I am *not* pointing fingers
at their tooling here, only at the choice of uploading to unstable what
*could* be known as breakage by way of a simple debdiff before upload.
- Jonas
-----BEGIN PGP SIGNATURE-----
wsG7BAEBCgBvBYJo1mXkCRAsfDFGwaABIUcUAAAAAAAeACBzYWx0QG5vdGF0aW9u
cy5zZXF1b2lhLXBncC5vcmcoxDa4wq34EYOi91N/hZrkTld1lM4nad6A1s496FU8
/xYhBJ/j6cNmkaaf9TzGhCx8MUbBoAEhAABWmBAArY50U1UvDgA9WseSGHWvQG5Y
K2jPZjnY/ohERs3VtzEMG6++WJX9/69kGU8cKXzo/7SQxQmbuZ/Ub3SzYPwkjU4r
HikTBDMYiiLL6dYHXdCa42BRn6bDeE31jB48efqAXYowac9+m7wWTXp+alc18RWz
Ec1L7EF6SEke0Liv+y9tCZIXwg78hzxXwrjBa5f7gLtNthXk2ky6usyVrceeLx+W
JqYsKvRjX+w1oUkjokWXVJTnmbNXp1SQRykAg+IL+CjGjMWUnVK+zVcxtAfuZous
7vwcQBaKkOfpiZbqtbpDVzIBrJPxbtTy+13WSuZszaGezTseZ9cFfhFyziYL+Fk1
zsMSUH1alLJ9bmAjNLepOSK+57Au3eQG4fUGK6wkM2JTwmSfFmV3+TRjfcHDWueF
OasiLI1q9N/ZR0bS4CxlWibYLo4d4FcKHlr5ax2Wx44DEUNDGkaz49SQKErD5Ymc
p4vHloXZUK6NEw8IPhzJAzyug69VlZ+bByKZo3iXRIY4L7Pyx33g/+iIALzpsfv3
FidMmgOu7PDcC4g379b8sQQn31jGYtUBkP0inPRC8pXLa9yZ/7BM/Jro3FQuChVr
8LOp07GS2XUV2Z8i+qDDEY4/FEl/wLl4v2J/UmLp1n28CcvKsnMTwyfiQwTquASc
bsc8qf44Eu/OpdbIn1s=
=hStZ
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
Version: 0.14.3-1
On 26/09/25 12:07, Jonas Smedegaard wrote:
Package: librust-font-kit-dev
Version: 0.14.2-2
Severity: grave
X-Debbugs-Cc:[email protected],[email protected]
Crate librust-font-kit-dev version 0.14.2-2 is impossible to install in
unstable, currently: It depends on
librust-yeslogic-fontconfig-sys-5+default-dev which is unavailable.
Cc'ing Rust team list [email protected] as an example of why I
request to please upload known broken packages to experimental, not to
unstable:
A newer rust-font-kit 0.14.3-1 was released earlier today, directly to
unstable despite it changes to tighten a build-dependency from
librust-pathfinder-simd-0.5+default-dev,
to
librust-pathfinder-simd-0.5+default-dev (>= 0.5.5-~~),
librust-pathfinder-simd-0.5+default-dev version 0.5.5 is not in unstable
so is what I call "known broken". That package is currently at version
0.5.2, last updated in November 2023.
To clarify, since I cannot read minds I do not claim that anyone in
parcilular knew what they were doing here, only that it was known
systematically - i.e. that it*would be* known to anyone actually
looking. And in case the former sounds like I have low expectations on
whether or not the Rust team is running blindfolded then no, I don't
know if they knew or could know - when I looked now, the git-tracked
source for the package apparently does not include a debian/control file
so it*seems* possible that they are "blindfolded" by way of their
choice of tooling. But let me emphasize that I am*not* pointing fingers
at their tooling here, only at the choice of uploading to unstable what
*could* be known as breakage by way of a simple debdiff before upload.
- Jonas
_______________________________________________
Pkg-rust-maintainers mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-rust-
maintainers
This is beyond ridiculous. Someone just failed to dput
rust-pathfinder-simd 0.5.5-1 (marked as released in git yesterday),
making rust-font-kit 0.14.3-1 B-D uninstallable and librust-font-kit-dev
0.14.2-2 uninstallable. That's been fixed now.
This marks the 3rd ordinary bug you needlessly cc to d-devel. I'll stop
answering d-devel until something interesting comes up.
Best.
--- End Message ---
