From owner-freebsd-ports-bugs@freebsd.org Sun Jun 3 19:49:24 2018 Return-Path: Delivered-To: freebsd-ports-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 49CEBFF33C8 for ; Sun, 3 Jun 2018 19:49:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id D98CE789A9 for ; Sun, 3 Jun 2018 19:49:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 96D23FF33C0; Sun, 3 Jun 2018 19:49:23 +0000 (UTC) Delivered-To: ports-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 85830FF33BF for ; Sun, 3 Jun 2018 19:49:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 26B10789A3 for ; Sun, 3 Jun 2018 19:49:23 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 698772C265 for ; Sun, 3 Jun 2018 19:49:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w53JnMeO078932 for ; Sun, 3 Jun 2018 19:49:22 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w53JnMvf078931 for ports-bugs@FreeBSD.org; Sun, 3 Jun 2018 19:49:22 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 227600] porter's handbook: use of distinfo Date: Sun, 03 Jun 2018 19:49:22 +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 Only Me X-Bugzilla-Who: freebsd@dreamchaser.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: ports-bugs@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.26 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2018 19:49:24 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D227600 --- Comment #2 from freebsd@dreamchaser.org --- You're correct in that the message clearly states that distinfo is out of d= ate. However, if one is updating a port, one needs to do the fetch before one can run make makesum to produce an up-to-date version of distinfo. But one can= 't do the fetch if a distinfo is lying around. A user can easily think "I know it's out of date, I'm trying to fetch the file and generate an up to date version!" The issue is not with the failure message; the issue is with the general description of the fetch phase in the Porter's Handbook. It would be helpf= ul if the Handbook indicated the fetch itself will not succeed if a distinfo is lying around which does not match the file being fetched. It is not at all clear that a mis-matched distinfo will cause a fetch to fail, particularly since distinfo is not required to be there to perform a fetch, and cannot be generated until after the fetch is done. One could also make the message a little clearer, such as: =3D> Either /hd2/home/garya/Computing/ports/graphics/nufraw/distinfo is out= of date, or =3D> nufraw-0.41.tar.gz is spelled incorrectly. =3D> If distinfo is out of date, delete it before attempting to fetch. --=20 You are receiving this mail because: You are the assignee for the bug.=