Skip to content

Switch to the new Pacman repository #615

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

Merged
merged 3 commits into from
May 22, 2025

Conversation

dscho
Copy link
Member

@dscho dscho commented May 9, 2025

I meant to do this a lot earlier: In February, I started migrating off of the Pacman repository that is hosted in my personal Azure account, to a new Pacman repository that is hosted on GitHub Releases.

With this PR, Git for Windows' SDK is moved over to the new Pacman repository.

Note that the get-sources.sh script is left alone, for now, as it will require substantial work (because it is no longer as easy to find the source package for a given package version; It will require using the GitHub REST API, probably via gh so that the --jq option can be used to filter by the desired asset filename).

@dscho dscho self-assigned this May 9, 2025
dscho added 3 commits May 10, 2025 14:54
For a couple of months now, to precise: since
git-for-windows#595 (Let
`pacman-helper` deploy also to the GitHub repo
`git-for-windows/pacman-repo`), every deployment to Git for Windows'
Pacman repository is mirrored to a new location:
https://github.com/git-for-windows/pacman-repo/

The idea set forth in one of the commits in that PR, 3fca5c7
(pacman-helper quick_add: start transitioning deployments to GitHub,
2025-02-16), is to switch to the new location eventually, avoiding the
dependency on my personal Azure account (where the old location
resides).

I had meant to transition a lot quicker, but procrastinated on this for
such a long time that I forgot. But today is the day!

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
@dscho dscho force-pushed the switch-to-new-pacman-repo branch from 7594487 to f2b7fdd Compare May 10, 2025 12:59
@dscho dscho marked this pull request as ready for review May 10, 2025 12:59
@jeremyd2019
Copy link
Contributor

Note that the get-sources.sh script is left alone, for now, as it will require substantial work (because it is no longer as easy to find the source package for a given package version; It will require using the GitHub REST API, probably via gh so that the --jq option can be used to filter by the desired asset filename).

That sounds like it'll suck - --jq is client-side filtering, so if you don't know what release you're looking for, you may have to try to list all releases & their assets from the server and use jq to find the one you want. That doesn't scale well.

Also, lately I've been seeing HTTP 429 responses from github when attempting to get commits/PRs as .patch files - I hope they're not going to slap a rate limit on the raw files that'll cause issues with this.

@dscho
Copy link
Member Author

dscho commented May 12, 2025

Note that the get-sources.sh script is left alone, for now, as it will require substantial work (because it is no longer as easy to find the source package for a given package version; It will require using the GitHub REST API, probably via gh so that the --jq option can be used to filter by the desired asset filename).

That sounds like it'll suck - --jq is client-side filtering, so if you don't know what release you're looking for, you may have to try to list all releases & their assets from the server and use jq to find the one you want. That doesn't scale well.

Yes, this wouldn't scale well. I was considering caching the results in some way (and tracking that cache in Git).

If only GitHub Pages allowed 302s... But all I can find are <meta>-based redirects...

@jeremyd2019 do you know whether there is a way to let pacman handle <meta>-based redirects? If so, we could even use GitHub Pages to serve the Pacman repository...

@jeremyd2019
Copy link
Contributor

no, I did a quick search and I didn't see any way to get curl to do so, and pacman uses libcurl.

@dscho
Copy link
Member Author

dscho commented May 22, 2025

/deploy git-extra

The i686/x86_64 and the arm64 workflow runs were started.

@dscho dscho merged commit 8cfa119 into git-for-windows:main May 22, 2025
9 checks passed
@dscho dscho deleted the switch-to-new-pacman-repo branch May 22, 2025 09:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants