Skip to content

qdrant/1.14.1 package update #54173

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

octo-sts[bot]
Copy link
Contributor

@octo-sts octo-sts bot commented May 23, 2025

@octo-sts octo-sts bot added request-version-update request for a newer version of a package automated pr P1 This label indicates our scanning found High, Medium or Low CVEs for these packages. labels May 23, 2025
Copy link
Contributor Author

octo-sts bot commented May 23, 2025

⛓️ Build Failed: Constraint Not Satisfied

rustc 1.86.0 is not supported by the following package: [email protected] requires rustc 1.87

Build Details

Category Details
Build System Cargo (Rust)
Failure Point Rust package dependency resolution

Root Cause Analysis 🔍

The build is using Rust compiler version 1.86.0, but the Qdrant package version 1.14.1 specifically requires Rust compiler version 1.87 or newer. This version constraint cannot be satisfied with the current environment.


🔍 Build failure fix suggestions

Found similar build failures that have been fixed in the past and analyzed them to suggest a fix:

Suggested Changes

File: package:

name: qdrant
version: "1.14.1"

  • modification at line environment.contents.packages (environment.contents.packages)
    Original:
      - rust

Replacement:

      - rust>=1.87.0

Content:

Update the rust package dependency to specify minimum version 1.87.0
Click to expand fix analysis

Analysis

The build failure shows a version compatibility issue between the Rust compiler (rustc 1.86.0) and the qdrant package (v1.14.1), which requires rustc 1.87. This is a common pattern in Rust-based build failures where package requirements specify a minimum toolchain version. Although no similar fixed issues were provided, the standard approach is to update the Rust compiler version in the build environment to satisfy the package's requirements.

Click to expand fix explanation

Explanation

The error message clearly indicates that qdrant 1.14.1 requires Rust 1.87, but the current build environment is using Rust 1.86.0. The package dependency constraint "rustc 1.87" is not being satisfied.

In Wolfi's package build system, dependencies are installed via the Alpine package manager (apk) at build time. By modifying the rust package dependency in the Melange YAML to specify a minimum version of 1.87.0, we ensure that the build environment will use a Rust compiler version that satisfies qdrant's requirements.

This is the most direct solution to address the UNSATISFIED_CONSTRAINT error. The error is explicit that qdrant 1.14.1 requires rustc 1.87, and our fix directly addresses this by ensuring the appropriate Rust version is used during the build process. This approach aligns with Wolfi's guiding principles of keeping packages up to date with upstream releases and using the latest versions where possible.

Click to expand alternative approaches

Alternative Approaches

  • If rust 1.87.0 is not yet available in the package repository, an alternative would be to temporarily downgrade the qdrant version to one compatible with rust 1.86.0, but this would be less preferred given Wolfi's principle of keeping packages up to date.
  • Another approach could be to add a custom build step that downloads and installs rustc 1.87.0 directly from upstream sources, but this would be more complex and less maintainable than using the package manager.
  • If a newer version of qdrant is available that still works with rust 1.86.0, upgrading the package version could be considered, though the error suggests newer versions likely require newer Rust versions.

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

@octo-sts octo-sts bot added the ai/skip-comment Stop AI from commenting on PR label May 23, 2025
@AmberArcadia AmberArcadia self-assigned this May 23, 2025
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 P1 This label indicates our scanning found High, Medium or Low CVEs for these packages. request-version-update request for a newer version of a package
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants