peculiar error: (void-function use-package-hook!)
- Dominant language
- Emacs Lisp
- Stars
- 22.7k
- Forks
- 3.1k
- Avg merge
- 10h 46m
- Merged PRs (30d)
- 4
Description
### I confirm that...
- [X] I have searched the [issue tracker](https://github.com/doomemacs/doomemacs/issues), [documentation](https://docs.doomemacs.org), [FAQ](https://docs.doomemacs.org/-/faq), [Discourse](https://discourse.doomemacs.org), and [Google](https://google.com), in case this issue has already been reported/resolved.
- [X] I have read "[How to Debug Issues](https://doomemacs.org/d/how2debug)", and will use it to provide as much information about this issue as possible.
- [X] The issue can be reproduced on the **latest** available commit of Doom.
- [X] The issue can be reproduced on a stable release of Emacs, such as 27 or 28. *(Doom does not support development builds like 29+ or any version ending in .50 or .9x)*
### Expected behavior
Ability to upgrade doom emacs
### Current behavior
Can't update doom emacs, with an error message of `peculiar error: (void-function use-package-hook!) ` I tried to clean install doom emacs but still getting the same error
### Steps to reproduce
1.
```
~/.emacs.d/bin/doom upgrade
> Preparing to upgrade Doom Emacs and its packages...
x There was an unexpected runtime error
Message: Failed to fetch from upstream
```
2. `cd ~/.emacs.d`
3.
```
$ cd ~/.emacs.d # or wherever you've cloned Doom to
$ git reset --hard a9866e37e45b43785116ef474c8cd6aa9b5185dd
$ git pull origin master
$ doom sync -u
`peculiar error: (void-function use-package-hook!) `
```
### System Information
https://pastebin.com/RWgvYiDQ
Contributor guide
Research direction
Start with the upgrade path at ~/.emacs.d/bin/doom and reproduce the failure using `doom upgrade` and `doom sync -u` after the documented git reset and pull steps. Use the linked system information and the `(void-function use-package-hook!)` error to trace the failing upgrade; done means Doom upgrades or syncs successfully without that error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- emacs-lisp
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100