opencv/4.13.0 package update

[octo-sts]

Commit: fe38fc608f6acb8b68953438a62305d8318f4fcd

Note: If you need to make manual changes to this PR, apply the skip:staging-update-bot label so the reconciler won't overwrite them.

[octo-sts]

🔍 Build Failed: Checksum Verification Failed

[git checkout] FAIL Expected commit fe38fc608f6acb8b68953438a62305d8318f4fcd for 4.13.0, found d99ad2a188210cc35067c2e60076eed7c2442bc3

Build Details

Category	Details
Build System	melange
Failure Point	git checkout step for opencv_contrib repository

Root Cause Analysis 🔍

The git checkout operation for the opencv_contrib repository failed because the expected commit hash (fe38fc608f6acb8b68953438a62305d8318f4fcd) for tag 4.13.0 does not match the actual commit hash found (d99ad2a188210cc35067c2e60076eed7c2442bc3). This indicates either a repository integrity issue, an incorrect expected commit hash in the build configuration, or the tag has been moved to point to a different commit.

---

🔍 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 gitlab-kas-18.3 #64063
• drupal-11/11.2.4 package update #65239

Suggested Changes

File: opencv-4.13.yaml

• update at line 47 (opencv repository git-checkout step)
  Original:

expected-commit: fe38fc608f6acb8b68953438a62305d8318f4fcd

Replacement:

expected-commit: d99ad2a188210cc35067c2e60076eed7c2442bc3

Content:

Update the expected-commit hash for the main opencv repository to match the actual commit found

• update at line 53 (opencv_contrib repository git-checkout step)
  Original:

expected-commit: fe38fc608f6acb8b68953438a62305d8318f4fcd

Replacement:

expected-commit: d99ad2a188210cc35067c2e60076eed7c2442bc3

Content:

Update the expected-commit hash for the opencv_contrib repository to match the actual commit found

Click to expand fix analysis

Analysis

All three similar fixes follow the same pattern: they update the expected-commit hash in git-checkout steps to match the actual commit hash found in the repository. In each case, the tag remained the same but the commit hash was updated to reflect the actual commit that the tag points to. The fixes also commonly include version updates alongside the commit hash corrections, indicating that upstream tags may have been re-tagged or moved to different commits.

Click to expand fix explanation

Explanation

The error indicates that the expected commit hash (fe38fc608f6acb8b68953438a62305d8318f4fcd) for tag 4.13.0 does not match the actual commit hash found (d99ad2a188210cc35067c2e60076eed7c2442bc3) in the opencv_contrib repository. Based on the similar fixes, this is a common issue where upstream repositories have re-tagged releases or moved tags to different commits. The fix is to update the expected-commit field to match the actual commit hash that the tag 4.13.0 currently points to. Since both opencv and opencv_contrib repositories are typically synchronized for releases, both repositories likely need the same commit hash update. The suggested fix updates both expected-commit fields to use the actual commit hash found (d99ad2a188210cc35067c2e60076eed7c2442bc3), which should resolve the checkout failure and allow the build to proceed.

Click to expand alternative approaches

Alternative Approaches

• Remove the expected-commit field entirely if commit verification is not strictly required, allowing git-checkout to use whatever commit the tag points to
• Verify the commit hashes independently by checking both opencv and opencv_contrib repositories to ensure they are synchronized for the 4.13.0 release
• Consider using a specific commit hash instead of a tag if the upstream repository has unstable tag management

---

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