-
Notifications
You must be signed in to change notification settings - Fork 99
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
onefetch release 7 update fails #2545
Comments
**Summary** Due to a packaging accident, the completions were installed as directories, and when an attempt was made to correct this, eopkg didn't know how to handle turning a directory into a file. We'll revisit this at a later date. Ref #2545 Signed-off-by: Evan Maddock <[email protected]>
I think this is because the completions were accidentally installed as directories, and eopkg doesn't know how to turn a directory into a file (curse lack of atomic updates). For now, the completions have been removed so we can focus on fixing the |
Can we consider this solved? |
The original issue has been solved. The underlying eopkg issue is still there of course, but that's better handled as a ticket in the eopkg repository directly. I'll create one there. |
Please confirm there isn't an existing open bug report
Summary
Running
sudo eopkg up
with a previous release ofonefetch
installed fails on the update toversion 2.21.0, release 7
with the following errorSteps to reproduce
onefetch
versionsudo eopkg it https://packages.getsol.us/shannon/o/onefetch/onefetch-2.20.0-5-1-x86_64.eopkg
sudo eopkg up
Expected result
onefetch package gets upgraded to
version 2.21.0, release 7
Actual result
sudo eopkg upgrade
fails with above error messageEnvironment
Repo
Unstable
Desktop Environment
Budgie
System details
Other comments
The corresponding packaging change: 7a9ab97
The path mentioned in the error message was previously a directory containing the shell completions, while with this commit the path now corresponds to the shell completions file itself
The text was updated successfully, but these errors were encountered: