From nobody Fri Apr 8 02:34:57 2022 X-Original-To: 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 C38CD1A95CB2 for ; Fri, 8 Apr 2022 02:35:09 +0000 (UTC) (envelope-from 4250.82.1d4dd0004977610.88ec1c2342ba62b5e2c0e7181b269368@email-od.com) Received: from s1-b0c6.socketlabs.email-od.com (s1-b0c6.socketlabs.email-od.com [142.0.176.198]) (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 4KZMmF0WHmz3jJq for ; Fri, 8 Apr 2022 02:35:09 +0000 (UTC) (envelope-from 4250.82.1d4dd0004977610.88ec1c2342ba62b5e2c0e7181b269368@email-od.com) DKIM-Signature: v=1; a=rsa-sha256; d=email-od.com;i=@email-od.com;s=dkim; c=relaxed/relaxed; q=dns/txt; t=1649385309; x=1651977309; h=content-transfer-encoding:content-type:mime-version:references:in-reply-to:message-id:subject:cc:to:from:date:x-thread-info:subject:to:from:cc:reply-to; bh=aQ+55i3QCBTllZHQeyQvKUlvmCrUVaAa30MHvQJzSTc=; b=EvZaQEJGOR1Ue+43zkZSdnhl+y1644lpY40jhYt810BWcdz+xQ0bpeKr8cnQ/9H/9I1X3kXeLqQo80mxdP98SurijxI4FwkdKnMsrQFP4VTJt+9WEv63crlJBoAtG3QrfjSef/sdXhaqFUnVtNB42OK0cviMHgmNUE4gSSqESo4= X-Thread-Info: NDI1MC4xMi4xZDRkZDAwMDQ5Nzc2MTAucXVlc3Rpb25zPWZyZWVic2Qub3Jn Received: from r2.us-east-2.aws.in.socketlabs.com (r2.us-east-2.aws.in.socketlabs.com [142.0.189.2]) by mxsg2.email-od.com with ESMTP(version=Tls12 cipher=Aes256 bits=256); Thu, 7 Apr 2022 22:34:59 -0400 Received: from smtp.lan.sohara.org (EMTPY [185.202.17.215]) by r2.us-east-2.aws.in.socketlabs.com with ESMTP(version=Tls12 cipher=Aes256 bits=256); Thu, 7 Apr 2022 22:34:58 -0400 Received: from [192.168.63.1] (helo=steve.lan.sohara.org) by smtp.lan.sohara.org with smtp (Exim 4.94.2 (FreeBSD)) (envelope-from ) id 1nceSf-000KyT-9Y; Fri, 08 Apr 2022 03:34:57 +0100 Date: Fri, 8 Apr 2022 03:34:57 +0100 From: Steve O'Hara-Smith To: questions@freebsd.org Cc: tech-lists Subject: Re: nvidia-driver and no update in /usr/ports/UPDATING Message-Id: <20220408033457.847c7f829ab41f4db9a00ef3@sohara.org> In-Reply-To: References: X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd13.0) X-Clacks-Overhead: "GNU Terry Pratchett" 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: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4KZMmF0WHmz3jJq X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=email-od.com header.s=dkim header.b=EvZaQEJG; dmarc=none; spf=pass (mx1.freebsd.org: domain of 4250.82.1d4dd0004977610.88ec1c2342ba62b5e2c0e7181b269368@email-od.com designates 142.0.176.198 as permitted sender) smtp.mailfrom=4250.82.1d4dd0004977610.88ec1c2342ba62b5e2c0e7181b269368@email-od.com X-Spamd-Result: default: False [-2.70 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[email-od.com:s=dkim]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+ip4:142.0.176.0/20]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[sohara.org]; NEURAL_HAM_LONG(-1.00)[-1.000]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[email-od.com:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[142.0.189.2:received]; NEURAL_HAM_SHORT(-1.00)[-1.000]; MLMMJ_DEST(0.00)[questions]; FORGED_SENDER(0.30)[steve@sohara.org,4250.82.1d4dd0004977610.88ec1c2342ba62b5e2c0e7181b269368@email-od.com]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:7381, ipnet:142.0.176.0/22, country:US]; FROM_NEQ_ENVFROM(0.00)[steve@sohara.org,4250.82.1d4dd0004977610.88ec1c2342ba62b5e2c0e7181b269368@email-od.com]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[email-od.com:dkim] X-ThisMailContainsUnwantedMimeParts: N On Fri, 8 Apr 2022 00:00:34 +0100 tech-lists wrote: > So *WHY* were the consequences of PR 261666 not in /usr/ports/UPDATING? > nvidia-driver was updated to (560) i think. 5-something.. the instance > before was moved to nvidia-driver-470 as it's now legacy. That's great > and all, but *WHY* the *F**K* isn't in *UPDATING??!??!?!?!* You know if this was a commercial product for which you were paying for support and you spoke like that to a support worker you would get hung up on and blacklisted for verbal abuse. It is no more acceptable in text, especially since you are talking to users - I very much doubt that anyone involved will see your rant. Now to answer your question - there's nothing in UPDATING because the port maintainer for that port didn't put anything in there when they made the change. So if you want to know why you could look up the maintainer (listed in the Makefile) and ask them *politely* about it - maybe they had to rush a child to hospital or attend some social event and forgot to do it. Whatever the reason they deserve politeness and gratitude for what they have done not abuse for what they haven't. Or you could hurl anonymous abuse at the uninvolved with thinly disguised obscenities in a public forum to no effect whatsoever except to make yourself look foolish. -- Steve O'Hara-Smith