From nobody Wed Apr 13 01:25:04 2022 X-Original-To: freebsd-questions@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 6560711D5132 for ; Wed, 13 Apr 2022 01:25:17 +0000 (UTC) (envelope-from paul@gromit.dlib.vt.edu) Received: from gromit.dlib.vt.edu (gromit.dlib.vt.edu [128.173.126.123]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4KdPzJ3BWnz4drP for ; Wed, 13 Apr 2022 01:25:16 +0000 (UTC) (envelope-from paul@gromit.dlib.vt.edu) Received: from smtpclient.apple (unknown [IPv6:2001:470:e15b:23::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gromit.dlib.vt.edu (Postfix) with ESMTPSA id DA3AD735DB for ; Tue, 12 Apr 2022 21:25:05 -0400 (EDT) From: Paul Mather Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.80.82.1.1\)) Subject: Re: Changes (was: nvidia-driver and no update in /usr/ports/UPDATING) Date: Tue, 12 Apr 2022 21:25:04 -0400 References: <16715f81-49c7-9710-d4f4-2a555f0eff74@gmail.com> To: freebsd-questions@freebsd.org In-Reply-To: Message-Id: X-Mailer: Apple Mail (2.3696.80.82.1.1) X-Rspamd-Queue-Id: 4KdPzJ3BWnz4drP X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=fail reason="No valid SPF, No valid DKIM" header.from=vt.edu (policy=none); spf=none (mx1.freebsd.org: domain of paul@gromit.dlib.vt.edu has no SPF policy when checking 128.173.126.123) smtp.mailfrom=paul@gromit.dlib.vt.edu X-Spamd-Result: default: False [-2.42 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; FREEFALL_USER(0.00)[paul]; FROM_HAS_DN(0.00)[]; MV_CASE(0.50)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-0.99)[-0.986]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.94)[-0.938]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-questions]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:1312, ipnet:128.173.0.0/16, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; DMARC_POLICY_SOFTFAIL(0.10)[vt.edu : No valid SPF, No valid DKIM,none] X-ThisMailContainsUnwantedMimeParts: N On Apr 12, 2022, at 8:44 PM, tech-lists wrote: > On Mon, Apr 11, 2022 at 05:44:28PM +0100, Graham Perrin wrote: >=20 >> Did you also rant about the commit message for >> > /411dc97c6b9b60301edaf6cc0fa04053b0f56dd4>? >=20 > No I did not. But I'm I'm sorry I ranted here, truly. It was an = emotional outburst. >=20 > But trust is an emotional thing. I can't trust ports right > now to do the right thing. I have many freebsd vms to decomission and = replace now with something else, because of this fact. There are some I = must not be blindsided like this on. Have you considered tracking the quarterly ports branch instead, if you = want less volatility? (IMHO, the quarterly branch brings its own set of = issues, so this may not be a good solution for you.) Also, do you have a dev/test environment where you can smoke-test = changes before deploying them in production? Finally, have you considered subscribing to the ports mailing list, = where reports of breakage and heads-up on potentially dangerous change = often surface (along with solutions/workarounds)? FWIW, I've also fallen foul of tardy or absent ports UPDATING entries = that have left me temporarily broken, so I feel your pain. I've learned = to counter it with more rigorous QA on my part. :-) Cheers, Paul.