Adding VersionStream for haproxy-3.3

[octo-sts]

No description provided.

[octo-sts]

🔄 Build Failed: Git Checkout Error

Expected commit 170436929ac78cfc4d1a43b3340535e1ac4d00d8 for v3.3.0, found 7832fb21fe2dd11ce44e996d8e86802731b871b2

Build Details

Category	Details
Build System	melange
Failure Point	git-checkout step during source code retrieval

Root Cause Analysis 🔍

Git tag v3.3.0 points to a different commit than expected in the build configuration. The build script expects commit 170436929ac78cfc4d1a43b3340535e1ac4d00d8 but the actual tag points to commit 7832fb21fe2dd11ce44e996d8e86802731b871b2. This indicates either the upstream repository has been updated or there's a mismatch in the build configuration's expected commit hash.

---

🔍 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

• Adding VersionStream for gitaly-18.3 #64066

Suggested Changes

File: haproxy-3.3.yaml

• modification at line 45 (pipeline git-checkout step)
  Original:

expected-commit: 170436929ac78cfc4d1a43b3340535e1ac4d00d8

Replacement:

expected-commit: 7832fb21fe2dd11ce44e996d8e86802731b871b2

Content:

Update the expected commit hash to match the actual commit that tag v3.3.0 points to in the upstream repository

Click to expand fix analysis

Analysis

All three similar fixes follow the same pattern: when a git tag points to a different commit than expected, the solution is to update the expected-commit field in the git-checkout step to match the actual commit hash that the tag points to. In each case, the build configuration was updated to use the correct commit hash (7832fb21fe2dd11ce44e996d8e86802731b871b2 in our case) rather than the previously expected one. This indicates that upstream repositories occasionally update tags or the initial commit hash was incorrect.

Click to expand fix explanation

Explanation

This fix addresses the root cause by updating the expected-commit field to match the actual commit hash that the v3.3.0 tag points to in the upstream HAProxy repository. The error occurs because the build system performs a verification step to ensure the tag points to the expected commit for security and reproducibility purposes. When upstream repositories update tags (either due to corrections, security fixes, or repository maintenance), the commit hash changes and must be updated in the build configuration. By changing the expected-commit from 170436929ac78cfc4d1a43b3340535e1ac4d00d8 to 7832fb21fe2dd11ce44e996d8e86802731b871b2, the build will succeed as it will match the actual commit that v3.3.0 currently points to.

Click to expand alternative approaches

Alternative Approaches

• Remove the expected-commit field entirely if commit verification is not strictly required for this package, though this reduces build security
• Investigate if there's a different tag or commit that should be used if the current v3.3.0 tag is not the intended release
• Check if upstream has released a corrected v3.3.0 tag and wait for repository synchronization if this is a temporary issue

---

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