-
Notifications
You must be signed in to change notification settings - Fork 8
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
gitup: load_file: problem reading /usr/src/contrib/llvm-project/libcxx/include/__string: Input/output error #94
Comments
|
When I clone 525ecfdad5 and then pull fc952ac221, it goes through without any issue. When I clone a previous commit (such as 3b5e5ce87b) then pull 525ecfdad5 and then pull fc952ac221, I get a different list of files to repair than what you're seeing and the repair never takes so this problem seems more widespread when reverting to earlier commits. This one might take me a while to fix. |
|
If it helps …
From #94 (comment):
Despite that, it still exists as a directory file: |
|
I just committed a potential fix for this issue. When you have a chance, could you please retrace your steps and see if the problem persists? Thank you! |
This comment was marked as resolved.
This comment was marked as resolved.
|
If you cd into cloned directory and then execute |
|
Sorry for taking so long.
I think I retraced correctly, the problem is no longer reproducible. Thanks!
Command history, condensed: |
|
No worries! |
Briefly:
/usr/srcmight have been at 13.2.0 before the commands belowgitup release -t release/13.1.0included removal of the/usr/src/contrib/llvm-project/libcxx/include/__stringdirectory and its contents (lines 14035 and 14036 of the attached transcript), with an invitation to rerun gitupgitup release -t release/13.1.0failed with what might be a file-related error:error, __string.txt
Edge case, I suspect.
The text was updated successfully, but these errors were encountered: