From nobody Fri Apr 8 03:11:25 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 AF0C01AA0A57 for ; Fri, 8 Apr 2022 03:11:28 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (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 4KZNZ80CCrz3sch for ; Fri, 8 Apr 2022 03:11:28 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id DF7FD5C0117 for ; Thu, 7 Apr 2022 23:11:27 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Thu, 07 Apr 2022 23:11:27 -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; bh=lC9jmXWMrPNhUWNlsPCm2MfvJFTFvdKJ6ulanJ QXqxo=; b=rdDHXWt5NB8zPaN7V1lOSQxl0/SKpAzQQAuq7K4XEvKIgw+24zMFvc b/sgEQCD5QvTVIkBbYUfRLDtaKjlZGL2RkNY/u0OvtkiF4XeGQaYx7JDSZkC9JdV t8CgRO0i5f2o721TGmuxiCMooN4Prt+1NN4tiYH89yk0SDBN0hLDCob+l5x95daW hOtGDp1ZpRi1Y7cgSAXsy1n1CWZYw9SZT0tFY2REkPb0pZr+BPPHS0VHGIxn0CyA fylyR7SsQ0nh/uA2C4rluLspysnT2TVecldMZjJA1/omTbr7h4jsv8XKpAAA0GOL JXHUBztDwViLmsHpxLUmAQGRyiWG/QBw== 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; bh=lC9jmXWMrPNhUWNls PCm2MfvJFTFvdKJ6ulanJQXqxo=; b=KrpVqPv9NPHqFR7EPo0hTMrzlNhS6nC7/ KFM9SKiIq2mSMsrj6JKcvwSNQ/DhX7wbfCz6z/pYtEMF3dhbxsgjLgdcwR/GhQdd 0zfmlwyzIf1f+BTBCzRwROnglHx2rF1qEzkXkCuCUbPNxjaqVzms/i6fR5UMs8Ot Ka8LviX5EcZx8O0RN7tsgpRFPERXZR/pGaDBXXl6ZwNf5MWr9XdIALNI1NsGeMjW hXXhJm3dNuS7NHDiO4WhQGtcpcvhs0MhSrc169HFsKiYtdp7p4A4hswfKU7lzMTY IgyNjK+XA4OH3pq9zGOZUlUu7HTL290MDyy2820SJ7f+su3U+4a1Q== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrudejledgieefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkfhggtggujgesghdtre ertddtvdenucfhrhhomhepthgvtghhqdhlihhsthhsuceothgvtghhqdhlihhsthhsseii hiigshhtrdhnvghtqeenucggtffrrghtthgvrhhnpeettddtudeugfeggefhkeekteekje elfeffleehjeffgffftdeffedtjeegueeiffenucffohhmrghinhepfhhrvggvsghsugdr ohhrghenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpe htvggthhdqlhhishhtshesiiihgihsthdrnhgvth X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Thu, 7 Apr 2022 23:11:27 -0400 (EDT) Date: Fri, 8 Apr 2022 04:11:25 +0100 From: tech-lists To: questions@freebsd.org Subject: Re: nvidia-driver and no update in /usr/ports/UPDATING Message-ID: References: <20220408033457.847c7f829ab41f4db9a00ef3@sohara.org> 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="Qsou2B0pspkMy+eO" Content-Disposition: inline In-Reply-To: <20220408033457.847c7f829ab41f4db9a00ef3@sohara.org> X-Rspamd-Queue-Id: 4KZNZ80CCrz3sch X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=zyxst.net header.s=fm2 header.b=rdDHXWt5; dkim=pass header.d=messagingengine.com header.s=fm3 header.b=KrpVqPv9; dmarc=none; spf=pass (mx1.freebsd.org: domain of tech-lists@zyxst.net designates 66.111.4.26 as permitted sender) smtp.mailfrom=tech-lists@zyxst.net X-Spamd-Result: default: False [-6.70 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; RWL_MAILSPIKE_GOOD(0.00)[66.111.4.26:from]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.26:c]; 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(-1.00)[-1.000]; 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.26: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)[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)[questions] X-ThisMailContainsUnwantedMimeParts: N --Qsou2B0pspkMy+eO Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Apr 08, 2022 at 03:34:57AM +0100, Steve O'Hara-Smith wrote: >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. I disagree with you here, having supported commercial products for over a decade. I thought my missive was mild; though that might be cultural. This isn't truly a rant, and I'm astonished you're discounting=20 it as such. I'm frustrated because it seems some ports maintainers will not follow freebsd policies. That costs time and money, makes people like me less likely to trust freebsd; it's all so=20 needless. Yes, I realise freebsd is free. It markets itself as "the power to serve". Well, it can't serve very well if port maintainers fail to follow policy. So, maybe a better and=20 more honest slogan would be "the power to serve, but if you=20 use ports then, well, you're on your own". At least we'd know where we are. As I understand it, there's no need to modify UPDATING if the port has simply moved. But if the executable name changes=20 or if the version changes majorly and *especially* if it's a kernel module then yeah I expect it to be in UPDATING. > 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.=20 I realised this before my post and it's the reason for it. > 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. Here's a way to avoid the whole issue - update *UPDATING* before making=20 the change, and make that *mandatory* in order to update a port. Having a polite communication with the maintainer is pointless in this=20 circumstance. See https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D249252 which was ignored, twice. The problem is one of policy. > 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. Foolish for articulating my frustration? You think my post is without merit? It's the situation I'm frustrated with. There's a policy in place for changes like this and as far as I can tell it's not being followed in some cases. This makes like hell for me for any freebsd=20 system I support. I guess you think it's better i ditch freebsd and use something else? Maybe I should just bite my lip, shut up and go away? --=20 J. --Qsou2B0pspkMy+eO Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEE8n3tWhxW11Ccvv9/s8o7QhFzNAUFAmJPp9UACgkQs8o7QhFz NAWuIQ//WS7wWird2dyBMt+7L8bBeDASAHszEp1gAMP78q3UVAYOHBxlAwsVo612 hhZndT9cqHDNcLBcdj0t+OFzFT8ShmJEAaO4vJM7VphBRSRUHTjQG5IMENOtKzHB qSAObKPPAz/ZJUeUSi+bYp6cBiBXIKZ8vzP68ZZENTpsSu9gDELpxvNrstTdrj+e 3EFAkTqoRq3vRi6d20urWEaeTNWd0XKMjra9Pm4nuabGblqzQysjic2cDhBRAcGU dsGM5yqfQKvOK4XMrKFMrtc6ldU+B3TXgD5BS79dNTi8id2FV1RDsM9Aesei93de ZNGWg7Z5fXKTz40ObKyj1DLJWF9t5VoBM/gEExmJvfaK3q/MIG9envA857z92elg qRj6B2Pwn7Dy+PlRSZcjfXdM5KQ+OQgSM+8rXAQUF5EN9wmByuNW8nDWVUPyAzw/ 9MPbU4eA8hRUGI5mB6OY0ADTzQNbE3QWlutkjQkVAEHhWv75uLORL2yKXZL6BgC2 Snq2wG4myHEtgeRdQ5a10mvKD5XPK9Gfwg1MxtmeGH3UYWoDtJvywPCYTIBX9gVm A4i2HbRyqgNI0cRH2JBopAHosOgo/wFtZv0KBlWEqiwZaPcjKhjKclKe9MT+uSux 1YIEDs3hBLw1ZwHnfYJzgiq5in+h8RqgJwMd3opFukJm0bbvcoU= =7ei+ -----END PGP SIGNATURE----- --Qsou2B0pspkMy+eO--