* [email protected] <[email protected]> [2026-01-27 23:55]:
Just to clarify, in the salsa-ci rdep job we only enable aspcud + the buildd like criteria when the target build is for experimental (that is, when building against experimental). For the normal case we use the default apt resolver, so this is indeed the exceptional path.
Great, thanks for pointing that out.
Regarding ratt, we use it mainly because it generates the full sbuild command lines for rebuilding reverse build-dependencies, and it wraps dose-ceve so the reverse build-dep closure is computed correctly (architecture context, filtering, etc) If there is a preferred Debian approach, I'd appreciate a pointer and I can check whether it fits the salsa-ci rdep job.
Debian uses ben: https://release.debian.org/transitions/index.htmlNote that sbuild can compute deb-src lines itself and you can pass a directory to --extra-package. ben even generates dependency levels so you could pass build results downstream. In essence it should be enough to pass sbuild --build-dir=/path/to/build --extra-package=/path/to/build --dist$DIST $PACKAGE.
signature.asc
Description: PGP signature
