I don't have enough experience/confidence with the ports system to supply a patch, but I did hack the existing 4.5.0 port enough to get things working for me * Makefile, distinfo and plist needed updating for the 4.7.0 tarball and the files in it * /usr/local/share/crashplan/bin/CrashPlanEngine needed hacking. it expects $JAVACOMMON to be the JRE path
I don't know if it needs to be noted anywhere, but CrashPlan 4.7.0 is incompatible with any prior version of CrashPlan for computer-to-computer backups. If anyone has been backing up to a FreeBSD CrashPlan, it would have stopped working around May 16 since the port is still on 4.5.0 https://support.code42.com/CrashPlan/4/Troubleshooting/Computer-To-Computer_Backups_Stop_Working_Between_Version_4.7_And_Earlier_Versions
Created attachment 171477 [details] Fix and update sysutils/linux-crashplan to 4.7.0 This patch updates CrashPlan to 4.7.0, fixes the JAVACOMMON variable issue (#209950), and fixes the log path (currently logs are dumped in / but the port creates and expects them in /var/log/crashplan).
I should point out that CrashPlan 4.7.0, at least when I tried it in a FreeNAS 9.10 jail, was having issues connecting to the login server - UnresolvedAddressException. Reverting to 4.5.0 but keeping all other installed dependencies the same causes the issue to disappear.
Nevermind, this was a local issue.
The patch looks good to me (thanks Samuel!). I'm unable to test this for at least the next 2 weeks, but I'm OK with submitting the patch as-is.
I think someone else besides me should test this first. I would hate to have this submitted if it is a real issue and then linux-crashplan starts breaking everywhere once people update. I thought it was a local issue but now I'm not so sure. That DNS issue I was having before... with linux-oracle-jdk18 it randomly appears and very rarely manages to connect to the CrashPlan servers even to log in - UnresolvedAddressException. Version 4.5.0 on the same JVM version is fine. With linux-sun-jre17 CrashPlan 4.7.0 is consistently fine connecting to CrashPlan servers. That version of the JVM, however, is deprecated.
Given that the port is already broken as it is, I'd say the risk of submitting this patch is pretty low. Anyone who has updated their port already has a non-functioning CrashPlan install. That said, it may take a while for the patch to get submitted anyway. I'll try to test it when I can, but I'd rather not wait for that before merging the patch.
Comment on attachment 171477 [details] Fix and update sysutils/linux-crashplan to 4.7.0 Nuno, feel free to flag the patch with maintainer-approval(+) when you think it's ready to be committed. (note: that's on the patch, different from maintainer-feedback(+) you gave)
Committed, thanks! Please note: ChangeLogs would be helpful: What changed from the last version ?
A commit references this bug: Author: pi Date: Sun Jul 3 14:14:33 UTC 2016 New revision: 417971 URL: https://svnweb.freebsd.org/changeset/ports/417971 Log: sysutils/linux-crashplan: 4.5.0 -> 4.7.0 PR: 210248 Submitted by: ludwigp-fbsdbugz@chip-web.com, Samuel Grossman <sam@samuelgrossman.ca> Approved by: Nuno Subtil <subtil@gmail.com> (maintainer) Changes: head/sysutils/linux-crashplan/Makefile head/sysutils/linux-crashplan/distinfo head/sysutils/linux-crashplan/pkg-plist