Bug 209950 - sysutils/linux-crashplan: $JAVACOMMON vs $JAVA_COMMON
Summary: sysutils/linux-crashplan: $JAVACOMMON vs $JAVA_COMMON
Status: Closed Overcome By Events
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Kubilay Kocak
URL:
Keywords:
Depends on: 210248
Blocks:
  Show dependency treegraph
 
Reported: 2016-06-02 00:49 UTC by Nicolas Le Gland
Modified: 2016-08-23 15:07 UTC (History)
3 users (show)

See Also:
subtil: maintainer-feedback+


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nicolas Le Gland 2016-06-02 00:49:21 UTC
Since ports r414797, the "Makefile" sets a $JAVA_COMMON variable in the "install.vars" configuration file. The patched "CrashPlanDesktop" and "CrashPlanEngine" use the $JAVA_COMMON variable instead.
Comment 1 Nicolas Le Gland 2016-06-03 21:46:52 UTC
Since ports r414797, the "Makefile" sets a JAVA_COMMON=${JAVA} variable in the "install.vars" configuration file. The patched "CrashPlanDesktop" and "CrashPlanEngine" use the ${JAVACOMMON} variable instead.

EDIT: Typo
Comment 2 jude609 2016-06-16 09:17:00 UTC
This issue (a typo in the Makefile) prevents CrashPlan from starting cleanly after install; workaround is to edit install.vars manually.

I submitted a patch to #206305 that updates CrashPlan to 4.7.0 and also fixes this problem.
Comment 3 jude609 2016-06-16 09:18:09 UTC
Oops, sorry, I meant #210248 not #206305.
Comment 4 Nuno Subtil 2016-08-23 15:04:58 UTC
Samuel is right, this was fixed under #210248. I think this bug can be closed.
Comment 5 Kubilay Kocak freebsd_committer freebsd_triage 2016-08-23 15:06:32 UTC
Close as resolved by bug 210248 as per maintainer comment 4.

Please re-open this issue if that turns out not to be the case.