From nobody Wed Apr 13 00:44:47 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 8D64F11C8ACD for ; Wed, 13 Apr 2022 00:44:56 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (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 4KdP4l5v07z4Td7 for ; Wed, 13 Apr 2022 00:44:55 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 906C35C0233 for ; Tue, 12 Apr 2022 20:44:49 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Tue, 12 Apr 2022 20:44:49 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h=cc :content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm2; t=1649810689; x=1649897089; bh=Crz4PDgWFr 1dpMbxCUMG3xpwWewaBXfJP3uyhUbXfYQ=; b=ljQnu1YjlaL7wqJDBeq8rmVLwA 9yyebMzuZ7RTRN+V5HqwojvK44OzXdgVNdsv1ltXQNkwQqrp0zwuw71Ld8uR+zVu 6+4Nvttas8II5OmYP8KV1BUMahR08XTdbVCb4l8M1YQCC1yToYrp43BGpkXjKw3f E/GlXwfoW0H0NsttnKMq8BkY4owxz8CPOR9dDMQmwuTquYsFrEEpNJVEfoJ64JY8 sRdmc36jCKoSiNIV9qzpydAOTEvo19VqqyFkNS7N93KpWEV9PNtzDH2zC5hESnA/ Ddl1dNwRpcJLa7Ocsw6nGziatf6Tuorq/OtYg+I6jfJeKLgVQo8Km5hPz73Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1649810689; x= 1649897089; bh=Crz4PDgWFr1dpMbxCUMG3xpwWewaBXfJP3uyhUbXfYQ=; b=e mAcHC15wGK/9qlgWDQOQbTZAziESh915tguUzpQ9N9NJcLfIsIx41a6iyN/+amnt GfDwG8ZYLlfZnbOzGJNsp7bo3C/X+1wTZrxvN7T0QMHCFL6+SNDAfyYgNF/1QPhT 7QjmTNNO043KdBXyxMb3m8txMqI97Rrk8lgVcnD60+r0hnftuEkjXuDroALFw67k 1K5pa5xuC96y8ZUfcP7DKYyCCTcDz54KiO35jpAGW0NCtz/uK30dkfPp+HHOCmg9 NlcmdWlZqwOuvDRH4POpoxrTJOFBfkblFKotrLYMjon8CyK6XQJtFV/146vfbD9m LvHvEfJy7vnpaJtAbZQCQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrudekledgfeekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkfhggtggujgesghdtre ertddtvdenucfhrhhomhepthgvtghhqdhlihhsthhsuceothgvtghhqdhlihhsthhsseii hiigshhtrdhnvghtqeenucggtffrrghtthgvrhhnpeffieelteetleegffdvieeuieeuie dvtdfhueeutdfgjeekteeileeiueegkefhffenucffohhmrghinhepghhithhhuhgsrdgt ohhmnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepth gvtghhqdhlihhsthhsseiihiigshhtrdhnvght X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Tue, 12 Apr 2022 20:44:49 -0400 (EDT) Date: Wed, 13 Apr 2022 01:44:47 +0100 From: tech-lists To: freebsd-questions@freebsd.org Subject: Re: Changes (was: nvidia-driver and no update in /usr/ports/UPDATING) Message-ID: Mail-Followup-To: freebsd-questions@freebsd.org References: <16715f81-49c7-9710-d4f4-2a555f0eff74@gmail.com> 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 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="VIyRRt2ck7WIHiYG" Content-Disposition: inline In-Reply-To: <16715f81-49c7-9710-d4f4-2a555f0eff74@gmail.com> X-Rspamd-Queue-Id: 4KdP4l5v07z4Td7 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=zyxst.net header.s=fm2 header.b=ljQnu1Yj; dkim=pass header.d=messagingengine.com header.s=fm3 header.b="e mAcHC1"; dmarc=none; spf=pass (mx1.freebsd.org: domain of tech-lists@zyxst.net designates 66.111.4.25 as permitted sender) smtp.mailfrom=tech-lists@zyxst.net X-Spamd-Result: default: False [-6.48 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; RWL_MAILSPIKE_GOOD(0.00)[66.111.4.25:from]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.25]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; MID_RHS_MATCH_FROMTLD(0.00)[]; DKIM_TRACE(0.00)[zyxst.net:+,messagingengine.com:+]; NEURAL_HAM_SHORT(-0.78)[-0.780]; SIGNED_PGP(-2.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:19151, ipnet:66.111.4.0/24, country:US]; RCVD_IN_DNSWL_LOW(-0.10)[66.111.4.25:from]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[zyxst.net:s=fm2,messagingengine.com:s=fm3]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; DMARC_NA(0.00)[zyxst.net]; RCPT_COUNT_ONE(0.00)[1]; DWL_DNSWL_LOW(-1.00)[messagingengine.com:dkim]; MLMMJ_DEST(0.00)[freebsd-questions] X-ThisMailContainsUnwantedMimeParts: N --VIyRRt2ck7WIHiYG Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Apr 11, 2022 at 05:44:28PM +0100, Graham Perrin wrote: > Did you also rant about the commit message for >/411dc97c6b9b60301edaf6cc0fa04053b0f56dd4>? No I did not. But I'm I'm sorry I ranted here, truly.=20 It was an emotional outburst. But trust is an emotional thing. I can't trust ports right now to do the right thing. I have many freebsd vms to=20 decomission and replace now with something else, because=20 of this fact. There are some I must not be blindsided=20 like this on. I accept stuff changes, having used freebsd and the ports collection since 1997. I can and have done when needs=20 be work with and round issues with PRs, and I am very=20 grateful for both in ports and src to have this great=20 ecosystem provided by volounteers. But if you've read this thread, you will understand it wasn't about any one port. It was about not updating UPDATING when a port changes name (in this example). It's not a bug. To avoid the issue requires hardly any work from the committer, if it is indeed the committer who would update this file=20 (I don't actually know, it might be another department or group).=20 Just a note at the top of the file in /usr/ports/UPDATING. Ideally before an update is committed. I see there is still no note in UPDATING for nvidia-driver in ports-579962. This means that anyone with PORTS_MODULES+=3Dx11/nvidia-driver in their /etc/src.conf who updates their stable/13 world/kernel and who has eg a GeForce (640 for example) will not be able to=20 load xorg when their system reboots. Because the wrong kernel=20 driver was compiled. Because the name change wasn't in UPDATING. --=20 J. --VIyRRt2ck7WIHiYG Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEE8n3tWhxW11Ccvv9/s8o7QhFzNAUFAmJWHPYACgkQs8o7QhFz NAXY+Q//W5wcfXAyOuRxQWn1BYWm7Vt9S0UdMclxu4guHZs5YPkp2O6MaCV91+2W 1fnVtwgiXITwsSxMFgMbf4+a3T70+PRzh+jVUrwzwB4fJj2IzVz9W4dREnOBsQ19 9HsWAKb3k/EGmSsjWOxJC8k81ipIqHU4qLhN2JO5uv0UZAVGCSKVHbL7XXFSozUp guLZA57jMS4yCFU4GsyEUJc+RTP/42xKxZNaJ9R1Il9EGRXaVF8qje5xvoB9jCma J8GzNotaZRK6MYuQn3DaXfnAW2O2PCOeBkhoxcCz0O/kTAl0UssEzW0S7S3ESpM0 KN/nlvxEUhUrWFZDhZx83GPaXaKcPOBeowR01Ax6giQcITd0Y0qN7honDR9qbxmA fWyAgo80InqsQKH2IB0RQXzwJShiUe/HzHfgauLrRucnjw7q4sX+EaglE8q16tEH AWDjH+iLlm3FcL2YrX4/REh+EGMghppnufw2WLJxJoDlefzvnMl7Z2QMmNoaLJoe obELzdCN2YHgTbkM4Ga2DK+4tZjLdnh6AS9a74eU24X8UC6VDu9H2KoNXGyrVwJc k87QpPaMEIaX0OUV830vqwqQnZ0A7dFUmkzEvyhJsSrZn3NWAmhwaKqF0Dd7aVky A1Cjbe16iyc0NCZMMX/v5KnruZJ7zzSy9B4oJnSyoYo0y4KEojY= =vpk5 -----END PGP SIGNATURE----- --VIyRRt2ck7WIHiYG--