From nobody Fri Apr 8 04:24:05 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 C81551A8DBE7 for ; Fri, 8 Apr 2022 04:24:09 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4KZQB03YTGz4gSh for ; Fri, 8 Apr 2022 04:24:08 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 3EC885C01E5 for ; Fri, 8 Apr 2022 00:24:08 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Fri, 08 Apr 2022 00:24:08 -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=WWqMnPtqjQJcrRL7csf5s6hpL6ISHgup3DDE1U CIrcM=; b=G23hfuVOlOYSpPzXKvrnqvzqj6xCz1P1Ss5+4NIdNWgScoj3T18FTO ZrSplaqfC/B/m8FPYx1KDcDVGemkiAtHZPp6UDto+d/Tm12U2S+om7rOwMs4Up+6 wiksk0ca1v1iePNOCA4nExNlgDQfIv9N9rQxRutoXk3UO81XncuLcatmO65NQhcA 95aNe3xSgrG5tzXZDcBZiTFoyHSH9Gg5Iq2IXflckuJGUKQgIh20OmLvXGLI72Ss tyve95c5UMPDVUgxiCjhIOjuXQ70CZxNfMz0wrCY78C0Iou7civr2/j952LzEU+8 wb/birbz+phMBQ3Uc24fTxHECSUYj9KQ== 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=WWqMnPtqjQJcrRL7c sf5s6hpL6ISHgup3DDE1UCIrcM=; b=GZeLRCIeGfy2rkuVOD9UI/dk9r+vf0iwg 2swVxlRLoDQGOQEYuLDbgbGE0KfAXOyHPU/Gw4IRtH8wvoq75caIDCiRhJtiicg9 LFuyX5CzJ5joeKC9bTcl7w+fkC6pRdeAdCI2KECvf/1mrrQ+3KPscCLKQSBjNBlO HVZuZRF4vj85KWbAv1O9BdXzxEP49IyzJCRyruvG4absuJtR0VpgtmA1foCCu0j0 UJS+fHW5dP9kmL83aqPoEXJUivh3v8CcTiTbgdRCOjOC+LM2tBvKMs4lSMdYKt1p IKg4j3DE1AUgsYFLAN2eVfakU7GbWy78oTZ8MmR8lOlKXhRfDJ25Q== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrudejledgjeelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkfhggtggujgesghdtre ertddtvdenucfhrhhomhepthgvtghhqdhlihhsthhsuceothgvtghhqdhlihhsthhsseii hiigshhtrdhnvghtqeenucggtffrrghtthgvrhhnpedtheeigfdvudefkeekvddtfedvte dttdekuddvgeevlefftdekffdujedvhfduteenucevlhhushhtvghrufhiiigvpedtnecu rfgrrhgrmhepmhgrihhlfhhrohhmpehtvggthhdqlhhishhtshesiiihgihsthdrnhgvth X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Fri, 8 Apr 2022 00:24:07 -0400 (EDT) Date: Fri, 8 Apr 2022 05:24:05 +0100 From: tech-lists To: freebsd-questions@freebsd.org Subject: Re: nvidia-driver and no update in /usr/ports/UPDATING Message-ID: Mail-Followup-To: freebsd-questions@freebsd.org References: <20220408040100.7ce89e7d46a0cea249a89711@sohara.org> <20220408043958.788fb8e1d0d404c590a211d2@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="jF1MwzQBuAL7EKSq" Content-Disposition: inline In-Reply-To: <20220408043958.788fb8e1d0d404c590a211d2@sohara.org> X-Rspamd-Queue-Id: 4KZQB03YTGz4gSh X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=zyxst.net header.s=fm2 header.b=G23hfuVO; dkim=pass header.d=messagingengine.com header.s=fm3 header.b=GZeLRCIe; dmarc=none; spf=pass (mx1.freebsd.org: domain of tech-lists@zyxst.net designates 66.111.4.29 as permitted sender) smtp.mailfrom=tech-lists@zyxst.net X-Spamd-Result: default: False [-6.70 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[zyxst.net:s=fm2,messagingengine.com:s=fm3]; NEURAL_HAM_LONG(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.29]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; DWL_DNSWL_LOW(-1.00)[messagingengine.com:dkim]; 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]; DMARC_NA(0.00)[zyxst.net]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; MLMMJ_DEST(0.00)[freebsd-questions]; 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.29:from] X-ThisMailContainsUnwantedMimeParts: N --jF1MwzQBuAL7EKSq Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Apr 08, 2022 at 04:39:58AM +0100, Steve O'Hara-Smith wrote: >On Fri, 8 Apr 2022 04:21:55 +0100 >tech-lists wrote: > >> Where, exactly, did I rant, in that report? Honestly, I can't >> see where. > > It's a rant because it's not actionable. > > You failed to explain the impact on the user - you clearly know >what the impact was but I couldn't tell from your bug report what the entry >needed to tell the user just that you thought one was needed to tell people >something about a name change. This wasn't a "bug" to "fix" in the usual sense. My issue there wasn't that the name changed per se, it was that there was no notice of=20 it in UPDATING. My issue is that baseline changes that by policy should=20 be recorded in UPDATING, are not and this is causing chaos. I can accomodate a name change if it's added to UPDATING because=20 UPDATING is something I regularly check (like every time before a=20 pkg upgrade) If a font name is changed then everything referencing that font=20 name will fail to display unless the php (in this case) referencing the font also changes its reference. This I would think would be implicitly understood by the font maintainer. If bash changed name of its installed binary to aildgjvoieaf,=20 wouldn't you expect this to be in UPDATING? > A suggested entry would go a *long* way to getting it addressed - >you clearly know what the entry should say having solved the problems >yourself but you didn't bother to share your experience in detail. Does the maintainer not know how to make an entry in UPDATING for a port they're maintainer for? If so, that would be news to me. > Because you didn't provide a solution when you could and should >have done so and you didn't make it easy for the triager to assess the >importance of the bug. My "solution" is in the bug. From the bug: "The name of this font has changed to include the version number.=20 Can something about this be put in /usr/ports/UPDATING ?=20 Because otherwise it's easy to miss." I was never asking to modify a program. I was asking for the fact it=20 had been non-trivially modified to be put into UPDATING. I showed=20 the consequences of the port update.Why was that not actionable? --=20 J. --jF1MwzQBuAL7EKSq Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEE8n3tWhxW11Ccvv9/s8o7QhFzNAUFAmJPuN0ACgkQs8o7QhFz NAV56A/+O0L80oT/gS5uprA90EGs2zkvIYV8BkoxSDY1TDOXm9eVkRdQyNKG0UWg vCQ1YVT8FfCHhOdc4EG2H4UpAmeiKC+FVtzTA/7n60cda/+FgO2XFoYFom+4qQ2T s/cQc4SlK1OUbTfoEWtS2KCIm5mK4HlEyRB7dOejpmy0Q5ygDsNi7b5CyEnMUpL+ XROECtKDVXCEJViOoEPhzgpMkIRzDIt+yX1JvhjvFK/h5MjtTSjOTXAUgdy6/QT3 DiJEa1YLg2dQj0Eih+Bb6dhnVqYHWKrx7UcJRsrxVk+pD+iEyKWxiMq2Dn0MLUeq 7Qm6uCEcslhPfV5J2xZRDLtdwVf/xpS2hdclPiQ//E48QXtEkiB/NLSUCYqKpxgu 31AnELm6EV+Vg+xuPhMNenBUadZnY3Dfjicv9RL4lBMfYZly6IIfTX82MHzhT4EL krE1LEooBavIyAUBxr6CbnboDNeho6VltDPmyZjnfQOnqjzQxNiQumn3V9Ml/L59 rndqblu7owIRloPBPtXjz2E3lSvmNHJyFWvsTZpgJiUctANOSBUIioyq9cSwCjFg 8RYXFS08tfcx7P+4pewzTNN87421HK1ltxi0kyVo/AaEQQ6lRB/N3hj2QGkyBT8y HfIOYQaWtOvnIkrI3MnVpqRYNxKEuZ+j1gL/vyfI9eVHjx6nlkA= =H/QC -----END PGP SIGNATURE----- --jF1MwzQBuAL7EKSq--