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

shadowsocks-rust/1.23.0 package update #47440

Merged
merged 2 commits into from
Mar 21, 2025

Conversation

octo-sts[bot]
Copy link
Contributor

@octo-sts octo-sts bot commented Mar 19, 2025

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

octo-sts bot commented Mar 19, 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:

• Detected Error: "fatal: bad object dccb3c4c4a4c407f18cfe2e1057d0e39acb9a2d2"

• Error Category: Version/Git Configuration

• Failure Point: Git cherry-pick operation during the git-checkout step

• Root Cause Analysis: The cherry-pick is failing because the specified commit hash dccb3c4c4a4c407f18cfe2e1057d0e39acb9a2d2 cannot be found in the repository. This could be because:

  1. The commit hash is incorrect
  2. The commit exists in a different branch/fork
  3. The commit has been rebased or force-pushed away

• Suggested Fix:

  1. Verify the correct commit hash from the upstream repository
  2. Update the melange.yaml to remove or update the cherry-pick section:
pipeline:
  - uses: git-checkout
    with:
      repository: https://github.com/shadowsocks/shadowsocks-rust
      tag: v${{package.version}}
      expected-commit: 4beddbeb200ad7f2194479f95867c3fd447dc69c
      # Either remove cherry-picks or update with correct commit hash

• Explanation: The error indicates a Git operation failure when trying to apply patches from specific commits. Since this is a release version (v1.23.0), the cherry-picks may no longer be necessary as the changes should already be included in the release tag.

• Additional Notes:

  • Cherry-picks are typically used for backporting fixes, but since this is a new release (1.23.0), the changes may already be included
  • The changelog shows multiple dependency updates and fixes that may have made these cherry-picks obsolete
  • Consider checking if the Hickory bump changes are already part of v1.23.0

• References:

@octo-sts octo-sts bot added the ai/skip-comment Stop AI from commenting on PR label Mar 19, 2025
@OddBloke OddBloke self-assigned this Mar 20, 2025
wolfi-bot and others added 2 commits March 20, 2025 18:27

Unverified

The signing certificate or its chain could not be verified.
Signed-off-by: wolfi-bot <121097084+wolfi-bot@users.noreply.github.com>

Unverified

The signing certificate or its chain could not be verified.
@OddBloke OddBloke force-pushed the wolfictl-00ecb343-8abd-4992-a763-3ae2823f4913 branch from 6df28f4 to 4e68be3 Compare March 20, 2025 22:29
@octo-sts octo-sts bot added the bincapz/pass bincapz/pass Bincapz (aka. malcontent) scan didn't detect any CRITICALs on the scanned packages. label Mar 20, 2025
@OddBloke OddBloke requested a review from a team March 20, 2025 22:46
@OddBloke OddBloke enabled auto-merge March 20, 2025 22:46
@OddBloke OddBloke merged commit ebb3bae into main Mar 21, 2025
21 checks passed
@OddBloke OddBloke deleted the wolfictl-00ecb343-8abd-4992-a763-3ae2823f4913 branch March 21, 2025 13:29
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 bincapz/pass bincapz/pass Bincapz (aka. malcontent) scan didn't detect any CRITICALs on the scanned packages. manual/review-needed request-version-update request for a newer version of a package
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants