Add binutils-2.39 configuration - #1
Merged
Merged
Conversation
kaniini
reviewed
Sep 8, 2022
| - name: "binutils-dev" | ||
| description: "binutils development headers" | ||
| pipeline: | ||
| - runs: | |
Contributor
There was a problem hiding this comment.
This can just be - uses: split/dev here.
kaniini
reviewed
Sep 8, 2022
| - uses: chainguard-dev/actions/inky-build-pkg@main | ||
| with: | ||
| package-name: binutils | ||
| empty-workspace: false |
Contributor
There was a problem hiding this comment.
these parameters can be dropped, also the other packages need to be added :)
Contributor
Author
There was a problem hiding this comment.
Duh forgot to commit the last change. Fixed.
Signed-off-by: Adolfo García Veytia (Puerco) <puerco@chainguard.dev>
Signed-off-by: Adolfo García Veytia (Puerco) <puerco@chainguard.dev>
Signed-off-by: Adolfo García Veytia (Puerco) <puerco@chainguard.dev>
Signed-off-by: Adolfo Garcia Veytia (puerco) <puerco@chainguard.dev>
Signed-off-by: Adolfo Garcia Veytia (puerco) <puerco@chainguard.dev>
Signed-off-by: Adolfo Garcia Veytia (puerco) <puerco@chainguard.dev>
Signed-off-by: Adolfo Garcia Veytia (puerco) <puerco@chainguard.dev>
Signed-off-by: Adolfo Garcia Veytia (puerco) <puerco@chainguard.dev>
Signed-off-by: Adolfo Garcia Veytia (puerco) <puerco@chainguard.dev>
Signed-off-by: Adolfo Garcia Veytia (puerco) <puerco@chainguard.dev>
Signed-off-by: Adolfo Garcia Veytia (puerco) <puerco@chainguard.dev>
rawlingsj
added a commit
that referenced
this pull request
Jun 20, 2023
```⚠️ aarch64 | UNAME_MACHINE = aarch64⚠️ aarch64 | UNAME_RELEASE = 5.15.89+⚠️ aarch64 | UNAME_SYSTEM = Linux⚠️ aarch64 | UNAME_VERSION = #1 SMP Sat Mar 18 09:28:00 UTC 2023⚠️ aarch64 | configure: error: cannot guess build type; you must specify one ℹ️ aarch64 | checking build system type... 2023/06/20 12:57:05 ERROR: failed to build package. the build environment has been preserved: ``` https://github.com/wolfi-dev/os/actions/runs/5322650469/jobs/9639610550 Signed-off-by: James Rawlings <jrawlings@chainguard.dev>
afeddersen
added a commit
that referenced
this pull request
Feb 24, 2024
Add 7 Python package tests - #1
xnox
referenced
this pull request
in xnox/os
May 23, 2024
Bump to regenerated SPDX with the following fixes:
- **gcc** Components missing an supplier: libgcc,libstdc++
- **all** add source code external references (pkg:generic or
pkg:github)
The SDK image has up to date wolfictl that will fix the above.
Signed-off-by: Dimitri John Ledkov <dimitri.ledkov@chainguard.dev>
developer-guy
pushed a commit
that referenced
this pull request
May 29, 2024
achraf-mer
added a commit
to achraf-mer/wolfi-os
that referenced
this pull request
Jul 24, 2024
Add an x86_64 pandoc build
This was referenced Oct 30, 2024
This was referenced Dec 30, 2025
This was referenced Jan 7, 2026
This was referenced Jan 16, 2026
octo-sts-3 Bot
pushed a commit
that referenced
this pull request
Jun 3, 2026
* Automated fixes: - stream-transition: version_data/keda.yaml - add keda 2.20 version stream * fix(version-stream): drop stale patches for keda-2.20 The gomod-bump-prometheus.patch fails to apply against v2.20.0's go.mod (Hunk #1 FAILED at 8) because the prometheus replace directives in go.mod already have different versions than the patch expects. The promql-new-parser-api.patch also fails for keda-fips-2.20 because v2.20.0 already uses the new parser.NewParser(parser.Options{}).ParseMetricSelector() API natively. For keda-2.20: remove the patch step and use replaces: in the bump step to handle prometheus replace directives, matching the approach already used by keda-fips-2.19 and keda-fips-2.20. For keda-fips-2.20: remove the patch step that applied promql-new-parser-api.patch since v2.20.0 already has the fix. * fix(version-stream): apply promql-new-parser-api patch in keda-2.20 The keda-2.20 and keda-fips-2.20 builds failed with: pkg/scalers/metrics_api_scaler.go:159:26: undefined: parser.ParseMetricSelector prometheus v0.307+ removed the top-level parser.ParseMetricSelector function, replacing it with a method on the parser instance: parser.NewParser(parser.Options{}).ParseMetricSelector(). The promql-new-parser-api.patch that fixes this call site already existed in the os/keda-2.20/ and enterprise-packages/keda-fips-2.20/ directories but was never applied in the pipeline. Add a `uses: patch` step after git-checkout in both os/keda-2.20.yaml and enterprise-packages/keda-fips-2.20.yaml to apply the patch, matching the approach used in keda-2.19 and keda-fips-2.19. * fix(version-stream): clean up keda-2.20 epoch comment The CVE scan CI failure was a transient infrastructure error (vulnerability database unavailable). Remove the stale epoch comment referencing the 2.19 stream to trigger a new CI run. * fix(version-stream): update keda-fips-2.20 to use go-fips-1.26 The keda-fips-2.20 build was failing because it used go-fips-1.25, but keda 2.20 requires Go 1.26 (the non-FIPS keda-2.20 package already uses go-1.26 successfully). Update all go-fips-1.25 references in enterprise-packages/keda-fips-2.20.yaml to go-fips-1.26 to match the required Go version. * fix(version-stream): restore patch comment and formatting in keda-fips-2.20 Restore the previous comment and formatting for the promql patch step in enterprise-packages/keda-fips-2.20.yaml to match the 2.19 stream: - Restore full GHSA-8rm2-7qqf-34qm reference in the comment - Restore block scalar style for the patches field (`patches: |`) --------- Co-authored-by: version-stream-reconciler <version-stream-reconciler@chainguard.dev> Export: 2d9ab7ed78bba9f612142266ef7277b0e8b0c836
octo-sts-10 Bot
pushed a commit
that referenced
this pull request
Jul 7, 2026
* feat(os): add gss-ntlmssp (ZD9835) Package the GSS-NTLMSSP GSSAPI mechanism (NTLM / MS-NLMP). This is the NTLM authentication mechanism the PowerShell WinRM/WSMan remoting stack relies on for Negotiate/NTLM auth on Linux. The package ships the mechanism plugin (/usr/lib/gssntlmssp/gssntlmssp.so) and registers it with the krb5 GSSAPI mechglue via /etc/gss/mech.d/ntlmssp.conf. Microsoft's powershell Linux image ships gss-ntlmssp; the Chainguard powershell image does not, which blocks NTLM-based WinRM remoting. Functional test compiles a GSSAPI client and asserts the NTLM OID (1.3.6.1.4.1.311.2.2.10) is advertised via gss_indicate_mechs. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * fix(gss-ntlmssp): split development headers into -dev subpackage make install ships a public header (src/gssapi_ntlmssp.h -> /usr/include/gssapi/gssapi_ntlmssp.h via dist_gssapi_HEADERS). Per the c-cpp-package skill rule #1, library packages that install headers must carry a -dev subpackage with `uses: split/dev`. Previously the header shipped in the main runtime package. Verified: header now lands in gss-ntlmssp-dev, main package no longer carries /usr/include. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * fix(gss-ntlmssp): depend on krb5-libs instead of krb5 at runtime The mechanism only needs the GSSAPI mechglue (libgssapi_krb5), which is provided by krb5-libs; the full krb5 package pulls in the KDC/admin tooling that isn't required to load and register the NTLM mech. Trim the runtime dependency to krb5-libs. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * fix(gss-ntlmssp): document why openssl-hardened-dev cannot be used Per the build-hardening skill, evaluated openssl-hardened-dev in place of openssl-dev. It fails: hardened OpenSSL removes the legacy RC4 API (RC4_KEY/RC4_set_key/RC4), but NTLM (MS-NLMP) requires RC4 and MD4 for its sign/seal, so src/crypto.c fails to compile (unknown type name 'RC4_KEY'). Keep openssl-dev and record the reason inline so the choice isn't revisited. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * fix(gss-ntlmssp): drop unnecessary pkgconf build dependency With --without-wbclient there is no PKG_CHECK_MODULES consumer (GSSAPI uses krb5-config, not pkg-config), so pkgconf isn't needed as an explicit build input. Verified: the package still configures, builds, and passes its tests without it. autoconf/automake/libtool remain — they're required by the raw `autoreconf -fiv` step. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com> Export: dcf6a11b89a3b727d54a9dfc5790ee27e7406fd1
octo-sts Bot
pushed a commit
that referenced
this pull request
Jul 18, 2026
* test(pstack): add functional test against live process The previous test pipeline only contained --version/-v invocations and ldd-check, none of which exercise pstack's actual purpose. Add a functional test step that: - Starts a background `sleep 300` process - Runs `pstack` against its PID - Asserts the output contains stack frame lines (#0, #1, ...) - Cleans up the background process This validates that pstack can actually inspect a live process and produce a meaningful symbolic stack trace. * fix(pstack): bump epoch to 1 The epoch-bot CI check flagged os/pstack.yaml for having changes without an epoch bump. Increment epoch from 0 to 1 so the package gets rebuilt. --------- Co-authored-by: skillup <skillup@chainguard.dev> Export: 244c63cc85ad31142887aa72d82ee9cef5f92cb2
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds the build configuration for binutils-2.39
Signed-off-by: Adolfo García Veytia (Puerco) puerco@chainguard.dev