From owner-freebsd-ports-bugs@freebsd.org Sat Sep 2 20:22:29 2017 Return-Path: Delivered-To: freebsd-ports-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9931EE0282F for ; Sat, 2 Sep 2017 20:22:29 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8187E6F68E for ; Sat, 2 Sep 2017 20:22:29 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v82KMTPC044374 for ; Sat, 2 Sep 2017 20:22:29 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 221983] sysutils/linux-crashplan: Update to 4.9.0 Date: Sat, 02 Sep 2017 20:22:29 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: subtil@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-ports-bugs@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Sep 2017 20:22:29 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221983 --- Comment #1 from Nuno Subtil --- Yes, this port should be updated. I will try to do so soon. In the meantime, the automatic upgrade process worked for me to go from 4.8= .3 to 4.9.0. The client just updated itself after the subscription was updated with no manual intervention required. It might be worth checking if that wo= rks in your situation, since it may be the easiest way to unblock you. I'd also like to make sure that automatic updates are working after install= ing via the ports tree, since there is usually a fair amount of latency in gett= ing patches prepared and submitted. If you find that the automatic upgrade does= n't work, it might be useful to review the logs and figure out if there is anyt= hing that needs to be adjusted in the port. --=20 You are receiving this mail because: You are the assignee for the bug.=