Aiming to reduce the space used in the salsa infrastructure by the
salsa-ci artifacts, and to avoid exceeding the size limit in build jobs,
we (Salsa CI Team) are planning to stop building dbgsym packages: https://salsa.debian.org/salsa-ci-team/pipeline/-/merge_requests/382
We are aware some fellows have pipelines based on salsa-ci's, and we
would like to avoid breaking their stuff, in case something depends on
the dbgsym packages.
The question is: should `DEB_BUILD_OPTIONS=noautodbgsym` be opt-in
or enabled by default?
Hi!
On Wed, 9 Nov 2022 at 01:08, Santiago Ruano Rincón
<santiagorr@riseup.net> wrote:
Aiming to reduce the space used in the salsa infrastructure by the
salsa-ci artifacts, and to avoid exceeding the size limit in build jobs,
we (Salsa CI Team) are planning to stop building dbgsym packages: https://salsa.debian.org/salsa-ci-team/pipeline/-/merge_requests/382
+1
We are aware some fellows have pipelines based on salsa-ci's, and we
would like to avoid breaking their stuff, in case something depends on
the dbgsym packages.
The question is: should `DEB_BUILD_OPTIONS=noautodbgsym` be opt-in
or enabled by default?
The proposal to make it opt-in makes sense to me.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 300 |
Nodes: | 16 (2 / 14) |
Uptime: | 23:20:53 |
Calls: | 6,707 |
Calls today: | 1 |
Files: | 12,239 |
Messages: | 5,352,099 |