On Sun, 29 Mar 2026 13:18:36 +0200 Matthias Klose <[email protected]> wrote:
Package: src:deb-build-artifact-gather
Version: 0.1

People on #debian-reproducible pointed me to this package ...

Some questions:

- the docs/*.md files should be part of the binary package.


Will be in the next version.

- it is unclear for me, how artifacts of successful and
   unsuccessful builds are collected, and if there is a
   difference


Now documented in https://salsa.debian.org/debian/deb-build-artifact-gather#what-is-collected-and-how-to-control-what-is-collected

- how are artifacts collected that are not part of the
   package builds, like preprocessed source of compiler
   errors, or dump files for OpenJDK crashes?
   These two use cases showing up as /tmp/cc* and /tmp/hs_*


There are built-in rules for that kind of thing. Please see the built-in rule list at:
https://salsa.debian.org/debian/deb-build-artifact-gather/-/blob/main/src/deb_build_artifact_gather/rules.py?ref_type=heads#L103

Patches to expand it welcome. Based on your description, I would expect there is at least two changes you would like to see (including the `test-summary.log` below).

- X-Build-Time-Aux-Artifacts lines: Are these optional,
   e.g. ignored when there are no matches?
   Architecture specific logs should be considered.


Now documented at https://salsa.debian.org/debian/deb-build-artifact-gather/-/blob/main/docs/INTERFACE-PACKAGE-MAINTAINER.md?ref_type=heads#what-do-you-as-a-maintainer-need-to-do

- X-Build-Time-Aux-Artifacts: what's the equivalent for
   find -name '*.log'? or do these have to be specified
   separately?


This is currently not supported. There are some architectural and chroot provider related decisions to sort out first before I am ready to commit to more complex pattern.

- X-Build-Time-Aux-Artifacts: are there exclusion patterns
   for logs?


No, and I am not expecting to support it either.

- X-Build-Time-Aux-Artifacts: Are complete directory
   names allowed as an artifact?
   Use-case is getting the complete failing test in
   a testsuite


Currently not supported. Might be something I can support without getting into the chroot provider issue.

- I assume that debhelper's config.log dumping will be
   replaced by this, or at least that config.log files
   will appear in the artifacts.

   test-summary.log files are currently not dumped (autotools
   specific?). How are these added to the artifacts without
   having every package maintainer specifying these themself?


These are covered by built-in rules at:
https://salsa.debian.org/debian/deb-build-artifact-gather/-/blob/main/src/deb_build_artifact_gather/rules.py?ref_type=heads#L103

Best regards,
Niels

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

Reply via email to