xbmc / xbmc/inputstream.ffmpegdirect
How to find problem mirrors for Windows msys2 packages when building PRs
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 101
- Forks
- 56
- PR merge metrics
- No merged PRs in 30d
Description
If windows packages are failing a lot it is likely it's a kodi mirror involving the msys2 packages.
First add a temp commit adding the verbose flag -v to the curl command in both these files:
depends/windows/mingw/03-use-curl.patchdepends/windowsstore/mingw/03-use-curl.patch
Then go the log and search for Transfer returned error. The mirror listed prior to this will be the problem mirror. Check a few more to be sure.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with depends/windows/mingw/03-use-curl.patch and depends/windowsstore/mingw/03-use-curl.patch, then inspect the Windows package build log for “Transfer returned error.” Verify the mirror identified by the preceding log entry against several failures; done means the problematic mirror can be identified reliably from the documented procedure.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100