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

shadow/4.17.4 package update #47471

Merged
merged 2 commits into from
Mar 20, 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:

Based on the build log, here's my analysis:

• Detected Error: libtool: warning: '../libsubid/libsubid.la' has not been installed in '/usr/lib'

• Error Category: Configuration/Dependency

• Failure Point: During make install when installing getsubids binary

• Root Cause Analysis: There appears to be an issue with the installation order and library linking of libsubid. The library isn't being properly installed before its dependencies try to use it.

• Suggested Fix: Add library installation directory to pipeline:

pipeline:
  - uses: autoconf/configure
    with:
      opts: |
        --libdir=/usr/lib \
        [existing options...]

• Explanation: The libsubid library needs to be properly installed in the system library path before other components can link against it. The libdir configure option ensures the library gets installed to the correct location.

• Additional Notes:

  • This is a common issue with libtool-based builds when library installation paths aren't explicitly specified
  • The warning doesn't fail the build but could cause runtime issues
  • Proper library path specification helps ensure clean installation and linking

• References:

Let me know if you need any clarification or have additional questions!

@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 19, 2025
wolfi-bot and others added 2 commits March 20, 2025 12:30

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.
This avoids tripping the usrmerge linter.
@OddBloke OddBloke force-pushed the wolfictl-0ba1dfd5-7458-4505-8a95-73317d210670 branch from 0a48770 to 4e527ef Compare March 20, 2025 16:30
@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 16:41
@OddBloke OddBloke enabled auto-merge March 20, 2025 16:41
@OddBloke OddBloke merged commit 86a2e65 into main Mar 20, 2025
21 checks passed
@OddBloke OddBloke deleted the wolfictl-0ba1dfd5-7458-4505-8a95-73317d210670 branch March 20, 2025 17:55
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