Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

libcap/20071031 package update #40472

Closed
wants to merge 2 commits into from

Conversation

octo-sts[bot]
Copy link
Contributor

@octo-sts octo-sts bot commented Jan 24, 2025

@octo-sts octo-sts bot added request-version-update request for a newer version of a package automated pr labels Jan 24, 2025
Copy link
Contributor Author

octo-sts bot commented Jan 24, 2025

⚠️ EXPERIMENTAL

Please use 👍 or 👎 on this comment to indicate if you agree or disagree with the recommendation.

To provide more detailed feedback please comment on the recommendation prefixed with /ai-verify:

e.g. /ai-verify partially helpful but I also added bash to the build environment

Gen AI suggestions to solve the build error:

Based on the error output, I'll analyze and provide specific fixes:

• Detected Error: [git checkout] execute: git clone --quiet --origin=origin --config=user.name=Melange Build [email protected] --config=advice.detachedHead=false --branch=v1.20071031 --depth=1 git://git.kernel.org/pub/scm/libs/libcap/libcap.git

• Error Category: Version/Git Checkout

• Failure Point: Git checkout step failing to clone with specified tag

• Root Cause Analysis: The git tag format in the melange YAML doesn't match the actual repository tag format. The repository uses a different versioning scheme than what's specified in the checkout command.

• Suggested Fix:

pipeline:
  - uses: git-checkout
    with:
      repository: git://git.kernel.org/pub/scm/libs/libcap/libcap.git
      tag: v2.20071031
      # or alternatively, use ref instead of tag:
      # ref: v2.20071031

• Explanation:

  • The libcap project uses a "v2.x" versioning scheme rather than "v1.x"
  • The current tag format in the YAML (v1.${{package.version}}) is incorrect
  • The version specified would try to checkout "v1.20071031" which doesn't exist
  • Using "v2.20071031" should match the actual tag in the repository

• Additional Notes:

  • Consider updating the package version format to match upstream
  • The expected-commit hash should also be verified after changing the tag
  • Git protocol (git://) is being deprecated in many places, consider using https:// instead

• References:

@octo-sts octo-sts bot added the ai/skip-comment Stop AI from commenting on PR label Jan 24, 2025
@OddBloke OddBloke self-assigned this Jan 24, 2025
@OddBloke OddBloke marked this pull request as draft January 24, 2025 22:44
@OddBloke
Copy link
Member

This version is definitely not the most recent libcap release.

release-monitoring.org is reporting it as the latest version which I've flagged. To avoid automation just reopening this PR, I'm leaving it open as Draft for now.

@OddBloke
Copy link
Member

#40574 fixes our config to ignore those versions, and bumps to the actual latest version.

@debasishbsws
Copy link
Member

closing this as this is fixed in #40574

@octo-sts octo-sts bot deleted the wolfictl-eed3c98f-e2d8-443a-9351-1cd8841fbca9 branch January 28, 2025 00:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ai/skip-comment Stop AI from commenting on PR automated pr request-version-update request for a newer version of a package
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants