Update 11.3 > 11.4
aryeh.friedman at gmail.com
Thu Jun 18 22:55:37 UTC 2020
On Thu, Jun 18, 2020 at 6:45 PM Jerry <jerry at seibercom.net> wrote:
> On Fri, 19 Jun 2020 08:19:12 +1000, Dewayne Geraghty commented:
> >Aryeh's suggestion of determining the cause of the problem would be
> >beneficial as the PR
> >appears to be caught in a non-reproducability trap. Eg "I have an X on
> >version Y and no bug" will not allay anyone's concerns.
> >Also reply 103 asserts that this problem doesn't exist on 11 (ie prior
> >to 11.4). Perhaps pulling the iso's for 11.4 and using on a machine
> >that reproduces the bug with 12.1 might be a more efficient path?
> It doesn't exist on 11.x at ll. If you read through the comments,
> etcetera, it was mentioned that it is most likely a regression problem.
> Regression bugs have a nasty habit of spreading.
Especially if people refuse to actual test it to see if it is a bug or not
on their system. Since it is not on mine my test is meaningless but your
might not be and might help debug it so if you care about helping the
community like you do you should try it and make a complete bug report as
possible. But as I said it happens in enough odd different places that it
is 90% likely user error not an actual bug and you just falling for FUD if
you are not willing to help figure it out.
> >Hans is clearly doing his best to address the issue but needs helpful
> >information from our active community.
> This bug has existed since at least 2019-04-30 04:22:45 EDT when it was
> first reported.
> >Regards, Dewayne
> freebsd-questions at freebsd.org mailing list
> To unsubscribe, send any mail to "
> freebsd-questions-unsubscribe at freebsd.org"
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
More information about the freebsd-questions