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

pixi/0.39.3 package update #37639

Closed
wants to merge 1 commit into from

Conversation

octo-sts[bot]
Copy link
Contributor

@octo-sts octo-sts bot commented Dec 19, 2024

@octo-sts octo-sts bot added request-version-update request for a newer version of a package automated pr labels Dec 19, 2024
@octo-sts octo-sts bot mentioned this pull request Dec 19, 2024
Copy link
Contributor Author

octo-sts bot commented Dec 19, 2024

Gen AI suggestions to solve the build error:

Based on the error log and context provided, I'll analyze the build failure and suggest fixes:

• Detected Error: "2024/12/19 14:55:17 INFO Update package: quinn-proto" (followed by implied failure)

• Error Category: Build/Configuration

• Failure Point: The rust/cargobump pipeline step

• Root Cause Analysis:
The cargobump tool is attempting to update dependencies but appears to be failing when processing the quinn-proto package. This is likely due to missing or incorrect cargobump configuration.

• Suggested Fix:

  1. Remove the rust/cargobump pipeline step since it's not strictly necessary for this build
  2. If cargobump is required, add a cargobump configuration:
pipeline:
  - uses: git-checkout
    with:
      repository: https://github.com/prefix-dev/pixi
      expected-commit: c8d1fe96e7da20c0e62d05fb4c44c0f4568d4a79
      tag: v${{package.version}}

  # Remove cargobump step entirely and proceed directly to build
  - name: Configure and build
    runs: |
      cargo auditable build --release
      mkdir -p ${{targets.destdir}}/usr/bin/
      mv target/release/pixi ${{targets.destdir}}/usr/bin/

• Explanation:

  • The cargobump step is typically used to update Rust dependencies, but in this case we're building a specific tagged version
  • Since we're using a specific git tag (v0.39.3), we don't need to bump dependencies
  • Removing this step simplifies the build and maintains version consistency with the upstream release

• Additional Notes:

  • The package is already using cargo-auditable for security tracking
  • The version (0.39.3) matches the latest release from the provided changelog
  • Build dependencies appear correct for a Rust project

• References:

The suggested fix aligns with Wolfi's principles of building from source while maintaining security and version consistency with upstream releases.

@octo-sts octo-sts bot closed this Dec 24, 2024
Copy link
Contributor Author

octo-sts bot commented Dec 24, 2024

superseded by #38302

@octo-sts octo-sts bot deleted the wolfictl-ba791c1b-05a3-43f8-985e-a2fb65b19a01 branch December 25, 2024 00:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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.

1 participant