gitlab-cng-18.0/18.0.1 package update

[octo-sts]

[octo-sts]

⛓️ Build Failed: Constraint Not Satisfied

Error: Expected shell-tag: 14.41.0 but got: 14.42.0

Build Details

Category	Details
Build System	melange
Failure Point	Verify all the vars tags are up to date with the upstream

Root Cause Analysis 🔍

The build is checking for consistency between expected and actual tag values. It expected the shell-tag to be 14.41.0 but found 14.42.0 instead. This is likely a version mismatch check that ensures the build configuration matches expected upstream version tags. The build fails because the detected version (14.42.0) is newer than the expected version (14.41.0) in the configuration.

---

🔍 Build failure fix suggestions

Found similar build failures that have been fixed in the past and analyzed them to suggest a fix:

Similar PRs with fixes

• gitlab-cng-17.8/17.8.4 package update #43843
• gitlab-runner-17.11/17.11.1 package update #52449
• chromium/132.0.6834.159 package update #40723

Suggested Changes

File: gitlab-cng-18.0.yaml

• replace at line 18 (vars section, shell-tag and shell-commit)
  Original:

  # Shell tags: https://gitlab.com/gitlab-org/gitlab-shell/-/tags
  shell-commit: 8b00540589eeeefc1774c92260286b7da1a112d1
  shell-tag: 14.41.0

Replacement:

  # Shell tags: https://gitlab.com/gitlab-org/gitlab-shell/-/tags
  shell-commit: 5957a2c703b4a5a89f2cd2cfd04ef957e0f23a4c
  shell-tag: 14.42.0

Click to expand fix analysis

Analysis

After analyzing the similar fixed build failures, I've identified a common pattern: version mismatches between the declared values in the package YAML file and the actual upstream values. In all three examples, the fix involved updating the expected version/tag/commit in the YAML file to match the actual upstream version. The current build failure shows a shell-tag mismatch where the build expected 14.41.0 but found 14.42.0. This indicates that GitLab has released a newer version of gitlab-shell (14.42.0) that doesn't match the version declared in our YAML file (14.41.0).

Click to expand fix explanation

Explanation

The build failure indicates that the shell-tag value in the vars section of the YAML file (14.41.0) doesn't match the actual version specified in the upstream CNG's variables.yml file (14.42.0). The error occurs in the "Verify all the vars tags are up to date with the upstream" check, which compares the values in the YAML file with those extracted from the CNG repository's variables.yml.

The fix is to update the shell-tag value in the vars section from 14.41.0 to 14.42.0, which aligns with what's in the upstream repository. I've also updated the shell-commit value to match the HEAD commit of the v14.42.0 tag in the gitlab-shell repository (found by checking the tag at https://gitlab.com/gitlab-org/gitlab-shell/-/tags/v14.42.0).

This follows the same pattern as the fixes in the examples provided, where the solution was to update the version/tag in the YAML file to match what's expected by the upstream. Specifically, in fix example #0, the exporter-tag was updated from 15.0.0 to 15.2.0 to resolve a similar version mismatch error.

This approach adheres to Wolfi's guiding principle of keeping packages up to date with upstream releases. The fix allows the build to proceed with the latest version of the gitlab-shell component.

Click to expand alternative approaches

Alternative Approaches

• We could modify the verification script to be more flexible with version checks, but this would go against Wolfi's principles of keeping packages up to date with upstream releases.
• Another approach would be to pin the CNG commit to an earlier version that still uses gitlab-shell 14.41.0, but this would result in using an older package version, which is not desirable for security and feature reasons.

---

Was this comment helpful? Please use 👍 or 👎 reactions on this comment.