FS#24296 - [namcap] detect java-environment dependency intead of the correct java-runtime

Attached to Project: Arch Linux
Opened by Eric Belanger (Snowman) - Sunday, 15 May 2011, 23:55 GMT
Last edited by Doug Newgard (Scimmia) - Monday, 19 December 2016, 01:48 GMT
Task Type Bug Report
Category Arch Projects
Status Closed
Assigned To Rémy Oudompheng (remyoudompheng)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 13
Private No

Details

Description:

When running namcap on glsof, it prints the following incorrect errors:

glsof E: Dependency java-environment detected and not included (found class files usr/share/java/glsof/queries.jar, usr/share/java/glsof/filemonitor.jar)
glsof W: Dependency included and not needed ('java-runtime')

The jar files are run with 'java -jar file.jar' which is provided by java-runtime.
This task depends upon

Closed by  Doug Newgard (Scimmia)
Monday, 19 December 2016, 01:48 GMT
Reason for closing:  Fixed
Comment by Rémy Oudompheng (remyoudompheng) - Monday, 16 May 2011, 05:34 GMT
openjdk6 provides both, so namcap should get the ability to detect that it satisfies both.
Comment by Eric Belanger (Snowman) - Monday, 16 May 2011, 09:48 GMT
to be clear, it is java-runtime (not openjdk6) that is listed in the package's depends array.
Comment by Alexander F. Rødseth (xyproto) - Sunday, 18 November 2012, 22:58 GMT
When running namcap on a freshly built glsof-2.1.0-1-x86_64.pkg.tar.xz, I get:

glsof W: No ELF files and not an "any" package
glsof E: Dependency java-environment detected and not included (found class files usr/share/java/glsof/filemonitor.jar, usr/share/java/glsof/queries.jar)
glsof W: Dependency included and not needed ('java-runtime')
glsof W: Dependency included and not needed ('lsof')

Confirmed.
Comment by Matthias Dienstbier (fs4000) - Wednesday, 17 April 2013, 23:46 GMT
Patch is untested.
Comment by Jelle van der Waa (jelly) - Wednesday, 30 October 2013, 11:08 GMT
Please submit the patch to arch-projects@archlinux.org ( the mailing list )
Comment by Marcel Korpel (Marcel-) - Wednesday, 30 April 2014, 20:59 GMT
But there *are* packages that depend on java-environment, like eclipse. Won't namcap complain the other way around when this patch is applied? That is, on eclipse it will complain that java-environment is included but not needed and that java-runtime should be included.

BTW, the patch is submitted to the mailing list, as far as I can see in the archive.
Comment by Marcel Korpel (Marcel-) - Wednesday, 30 April 2014, 21:00 GMT
Pressed 'add comment' to soon: I meant "isn't submitted", in my last sentence.
Comment by Matthias Dienstbier (fs4000) - Saturday, 03 May 2014, 17:12 GMT
I think a dependency on java-environment cannot be detected. If a package depends on java-environment, it will also depend on java-runtime.

Yes, the patch is not on the mailinglist, yet. I created it just to point out, what I think needs to be changed. This issue is absolutely trivial.
Comment by Norbert Pfeiler (npfeiler) - Thursday, 05 May 2016, 14:46 GMT
still an issue
Comment by Kyle Keen (keenerd) - Thursday, 05 May 2016, 18:11 GMT
Fixed in commit 01c89e0.
Comment by Norbert Pfeiler (npfeiler) - Tuesday, 17 May 2016, 22:20 GMT
@keenerd is this an unpushed commit?
Comment by Kyle Keen (keenerd) - Thursday, 19 May 2016, 04:13 GMT
Sorry, I had pushed that to the old projects.archlinux server instead of the new git.archlinux server. Should be visible now as commit 4424a23c.

Loading...