Package installation error is ignored despite --debug-init

[bcc32]

If package-installation fails (at least from quelpa recipes, I didn't test other packages), the error is not caught by --debug-init and instead startup proceeds as normal. This seems bad, --debug-init should start the debugger when the package installation encounters an error rather than later down the line when the package fails to load.

For example, I deliberately uninstalled and broke my local copy of evil-evilified-state, then tried starting emacs --debug-init. The error appears in *Messages* but does not trigger the debugger, which only gets tripped when a later step attempts to load the package and fails.

(Spacemacs) --> installing package: evil-evilified-state@spacemacs-bootstrap... [1/1]
Fetcher: file
Source: nil

(Spacemacs) Error: 
An error occurred while installing evil-evilified-state (error: (error Single file evil-evilified-state-2.el does not match package name evil-evilified-state))

Similarly, when use-package fails to find a package to load it does not trigger the debugger despite --debug-init.

[bcc32]

Doing some digging, it appears that errors raised inside condition-case-unless-debug (such as inside configuration-layer//install-package) do not trip the debugger with --debug-init. I don't happen to have an Emacs 29 install handy right now so I'm not immediately sure if this is a regression in Emacs 30.1. Seems surprising.