Page MenuHomeFreeBSD

Problem-Reports article: fix dead links, remove wrong info
ClosedPublic

Authored by linimon on Nov 15 2025, 11:00 PM.
Tags
None
Referenced Files
F141703466: D53778.diff
Fri, Jan 9, 2:38 AM
Unknown Object (File)
Dec 2 2025, 3:36 AM
Unknown Object (File)
Nov 30 2025, 1:07 PM
Unknown Object (File)
Nov 28 2025, 10:08 AM
Unknown Object (File)
Nov 28 2025, 12:33 AM
Unknown Object (File)
Nov 24 2025, 11:33 AM
Unknown Object (File)
Nov 21 2025, 5:34 AM
Unknown Object (File)
Nov 21 2025, 4:18 AM
Subscribers
None

Details

Summary

Continue to update the Problem-Reports article.

This pass attempts to get rid of dead links. In addition, some other wrong information is fixed.

This is one in a continuing series of fixes to this article.

Note: I have not yet build-tested it.

Diff Detail

Repository
R9 FreeBSD doc repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

linimon created this revision.
documentation/content/en/articles/problem-reports/_index.adoc
80

I cannot endorse telling people to consult the discord under it's current administration.

More precisely limit suggestions on searching.

documentation/content/en/articles/problem-reports/_index.adoc
102

I find this sentence confusing. Why are you mentioning the FAQ when the link it to the handbook?

144

Does that checkbox still exist? I don't remember seeing it the last 2 or 3 times I opened an update for my ports.

documentation/content/en/articles/problem-reports/_index.adoc
102

Well, it is a Frequently Asked Question. It used to be in the FAQ but now it isn't. I won't object if we just s/FAQ// .

documentation/content/en/articles/problem-reports/_index.adoc
144

Hmm. I don't know, but it seems to be setting it automatically.

I think it's basically fine.

documentation/content/en/articles/problem-reports/_index.adoc
120

and mailing lists?

144

If don't see that, click "Show Advanced Fields" on the top-left of the submitting new bug interface. Then in the "attachment" section, there is "Content Type: If the attachment is a patch, check the box below. [ ] patch"

This is very useful as it will mark the patch's mime type as "text/plain" which can be viewed in the browser correctly.

145

Indeed, and not sure if we want to mention that the patch generated via git format-patch will be detected as application/mbox automatically, this is hard to say a bug in the system as it's indeed a valid mbox format, but it's much better to be attributed as text/plain to be easier to review.

This revision is now accepted and ready to land.Nov 16 2025, 2:18 AM
documentation/content/en/articles/problem-reports/_index.adoc
102

I won't object if we just s/FAQ// .

Come to think of it, I'd make the whole clause "first read the extref:{handbook}/cutting-edge/[Handbook section on Versions]" (if that's indeed the section you mean).

documentation/content/en/articles/problem-reports/_index.adoc
120

Well, the line just above it is about the mailing lists.

documentation/content/en/articles/problem-reports/_index.adoc
145

Is *that* where that bug is. It has been driving me nuts.

This revision now requires review to proceed.Nov 16 2025, 2:48 AM
linimon retitled this revision from Problem-Reports article: fix dead links to Problem-Reports article: fix dead links, remove wrong info.Nov 16 2025, 2:49 AM
This revision is now accepted and ready to land.Nov 16 2025, 3:03 AM

I found some tweaks build testing (via cd doc && DOC_LANG=en make documentation && w3m documentation/public/en/articles/problem-reports/index.html):

  • the handbook link on 117 was still dead, so I changed that to just the top of the handbook
  • there were some apostrophe's that seem like they should be backticks

Since these seemed trivial I committed them with these fixes. Sorry for the delay!