From owner-freebsd-ports-bugs@freebsd.org  Sat Sep  2 21:59:46 2017
Return-Path: <owner-freebsd-ports-bugs@freebsd.org>
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 64C1EE06774
 for <freebsd-ports-bugs@mailman.ysv.freebsd.org>;
 Sat,  2 Sep 2017 21:59:46 +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 51B4271FDD
 for <freebsd-ports-bugs@FreeBSD.org>; Sat,  2 Sep 2017 21:59:46 +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 v82Lxk5I008577
 for <freebsd-ports-bugs@FreeBSD.org>; Sat, 2 Sep 2017 21:59:46 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 21:59:46 +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: rb@nugman.de
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: <bug-221983-13-7T0Xn1xgoD@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-221983-13@https.bugs.freebsd.org/bugzilla/>
References: <bug-221983-13@https.bugs.freebsd.org/bugzilla/>
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 <freebsd-ports-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports-bugs>, 
 <mailto:freebsd-ports-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports-bugs/>
List-Post: <mailto:freebsd-ports-bugs@freebsd.org>
List-Help: <mailto:freebsd-ports-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports-bugs>, 
 <mailto:freebsd-ports-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 02 Sep 2017 21:59:46 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221983

--- Comment #4 from rb@nugman.de ---
Hm, very strange.
The latest upgrade log is from April 28th. It seems that the upgrade back t=
hen
failed because of an invalid SSL certificate on Crashplan's download site, =
but
this is probably not related to the recent events.

I took a look at the logs but found no evidence that the automatic upgrade =
was
started after the subscription upgrade, although an upgrade thread seems to=
 be
running (named service.upgrade.DownloadManager).
Is there a way to trigger the upgrade manually?

--=20
You are receiving this mail because:
You are the assignee for the bug.=