14.4/errata: add issue - freebsd-update hanging when pkg is not bootstrapped

[vladlen]

Summary

Add an erratum describing a problem where freebsd-update(8) commands such as
fetch or install may hang when pkg(8) is not bootstrapped.

The erratum also documents a workaround: bootstrap pkg(8) before running
freebsd-update(8).

PR: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=293516

[grahamperrin]

website/content/en/releases/14.4R/errata.adoc

66–68

Punctuate between multiple sentences within a single list item.

I know, this was not done for https://www.freebsd.org/releases/15.0R/errata/#open-issues, but I do prefer to see full stops.

If punctuation will be omitted: someone should please check how these strings of sentences sound in a screen reader (I can not check this at the moment, sorry).

67

Acceptance is also required for pkg bootstrap.

For an erratum line, in this case, I lean towards the simplest possible description of a workaround. We're lucky, it's a very easy workaround :-)

A more eloquent description can be offered in an errata notice (EN) after the cause has been diagnosed (bug 293516) and fixed.

68

Punctuate.

[ziaee]

I really like Graham's suggested workaround, but I personally think it's wrong to punctuate items in this type of list. It's bad for URLs. I approve for accepting any combination or none of the suggestions. Thanks @vladlen!

website/content/en/releases/14.4R/errata.adoc

66–68

In American English this just isn't a requirement. See https://developers.google.com/style/periods for an example. I didn't do it when I wrote the 15.0 errata for consistency with the URL that should not have punctuation because periods are a valid URL character.

67

+1, open issues should be as simple as possible. The full lifecycle of deeper details should all be linked to the bug.

68

No, we don't punctuate list item URLs elsewhere in the release notes, and we do have them a few places. That is why I deliberately chose not to use them when I wrote this section for 15.0.

[vladlen]

I fixed punctuation and kept "then rerun man:freebsd-update[8]" , otherwise it looks like advise to run pkg instead of freebsd-update (too short description).

[grahamperrin]

Thanks.

Notes:

• Character Replacement Substitutions | Asciidoctor Docs
• Hard Line Breaks | Asciidoctor Docs.

Also, I guess, the state of bug 293516 might be in progress fairly soon …

website/content/en/releases/14.4R/errata.adoc

66

66–68

-- for an em dash, as shown at https://github.com/grahamperrin/freebsd-doc/pull/7.diff (from https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=293640#c2).

Remove the trailing +, a hard break is not required at the last line. (This mistake was in my PR. Sorry.)

Show the link to the bug as "bug 293516", and punctuate. Compare with https://github.com/freebsd/freebsd-doc/commit/c23463321cb279e25489c1861605adeff6012b4c (co-authored by cperciva); https://www.freebsd.org/releases/14.3R/errata/#late-287482.

[ziaee]

website/content/en/releases/14.4R/errata.adoc

66

Rerun is perfectly fine and I think sounds more normal than reuse in this context.

66–68

• for an em dash,

Why? We didn't use those last time.

Remove the trailing +, a hard break is not required at the last line.

It's correct to have actually because then the next entry does not have to disrupt this entry. The expectation is this list will grow.

Show the link to the bug as "bug 293516", and punctuate.

Why? I think the plain actual link is more useful in more types of rendering.

If you want to argue to change the style from what we've been using, you should explain what the problem is and how that would solve it, like I do and everyone else. These are all nits. However, we are dropping the release in ten hours. For Vladlen, who is doing all of the actual work to a very high standard, it is already the end of the workday in his timezone.

To be honest I don't care about the style that much as long as it's sensible and consistent with the rest of the page. But, this is the wrong time to press Request Changes over wanting to change the style from what we've been using, especially with no explanation as to why, at the eleventh hour of getting a release out the door.

[vladlen]

rerun changed to reuse
dash (-) and the final + kept unchanged according to the style in 15.0R errata.adoc.

If I get approval in 1-2 hours, I will land today, otherwise only tomorrow. I am in UTC+7.

[ziaee]

Thanks for your hard work @vladlen!