Skip to content
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

Could not find package X in recipe repositories #2802

Closed
flyingns opened this issue Mar 31, 2020 · 12 comments
Closed

Could not find package X in recipe repositories #2802

flyingns opened this issue Mar 31, 2020 · 12 comments
Labels
faq Comes up frequently, and is likely answered in the FAQ (or should be) is:bug Something isn't working as intended re:packages Pertains to package & dependency management re:straight To do with straight; our package manager status:resolved Issue was addressed internally

Comments

@flyingns
Copy link

flyingns commented Mar 31, 2020

After updating doom with doom upgrade, or its packages with doom update, I get errors like these:

Package error: (error Could not find package org-roam in recipe repositories: (org-elpa melpa gnu-elpa-mirror emacsmirror-mirror))
Package error: (error Could not find package company-org-roam in recipe repositories: (org-elpa melpa gnu-elpa-mirror emacsmirror-mirror))

And/or errors like these:

Cannot open load file: No such file or directory, org-roam
Cannot open load file: No such file or directory, org-superstar
@flyingns flyingns added the is:bug Something isn't working as intended label Mar 31, 2020
@jadestrong

This comment has been minimized.

@hlissner
Copy link
Member

hlissner commented Mar 31, 2020

It's a known issue where your local melpa repo isn't being updated, so straight (our package manager) can't find new packages (like org-roam or org-superstar).

I'm working on a fix, but in the meantime you'll need to update your local melpa repo manually:

EDIT: This has been fixed in recent commits of Doom, but users coming from an older version may yet encounter this the first time they run doom upgrade, so this fix is still applicable to you:

# Update MELPA
cd ~/.emacs.d/.local/straight/repos/melpa
git pull

# Clear straight's cache
rm -f ~/.emacs.d/.local/straight/build-cache.el
doom sync

@hlissner hlissner added module:lang/org Pertains to Doom's :lang org module re:packages Pertains to package & dependency management re:straight To do with straight; our package manager workaround Contains a workaround, but no acceptable or final solution (yet) status:pending-fix labels Mar 31, 2020
@hlissner hlissner changed the title Package error: (error Could not find package org-roam in recipe repositories... Package error: (error Could not find package X in recipe repositories... Apr 19, 2020
@hlissner hlissner added the faq Comes up frequently, and is likely answered in the FAQ (or should be) label Apr 19, 2020
@hlissner hlissner pinned this issue Apr 19, 2020
@hlissner hlissner changed the title Package error: (error Could not find package X in recipe repositories... Could not find package X in recipe repositories Apr 19, 2020
@hlissner hlissner removed the module:lang/org Pertains to Doom's :lang org module label Apr 19, 2020
@jcf

This comment has been minimized.

@hlissner
Copy link
Member

hlissner commented Apr 19, 2020

For posterity and to avoid confusion, @jcf's issue is unrelated to this one (see #2937, which was resolved separately).

@glencjones
Copy link

glencjones commented May 7, 2020

I had the same issue for shellcheck discovered it was also in my config (package.el), removed it and message has now gone...

@hlissner hlissner added status:resolved Issue was addressed internally and removed workaround Contains a workaround, but no acceptable or final solution (yet) status:pending-fix labels May 15, 2020
@hlissner
Copy link
Member

hlissner commented May 15, 2020

As of 0e851ac bin/doom will update your recipe repos before installing/updating packages, which should resolve this issue. Let me know if that isn't the case and I'll reopen it. Thanks for bringing it to my attention!

@hlissner hlissner unpinned this issue May 15, 2020
@kawaiier
Copy link

kawaiier commented May 15, 2020

Had the same problem. Just tried doom upgrade/update and got this

Type: error
  Message:
    error
  Data:
    "Could not find package org-superstar in recipe repositories: (org-elpa melpa gnu-elpa-mirror emacsmirror-mirror)"

UPDATE: Worked after following these steps

@nikolauska
Copy link

nikolauska commented May 15, 2020

@kawaiier Had the same issue org-superstar. Updating melpa manually as mentioned above fixed the issue

@harrisj
Copy link

harrisj commented May 16, 2020

I have done the fix as mentioned above, but it always breaks again the next time I run doom upgrade

x There was an unexpected error:ate...
  Type: doom-package-error
  Message:
    Error with packages
  Data:
    "org-superstar"
    (error "Failed to run \"git\"; see buffer *straight-process*")
  Straight output:
    fatal: ambiguous argument 'HEAD': unknown revision or path not in the working tree.
    Use '--' to separate paths from revisions, like this:
    'git <command> [<revision>...] -- [<file>...]'
    HEAD

@VitalyAnkh
Copy link
Contributor

VitalyAnkh commented May 31, 2020

@harrisj I have the same issue 😅

@hlissner
Copy link
Member

hlissner commented May 31, 2020

@harrisj @VitalyAnkh Try

git -C ~/.emacs.d pull
git -C ~/.emacs.d/.local/straight/repos/melpa pull
rm -rf ~/.emacs.d/.local/straight/repos/org-superstar
rm -f ~/.emacs.d/.local/straight/build-cache.el
doom sync

@samwhitlock
Copy link
Contributor

samwhitlock commented Aug 9, 2020

In case anyone happens upon this for org superstar in particular, @hlissner changed superstar to require (org +pretty) in init.el a few days ago (due to speed issues).

If the above package refreshing stuff doesn't work, you may need to add this flag.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 5, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
faq Comes up frequently, and is likely answered in the FAQ (or should be) is:bug Something isn't working as intended re:packages Pertains to package & dependency management re:straight To do with straight; our package manager status:resolved Issue was addressed internally
Projects
None yet
Development

No branches or pull requests

10 participants