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

wrong-type-argument package-desc error when using extended dependency format #106

Open
suhail-singh opened this issue Oct 31, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@suhail-singh
Copy link

suhail-singh commented Oct 31, 2024

Describe the bug

A clear and concise description of what the bug is.

Steps to reproduce

  1. Take a project that uses eldev and has melpa archive enabled.
  2. Add (eldev-add-extra-dependencies 'build '(:package magit)) to Eldev file.
  3. Run eldev -dt dependencies build.
  4. See error.

Expected behavior

No exception should be raised. Per the documentation of "Extended dependency
format", eldev-add-extra-dependencies should accept a plist.

Actual behavior

...
Debugger entered--Lisp error: (wrong-type-argument package-desc magit)
  signal(wrong-type-argument (package-desc magit))
  eldev-message-version(magit t)
  eldev-dependencies("build")
  apply(eldev-dependencies "build")
  eldev--execute-command(("dependencies" "build"))
  eldev-cli(("-dt" "dependencies" "build"))
...

Environment

  • Eldev: 1.10.3
  • Emacs: 29.4
  • OS: Linux

Additional context

N/A.

@doublep
Copy link
Collaborator

doublep commented Nov 3, 2024

A problem is that eldev-add-extra-dependencies predates the extended dependency format. Moreover, it accepts lists as dependencies, but for a different meaning. I guess I need to fix this anyway, but it would be useful to understand what exactly you are trying to achieve. Is this only a neatpick (as (:package magit) should be the same as just magit), or were you planning to use some functionality supported only by the extended format?

@suhail-singh
Copy link
Author

Is this only a neatpick (as (:package magit) should be the same as just
magit), or were you planning to use some functionality supported only by the
extended format?

The latter. I wanted to specify the archive for a package that's available via
multiple archives. The example I gave was a minimal one intended to reproduce
the error and not the one I encountered the error first on.

doublep added a commit that referenced this issue Nov 5, 2024
… dependency format is used for additional dependencies (issue #106).
@doublep
Copy link
Collaborator

doublep commented Nov 5, 2024

Fix will be released with 1.11. Apparently, the bug was only with commands dependencies and dependency-tree, otherwise the extended format worked.

@doublep doublep added the bug Something isn't working label Nov 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants