Dimitri John Ledkov
Dimitri John Ledkov
Hm, the difference is that you are writting xff instead of x00. Let me see if that makes a difference or not.
> Is there any particular reason why we are using those keys (repository, keyring) on these tests/packages anyways? Aren't these set implicitly by our Makefile normally? the nested apko test...
> I warn against this until internal issue https://github.com/chainguard-dev/internal-dev/issues/24527 is resolved to ensure these two package repositories are equivalent. Since the tests passed, this change is unaffected by the above....
Attempting to add the above, results in inability to initiate RSA, or numbers are significantly different between the two providers, or certificate verification fails.
Lol impressive => imprecise
Seems like an apko bug: - https://github.com/chainguard-dev/apko/issues/1543
This bug is the reason why `gcc-12` package uses `no-provides` which intern is buggy w.r.t. turning of depends, see https://github.com/chainguard-dev/melange/issues/1366
py3-seaborn => shouldn't really vendor in numpy, and should really depend on matching py3-numpy. Also our libquadmath currently is not correctly shipped by gcc as a separate package, as that...
There are two types of linking that is supported right now: - inside the FIPS module - outside of the FIPS module And the symbols leak. If one certifies jitterentropy...
I like that both options will be in active use in production.