loosen zlib-pin to major level (1/N; May 2024) #739
Merged
Conversation
This file contains 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
|
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
30 tasks
|
If we restrict to a single month (though we'd have to do that several times obviously), we'd get down to about ~4500 artefacts: |
isuruf
reviewed
May 23, 2024
h-vetinari
changed the title
beckermr
approved these changes
May 24, 2024
It's trivial to script the timestamp-logic, but I'm not sure it's worth setting up a separate migrator. I don't mind opening a few PRs, I mainly need to know what kind of cadence we want to aim for, how far back we want to go, and what the plan is for dealing with possible stragglers. But we can discuss that in conda-forge/conda-forge-pinning-feedstock#5959 |
|
FWIW, April has around 4000 artefacts that are affected |
|
We should let the CDN sync once or twice between PRs in terms of cadence. For this specific issue, even though I really don't like it, I think we should patch everything. :/ |
How often does the CDN sync happen? |
|
The CDN sync runs on a loop and the delay time between when a package uploads and is in the repodata is the sync time. |
|
So we should be able to do a month every ~4 hours? |
|
Sure yeah. |
kkraus14
approved these changes
May 28, 2024
|
Alright, let's get this effort started. Once we've patched the first 2-3 months of repodata, we should start seeing environments that only rely on recent builds to pull in zlib 1.3, so I'm planning to slow down a bit around there to see if we run into troubles, and then pick up speed if we don't see any issues occur. |
This was referenced May 28, 2024
h-vetinari
changed the title
This was referenced May 31, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Restricted to monthly cadence after discussion in conda-forge/conda-forge-pinning-feedstock#5959
Previously: