Skip to content
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

installing git-sdk-1.0.1-x64 fails due to download package error #367

Closed
max630 opened this issue Sep 9, 2015 · 2 comments
Closed

installing git-sdk-1.0.1-x64 fails due to download package error #367

max630 opened this issue Sep 9, 2015 · 2 comments

Comments

@max630
Copy link

max630 commented Sep 9, 2015

I tried twice, looks like persistent issue

the error messages are:

error: failed retrieving file 'mingw-w64-x86_64-crt-git-5.0.0.4531.49c7046-1-any.pkg.tar.xz' from repo.msys2.org : Operation too slow. Less than 1 bytes/sec transferred the last 10 seconds
error: failed retrieving file 'mingw-w64-x86_64-crt-git-5.0.0.4531.49c7046-1-any.pkg.tar.xz' from downloads.sourceforge.net : Operation too slow. Less than 1 bytes/sec transferred the last 10 seconds
error: failed retrieving file 'mingw-w64-x86_64-crt-git-5.0.0.4531.49c7046-1-any.pkg.tar.xz' from www2.futureware.at : The requested URL returned error: 404
warning: failed to retrieve some files
error: failed to commit transaction (unexpected error)
Errors occurred, no packages were upgraded.
Could not install the remaining packages

@max630
Copy link
Author

max630 commented Sep 9, 2015

worked around by manually downloading and copying the file into /var/cache/pacman/pkg

@nalla
Copy link

nalla commented Sep 9, 2015

Thanks for the report. For future reference here is the link to the official msys2 repository to manual download failed packages.

@nalla nalla closed this as completed Sep 9, 2015
jeffhostetler pushed a commit to jeffhostetler/git that referenced this issue Jul 2, 2021
Replaces git-for-windows#367, which used the upstream commits directly. This instead includes a merge commit onto `vfs-2.32.0` so we can move forward even if the upstream version is modified.

This integrates the sparse-index with `git status`. There is a LOT of code here, and much of it makes future changes (git-for-windows#361 and git-for-windows#364) much simpler than they would be otherwise.

This merges into `features/sparse-index` which is intended to be released as an experimental release. The goal of reviewing this PR is to find "good enough for a limited release to dogfooders" and not the same scrutiny of upstream.

In particular, I am currently looking for an issue with directory/file conflicts at the sparse-checkout boundary. They don't reveal themselves until `git checkout`, and only in very rare cases that won't affect our dogfooders.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants