On 9/17/25 06:04, Benjamin Kaduk wrote:
On Tue, Sep 16, 2025 at 08:51:09PM -0700, Benjamin Kaduk wrote:

A question, though: do the module-assistant-autopkgtest tests use the
default Testsuite: of autopkgtest?  Right now I already have an entry as
autopkgtest-pkg-dkms and it's unclear to me whether the default type that
dpkg adds will be appended to an already-extant Testsuite: stanza, or I
need to add it manually.

dpkg takes care of that

Also, I'm confused by the "Depends: module-assistant-autopkgtest" stanza
(the test command does use a script of that name but it seems to be
provided by the module-assistant package, and Google is not showing
anything to suggest that there's a package named
"module-assistant-autopkgtest" specifically.

module-assistant-autopkgtest is a virtual package provided by module-assistant (since the module-assistant-autopkgtest was added).
So the autopkgtest depends on the virtual package rather than
module-assistant (>= some-version-I-am-too-lazy-to-lookup)

Similarly, "Depends: linux-doc" seems very surprising.  Why would we need
the kernel documentation to build and test a module?  Was that intended to
be a different package?

Since the linux-headers-* packages change their names with every new version and on every architecture, we cannot easily add a dependency on them for the autopkgtest. On the other hand linux-doc is one of the few packages built from src:linux that does not have a version number embedded in its name and that is available on all architectures under this name. It is therefore used for triggering autopkgtests whenever src:linux gets uploaded. The script then looks at the version of the installed linux-doc to select the matching linux-headers-* packages it needs to install for the test. There are usually linux-headers-* packages in sid from older versions that have not yet been decrufted and that should not be used for the test. The dkms amd module-assistant autopkgtests are special in the sense that they install their real dependencies while running (and therefore need to be needs-root, breaks-testbed) and not via dependencies.


Andreas

Reply via email to