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

Version 0.0.0 not accepted for requirement (any) #107

Open
dradetsky opened this issue Nov 3, 2024 · 1 comment
Open

Version 0.0.0 not accepted for requirement (any) #107

dradetsky opened this issue Nov 3, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@dradetsky
Copy link

Describe the bug

I created a package and since eldev insisted it have a version, I added

;; Version: 0.0.0

I then went to run my tests with eldev test which triggered

Dependency ‘ignore-mouse’ version (any) is required, but at most 0.0.0 is available

And, uhh, that's not what "any" means, buddy.

Anyhow, I was able to fix this by setting the version to 0.0.1. So this is not hard to work around, but also maybe a sign that something is wrong. And in any case, if this is a requirement eldev wants to enforce for whatever reason, it's not clear that it actually attempting to enforce that requirement instead of just suffering from a bug. And also, it's not a requirement I care for.

Steps to reproduce

Create a file like

;;; replicate.el --- replicate  -*- lexical-binding: t -*-

;; Version: 0.0.0

;;; replicate.el ends here

and an Eldev like

(eldev-use-package-archive 'melpa)

And run eldev test in that directory.

Expected behavior

Complaint about inability to find any test files or something like that.

Actual behavior

Dependency ‘replicate’ version (any) is required, but at most 0.0.0 is available

Environment

  • Eldev: 1.10.3
  • Emacs: 29.4
  • OS: Arch Linux
@doublep
Copy link
Collaborator

doublep commented Nov 3, 2024

eldev insisted it have a version

Eldev requires it's a package from Emacs point of view. It's rather Emacs [package system] that insists on some version.

The rest is indeed a bug. I committed a fix; it will be released later, with 1.11, as it is a minor issue with a trivial workaround.

@doublep doublep added the bug Something isn't working label Nov 3, 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