Closed CGenie closed 4 years ago
Yep, happened a couple of times for me too and a git reset
to the parent commit was the fix.
EDIT: Just realized that #1721 already exists, so I'll mark this down as a duplicate.
Thank you for your hard work on the whole project!
Przemek
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Monday, October 7, 2019 11:18 PM, Henrik Lissner notifications@github.com wrote:
Folks have reported several issues with doom upgrade.
I am aware of these and am working on a solution, and have decided to use this issue as a catch-all for them. For the time being, here are the common issues and their respective workarounds:
doom upgrade hangs indefinitely while updating some packages
You'll need to delete said package(s) manually from ~/.emacs.d/.local/straight/{build,repos}/, then run doom refresh -f.
"No upstream configured for branch" errors
Example:
There was an unexpected error: error (error) Wrong type argument: listp, "There were errors:
- company-anaconda: ((error Failed to run \"git\"; see buffer straight-process) fatal: no upstream configured for branch 'master')
- anaconda-mode: ((error Failed to run \"git\"; see buffer straight-process) fatal: no upstream configured for branch 'master')"
Same solution as above: delete the listed packages manually.
Threads time out frequently.
Example:
. . ! A thread has timed out. The following packages were skipped: melpa, gnu-elpa-mirror, emacsmirror-mirror, straight, bind-key, async, dotenv-mode, auto-minor-mode, all-the-icons, hide-mode-line, highlight-numbers, rainbow-delimiters, restart-emacs, better-jumper, dtrt-indent, helpful, ns-auto-titlebar, pcre2el, smartparens, so-long, osx-clipboard, undo-tree, ws-butler, projectile . 11% . 22% . 33% . 44%
For this, you'll need to either:
- Increase the timeout (from the default 45s): doom upgrade -t 160 or
- Delete the packages listed in the "thread has timed out" message from ~/.emacs.d/.local/straight/{build,repos}/, then run doom refresh -f.
Doom throws "file-missing" errors at startup after doom upgrade
This means the autoloads files weren't generated correctly. doom refresh -f should address this. If not, run doom rebuild -f.
I'll keep you posted.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
Describe the feature When module git branch (eg.
org-ql
) has a hard reset and new commits on top of it,doom update
just hangs. I need to manually go to$HOME/.emacs.d/.local/straight/repos/<module>
, dogit reset --hard HEAD~50
, and thendoom update
works fine.Least doom should do is report such an issue and proceed with upgrading of next module.
System information