Hi, On Sat, 10 May 2025 13:35:02 +0000 Debian FTP Masters <ftpmaster@ftp- master.debian.org> wrote:
rust-graphene-sys (0.20.7-2) unstable; urgency=medium . * Depend on libgraphene for regeneration (Closes: #1104982)
I'm slightly confused about the solution. I'm now seeing libgraphene-1.0-dev twice, once in the Build-Depends (which always needs to be satisfied), and once with the !nocheck annotation in Build-Depends-Arch (which only needs to be installed during the build-arch, binary-arch, build and binary targets). I'm *assuming* that second line is ignored in all circumstances, so it's unnecessary at least, but if due to bugs the merging happens differently than I'd expect, the dependency can still be gone building with nocheck enabled. It might not be worth that risk.
I'm assuming that newly added separation between Build-Depends and Build-Depends-Arch is to reduce the required installed dependencies during the clean target which is useful during building the source?
Pauldiff -Nru rust-graphene-sys-0.20.7/debian/control rust-graphene-sys-0.20.7/debian/control --- rust-graphene-sys-0.20.7/debian/control 2025-01-11 17:22:33.000000000 +0000 +++ rust-graphene-sys-0.20.7/debian/control 2025-05-10 13:04:55.000000000 +0000
@@ -3,17 +3,18 @@ Priority: optional Build-Depends: debhelper-compat (= 13), dh-sequence-cargo, - cargo:native <!nocheck>, + gir-rust-code-generator (>= 0.20), + libgirepository1.0-dev, + xmlstarlet, + libgraphene-1.0-dev +Build-Depends-Arch: cargo:native <!nocheck>, rustc:native (>= 1.70) <!nocheck>, libstd-rust-dev <!nocheck>, librust-glib-sys-0.20+default-dev (>= 0.20.6-~~) <!nocheck>, librust-libc-0.2+default-dev <!nocheck>, librust-pkg-config-0.3+default-dev <!nocheck>, librust-system-deps-7+default-dev <!nocheck>, - libgraphene-1.0-dev <!nocheck>, - gir-rust-code-generator (>= 0.20), - libgirepository1.0-dev, - xmlstarlet + libgraphene-1.0-dev <!nocheck>
OpenPGP_signature.asc
Description: OpenPGP digital signature
