Hi. Thanks for the report, but I'm confused.
Why do the tests pass in both ci.debian.net and Salsa CI?
Are you saying that those autopkgtest implementations are buggy?
Note: This is a genuine question, and I'm open to "yes" being the
answer, but I would prefer some reference. It could be a kind of
"buggyness" similar to the official buildds installing ca-certificates >without being build-essential, for example.
The set of packages installed by default depends on the autopkgtest backend and can change as different backends serve different purposes (a test of a full desktop or boot loader needs a different test system then just running a command, also see thetest restrictions).
I assume that debci and salsa-ci have make installed by default.
Yes, that's clear, but the question is "why?".
[*] Will probably do this:
Depends: @, make
as the idea is to have something which may be cut & pasted
without changes to other packages doing the same as hello
(I have a few of them).
* Santiago Vila <sanvila@debian.org> [2025-04-16 11:40]:
Yes, that's clear, but the question is "why?".
Because of:
https://sources.debian.org/src/autopkgtest/5.48/setup-commands/setup-testbed/
installs dpkg-dev and that pulls in make. Note that not all autopkgtest backends use setup-testbed.
Also see: https://salsa.debian.org/ci-team/autopkgtest/-/merge_requests/536
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 489 |
Nodes: | 16 (2 / 14) |
Uptime: | 21:08:10 |
Calls: | 9,665 |
Files: | 13,714 |
Messages: | 6,168,097 |