FS#52905 - [emacs-nox] "missing dependency: emacs" when building packages that depend on emacs

Attached to Project: Community Packages
Opened by bluephoenix47 (bluephoenix47) - Wednesday, 08 February 2017, 23:20 GMT
Last edited by Jaroslav Lichtblau (Dragonlord) - Tuesday, 25 April 2017, 19:38 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Jaroslav Lichtblau (Dragonlord)
Architecture All
Severity Very Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:

I'm trying to build the AUR package proofgeneral with emacs-nox installed; however, I get Missing Dependency: emacs. emacs-nox does provide emacs, so I don't understand the error. proofgeneral requires emacs>=24.3

Additional info:
* package version(s)
emacs-nox: 25.1
proofgeneral 4.41-1

Steps to reproduce:

Install emacs-nox.
Attempt to build proofgeneral from the AUR.
Witness:
==> Making package: proofgeneral 4.4-1 (Wed Feb 8 18:19:39 EST 2017)
==> Checking runtime dependencies...
==> Missing dependencies:
-> emacs>=24.3
==> Checking buildtime dependencies...
==> ERROR: Could not resolve all dependencies.

==> ERROR: An unknown error has occurred. Exiting...
This task depends upon

Closed by  Jaroslav Lichtblau (Dragonlord)
Tuesday, 25 April 2017, 19:38 GMT
Reason for closing:  Won't implement
Comment by Doug Newgard (Scimmia) - Thursday, 09 February 2017, 03:01 GMT
The version requirement is the problem here. Two solutions: the proofgeneral maintainer can get rid of the useless version requirement, or the emacs-nox maintainer can add the version to the provides.
Comment by bluephoenix47 (bluephoenix47) - Tuesday, 14 February 2017, 17:25 GMT
As maintainer of proofgeneral, I've removed the version requirement. However, this seems like something that the package management system should be able to handle. Is there a reason it is unsupported, or a existing feature request?
Comment by Doug Newgard (Scimmia) - Tuesday, 14 February 2017, 23:29 GMT
Packages don't implicitly provide a version, since there's really no automated way to know what that version should be. Consider -git packages, many of them have a pkgver that doesn't correspond to the version used on a release package. This is then left up to the packager, they can specify it in the provides array as "emacs=<version>".

Loading...