patch packages affected by missing run_exports from petsc, fenics-libdolfinx rattler-build bug #971
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.
Bug in rattler-build means that any package with multiple run_exports in a single list will only produce packages with the last item in
run_exports
: prefix-dev/rattler-build#1468Probably not too many packages affected, as most have a single run_export. But petsc and fenics-libdolfinx have multiple run_exports fields, which have been producing downstream packages with inadequate pinning. This patches those downstream packages, built with the bad packages in
host
. Only packages published in a relatively short window are affected, so this usestimestamp_gt
because the conditions aren't perfect and would pull in some very old packages that are not affected, but all the matched packages within the time window get correct patches.This is fixed by PRs:
Checklist
pre-commit run -a
and ensured all files pass the linting checks.python show_diff.py
and posted the output as part of the PR.diff