Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 8 Apr 2022 04:55:24 +0100
From:      tech-lists <tech-lists@zyxst.net>
To:        questions@freebsd.org
Subject:   Re: nvidia-driver and no update in /usr/ports/UPDATING
Message-ID:  <Yk%2ByLLDYumYRCMVN@cloud9.zyxst.net>
In-Reply-To: <20220408042816.bef7ec05f4f80a2a9678d645@sohara.org>
References:  <Yk9tEmvtQB5JEWoz@cloud9.zyxst.net> <20220408033457.847c7f829ab41f4db9a00ef3@sohara.org> <Yk%2Bn3cF9HjixtuLv@cloud9.zyxst.net> <20220408042816.bef7ec05f4f80a2a9678d645@sohara.org>

next in thread | previous in thread | raw e-mail | index | archive | help

--6CIfBlwvdonnETot
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Apr 08, 2022 at 04:28:16AM +0100, Steve O'Hara-Smith wrote:
>	No I think you should help by making actionable bug reports and
>understanding that when something doesn't happen the best response is to
>help make it happen not complain about it and that phrases like "*WHY* the
>*F**K* isn't in *UPDATING??!??!?!?!*" are unhelpful ranting so *WHY* the
>*F**K* didn't YOU provide some TEXT and cc the MAINTAINER in your
>bug report??!??!?!?! there's a FSCKING STANDARD for good bug reports D*MN
>WELL FOLLOW IT* - see how does it feel ?

Feels fine to me and has a bit of useful information. I am not joking.

Like I said, back then I thought it was sufficient to just submit=20
the bug

> phrases like "*WHY* the *F**K* isn't in *UPDATING??!??!?!?!*"

wasn't in the bug report I cited (for the font)

Anyway, nvidia-driver not being in UPDATING is this really a bug?

I would have not posted my original missive here if there was somewhere=20
better to write. I know from the other bug cited it was unlikely to be=20
actioned, or acknowledged. I don't know what else to do, apart from=20
use something else, which I really don't want as i've been using=20
freebsd since 1997.

The situation as it is right now, is untenable. I can't support end users=
=20
depending on ports that change executable names and locations=20
and other properties without notice. This is like the 10th time something
like this has happened where it's been major.
--=20
J.

--6CIfBlwvdonnETot
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEE8n3tWhxW11Ccvv9/s8o7QhFzNAUFAmJPsiMACgkQs8o7QhFz
NAUuzxAAr13NoDJszfkCLKAisEQ/rovBOxhI9h5vHkp9LIuAQW1uKpaO1awLZQoe
7UCLlt2sp3hVbWH74qWYV+rj8Diy9Rp+rfHV7/WFzwqOL/E22Ok3c8TLi/pDlwdR
BTmbKe7PuO47mCXdkmiPsptzw4I+RvOBRgv37PCxAt7D6mPHj8YI8hQNEtp89c/l
k8kEEfR6hp3Tw6bwB/1RqKHsaYaOo0wxbQ8ysImBPPibaT+YB4GAdMJzgBxCvpwy
Dd7+FfYv83+IYNqqKubv1I72UtBFeKIG0B8QIwwB/cUucuDX+3rhiOHp+TQJJ3DD
JrGanKJpGVut+OiGkpoPTEuhr+0YvbY4C1c8p+RtcKYuwprhw8U7Z+lFIa7zrR8W
nwL8anLP67oNQeR0RNrqyVuEaESeuR/HoLmfPqRMSRK6e94jIK4SeXG5UgXn43Zk
y1/FqC/3ClAK+TMWTbZvzT7KxLrkUxPNEBYuCTc5GDA3sRSOR5lxiQGLfinK7GKW
lf3KSrv8RzKYHTXmFUzmySEantzLXvfkWQkaW4GLifKpPi0alPPeQ2xA+dZAmz0/
cwJDoDemKYJ2BySFyCc3PDiBpkuc9XnMSPmYAMAFl6+Ld2Q6mFcTmEVBsNjNHDLv
CdugU8KDKnrHzeUtWJtQ8s20hXElwzsBCj9oi0Y9pRiNGqiIALI=
=ydkq
-----END PGP SIGNATURE-----

--6CIfBlwvdonnETot--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Yk%2ByLLDYumYRCMVN>