FS#34213 - [namcap] voltdb can not check correctly for java-runtime and gcc-libs

Attached to Project: Arch Linux
Opened by Daniel YC Lin (dlin) - Friday, 08 March 2013, 08:50 GMT
Last edited by Jelle van der Waa (jelly) - Friday, 11 August 2023, 15:51 GMT
Task Type Bug Report
Category Arch Projects
Status Closed
Assigned To Rémy Oudompheng (remyoudompheng)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
When check voltdb in aur, it occurs
voltdb W: Referenced library 'libjvm.so' is an uninstalled dependency
voltdb W: Referenced library 'libjava.so' is an uninstalled dependency
voltdb W: Dependency included and not needed ('java-runtime')
voltdb W: Dependency gcc-libs included but already satisfied

Additional info:

* package version(s)
voltdb 3.2.4
jre 7.9-1 (which provide java-runtime and contains libjvm.so,libjava.so)
* config and/or log files etc.


Steps to reproduce:
This task depends upon

Closed by  Jelle van der Waa (jelly)
Friday, 11 August 2023, 15:51 GMT
Reason for closing:  Moved
Additional comments about closing:  https://gitlab.archlinux.org/pacman/namc ap/issues/39
Comment by Samantha McVey (samcv) - Thursday, 09 June 2016, 04:54 GMT
The PKGBUILD of the AUR package 'voltdb' depends on 'java-environment-jdk=7'.
When trying to make the package with yaourt I get the error:
error: target not found: java-environment-jdk=7

Changing the PKGBUILD to depend on 'java-environment-openjdk=7' instead of 'java-environment-jdk=7' allows the package to build properly. Not sure if this is a problem with the AUR package using the wrong depends or namcap not understanding that java-environment-jdk=7 should be fullfilled by java-environment-openjdk=7.
Comment by Kyle Keen (keenerd) - Thursday, 09 June 2016, 16:30 GMT
samcv, this is an old namcap issue and completely unrelated to yaourt.
Comment by Buggy McBugFace (bugbot) - Tuesday, 08 August 2023, 19:11 GMT
This is an automated comment as this bug is open for more then 2 years. Please reply if you still experience this bug otherwise this issue will be closed after 1 month.

Loading...