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

pacman with msys2 often gets stuck on never-ending "checking available disk space" #67

Open
pps83 opened this issue Jan 23, 2025 · 0 comments

Comments

@pps83
Copy link

pps83 commented Jan 23, 2025

I just did pacman -Suy and it asked to continue:

Total Download Size:    446.63 MiB
Total Installed Size:  2860.72 MiB
Net Upgrade Size:       -39.32 MiB

:: Proceed with installation? [Y/n] y
:: Retrieving packages...

I have 350GB of freespace. It's been calculating available frees pace for 5-10 mins already:

(164/164) checking for file conflicts                        [###############################] 100%
(136/169) checking available disk space                      [########################-------]  80%
(153/169) checking available disk space                      [###########################----]  90%
(167/169) checking available disk space                      [##############################-]  98%
(168/169) checking available disk space                      [##############################-]  99%
(169/169) checking available disk space                      [###############################] 100%
:: Running pre-transaction hooks...
(1/1) Removing old entries from the info directory file...
:: Processing package changes...
(1/5) removing mingw-w64-x86_64-libtre-git                   [###############################] 100%
(2/5) removing mingw-w64-i686-libtre-git                     [###############################] 100%
(3/5) removing mingw-w64-i686-libgccjit                      [###############################] 100%
(4/5) removing mingw-w64-i686-gcc-ada                        [-------------------------------]   0%

(it just happened that it completed while I was writing the issue report).

Can it be fixed someway not to calculate or bypass that check?

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

No branches or pull requests

1 participant