Skip to content

ci(debusine): include qli workspace for DKMS build-dependencies - #56

Open
Bjordis Collaku (bjordiscollaku) wants to merge 1 commit into
mainfrom
feat/debusine-extra-build-dep-workspaces
Open

ci(debusine): include qli workspace for DKMS build-dependencies#56
Bjordis Collaku (bjordiscollaku) wants to merge 1 commit into
mainfrom
feat/debusine-extra-build-dep-workspaces

Conversation

@bjordiscollaku

@bjordiscollaku Bjordis Collaku (bjordiscollaku) commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

Context

PR #54 introduces DKMS module integration on the packaging branch (qcom/debian/latest) and adds kgsl-dkms (>= 1.0.2) to Build-Depends.

The Debian build path on main runs through Debusine (build-kernel-debusine.yml), where build-dependency resolution is scoped to configured repositories/workspaces.

kgsl-dkms is published in Debusine workspace qli, so the build submission path must explicitly include that workspace for dependency resolution.

Decision

Thread Debusine workspace dependency context from the caller workflow into debusine-action/lib/build by setting, in the Build in Debusine step:

  • EXTRA_BUILD_DEP_WORKSPACES=qli
  • DEBUSINE_USER=${{ secrets.DEBUSINE_USER }}

lib/build already supports EXTRA_BUILD_DEP_WORKSPACES and requires DEBUSINE_USER for its current extra_repositories compatibility flow.

Scope

One targeted workflow change:

  • .github/workflows/build-kernel-debusine.yml
  • Build in Debusine env block only

No packaging metadata, kernel build scripts, or Ubuntu workflow behavior changed.

Why This Unblocks DKMS

Without this change, the Debusine Debian pipeline cannot discover kgsl-dkms from qli, which blocks PR #54’s DKMS-enabled build path at dependency resolution time.

With this change, the Debusine submission includes qli as an additional build-dependency source, enabling the Debian pipeline to resolve DKMS prerequisites introduced by PR #54.

Validation Evidence

Validation run:

Observed in Build in Debusine / Build (Debusine) logs:

  • DEBUSINE_USER is present
  • EXTRA_BUILD_DEP_WORKSPACES: qli is present
  • extra_repositories contains //workspace=qli/trixie@debian:suite and is expanded to explicit repository fields

The run later terminated because Debusine work request 14057 ended status=aborted during remote execution. That abort occurred after this PR’s wiring was applied and exercised.

Relationship to PR #54

Both are required to make the Debian Debusine DKMS build path functional end-to-end.

@github-advanced-security

Copy link
Copy Markdown

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

The Debian Debusine build path now needs kgsl-dkms as a build dependency
(via PR #54 against qcom/debian/latest). The package is published in the
qli Debusine workspace, so the build step must expose qli as an extra
build-dependency source when invoking debusine-action/lib/build.

Set EXTRA_BUILD_DEP_WORKSPACES=qli in Build in Debusine and pass
DEBUSINE_USER, which lib/build currently requires to apply its
extra_repositories compatibility workaround.

Signed-off-by: Bjordis Collaku <bcollaku@qti.qualcomm.com>
@bjordiscollaku Bjordis Collaku (bjordiscollaku) changed the title ci(debusine): wire qli as extra build-dep workspace for DKMS builds ci(debusine): include qli workspace for DKMS build-dependencies Jul 8, 2026
@bjordiscollaku
Bjordis Collaku (bjordiscollaku) force-pushed the feat/debusine-extra-build-dep-workspaces branch from 4f590fd to 18f6efe Compare July 8, 2026 22:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants