Date: Sun, 19 Jun 2016 05:46:06 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 210248] sysutils/linux-crashplan: Update to 4.7.0 Message-ID: <bug-210248-13-2zggevUFFV@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-210248-13@https.bugs.freebsd.org/bugzilla/> References: <bug-210248-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D210248 --- Comment #6 from Samuel Grossman <sam@samuelgrossman.ca> --- 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 breaki= ng everywhere once people update. I thought it was a local issue but now I'm n= ot 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 f= ine. With linux-sun-jre17 CrashPlan 4.7.0 is consistently fine connecting to CrashPlan servers. That version of the JVM, however, is deprecated. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-210248-13-2zggevUFFV>