On Sun, Nov 08, 2026 at 10:34:59AM +1300, Andrew McMillan wrote: > [...] > I really want to be able to do a full build of packages in the NEW > queue so we can provide *reliable* early signals of this sort of thing > as well as of whether they are repeatable builds, but until we have > something like that I don't fully trust these signals about whether the > build will or will not work - too often I've had a reply from the > maintainer saying this is fine, usually because of some obscure > debhelper behaviour the LLM didn't reason through correctly.
Indeed, being able to build the package would be the ideal scenario, so if you can't do that yet and rely only on the LLM being "psychic" (so to speak :-), I understand that you keep it conservative. > > Note: I make archive rebuilds from time to time with nocheck build > > profile, and report what I find here: > > > > https://bugs.debian.org/cgi-bin/[email protected];tag=ftbfs-nocheck-profile > > > > so if we can avoid adding new packages early to the "set of affected > > packages", the better. > > I've added an issue for this: > > https://salsa.debian.org/dfsg-team/dfsg-omp-review/-/work_items/27 > > and it would be helpful if you can add any more useful clarifying > information there that might help me explain to the LLM exactly how to > differentiate this issue better. Hmm, it looks like you would like some kind of "heuristic" to guess if the build "might" work or not without doing any real build. I don't know any magic trick for that. However, if you need a reference page to explain the nocheck build profile to maintainers, you can use this one which I started: https://wiki.debian.org/qa.debian.org/FTBFS/nocheck Thanks. -- Pkg-javascript-devel mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
