From owner-freebsd-ports-bugs@freebsd.org Sat Dec 14 06:50:15 2019 Return-Path: Delivered-To: freebsd-ports-bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id B34A61E39BE for ; Sat, 14 Dec 2019 06:50:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 47ZdT34LXbz42gF for ; Sat, 14 Dec 2019 06:50:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 9358E1E39BD; Sat, 14 Dec 2019 06:50:15 +0000 (UTC) Delivered-To: ports-bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 931DF1E39BC for ; Sat, 14 Dec 2019 06:50:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47ZdT33Q0jz42gD for ; Sat, 14 Dec 2019 06:50:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 6C30F20CD4 for ; Sat, 14 Dec 2019 06:50:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id xBE6oFLB076175 for ; Sat, 14 Dec 2019 06:50:15 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id xBE6oFgL076174 for ports-bugs@FreeBSD.org; Sat, 14 Dec 2019 06:50:15 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 242619] freebsd 11.3-p5: Ports Collection support for your FreeBSD version has ended Date: Sat, 14 Dec 2019 06:50:13 +0000 X-Bugzilla-Reason: CC 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 Only Me X-Bugzilla-Who: koobs@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Works As Intended X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: koobs@FreeBSD.org X-Bugzilla-Flags: 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.29 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Dec 2019 06:50:15 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D242619 --- Comment #7 from Kubilay Kocak --- (In reply to Chris Hutchinson from comment #5) There's no need to create a new/separate bug for addressing the specific is= sue mentioned in the summary, namely: eol error being present. However, if this specific issue can indeed be verified, information provid= ed such that it can be reproduced, and a 'problem' clearly described (expected= vs actual behaviour), rlease re-open this issue with a proposed patch and a modification of the issue summary, if appropriate. Open questions on this issue are: - Is the problem that the error comes up at all on an 11.3-p5 system at this time? - Is the problem that the error comes up in certain situations of a=20 partial/incomplete upgrade process and it shouldn't come up at all? - What are the steps to reproduce? - What is the exact state of the system experiencing the issue? At present this bug does not contain information sufficient to take action, hence the present resolution "works as intended". Comments on, and the issue of the timeout, or improving it in BATCH situati= ons should take place and addressed in a separate issue. --=20 You are receiving this mail because: You are on the CC list for the bug.=