In D54433#1244080, @pi wrote:

Will it also explain pkgbasify ?

1. Orientation

Thanks! I'm (blindly) accepting without checking.

My current thought is much the same as Sergio's in August:

I'll pause for now, because I find it difficult to visualise with Phabricator. Clicking Undo does not undo (so, you may see repetition), and so on.

Can you tell when pkgbase.freebsd.org will be introduced?

A while ago, probably around August, I began referring to freebsd-update as legacy, because it was commonly understood that it would be "removed or at least neutered" with 15.0-RELEASE.

In D52621#1203868, @ivy wrote:

FreeBSD-base is the name of the repo for all FreeBSD (operating system) packages.

Tested with:

I can't visualise the current edition of the dialogue, can someone provide a screenshot?

If I intentionally delete an unwanted non-essential automatic package that is not a meta package, then will pkg check -d prompt to reinstall?

Related: https://bugs.freebsd.org/258987 point 1.

In D52161#1191869, @rgrimes wrote:

… single user.

On the other hand, /etc/pkg/repos/ (if created) might be valid.

Commit log messages for D52161 and D52162 should, please, show:

In D51279#1190892, @lukas.engelhardt_gmx.de wrote:

… Changed that to "If you want to start building your own pkgbase packets" instead of "To start building custom pkgbase packets". Does that answer your question? If not please specify. …

pkgbase (lowercase) throughout, thanks.

Will there be a distinct FreeBSD-pkgbasify package in the FreeBSD-base repo?

Compare with a single FreeBSD.conf for multiple FreeBSD repos, e.g. https://reviews.freebsd.org/D50583.

In the preview, some of the navigation buttons don't work, for example:

Compare with the precedent of a single file:

Packages are the future.

In D50583#1155253, @zarychtam_plan-b.pwste.edu.pl wrote:

… setting a higher priority didn't help in my case …

In D49457#1131891, @junchoon_dec.sakura.ne.jp wrote:

For completeness, I'm testing with a GPU for which the 470.⋯ driver is:

In D49457#1131202, @ashafer wrote:

… 06:41 on Sunday. Whilst the clock on the lock screen was wrong (02:33), the system was not frozen. …

… With Plasma set to turn off the screen after two minutes, I sometimes found all displays blank/dark after e.g. moving a trackball. Not turning on, presumably, although they're on after Control-Alt-F2 (vt at ttyv1) and remain on after Alt-F9 (back to Plasma). … sense that the symptom was more likely to occur with two external displays.

… OK so far, no sense of regression. I'll test with WBINVD=on. …

Thanks

Thanks. With all inlines hidden, the language looks OK, to me.

Reported by: grahamperrin

Is addition to UPDATING appropriate?

Looks OK to me.

Nit (if the summary will be the commit message), taggued and break should be:

Time to close?

Late changes. Spelling, and (I think) you need not state .ko in the context of e.g. kldload.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271574 updated.

• freebsd-tips: freebsd-update fetch, then install by grahamperrin · Pull Request #1096 · freebsd/freebsd-src

Thanks. I ran a few tests. One test result below.

I forgot:

@delphij thanks for the context.

The tail of today's https://old.reddit.com/r/freebsd/comments/18gtb5r/-/:

Unexpected loss of free space has taken some users by surprise.

@karels, nice catch with the audible parts of "a -i option". I made the same mistake with something a few months ago.

After https://cgit.freebsd.org/doc/tree/website/content/en/releases/14.0R/installation.adoc is created, with the customary Upgrading FreeBSD content, then thought can be given to foot-shooting (e.g. https://reviews.freebsd.org/D42214#963193).

In D42214#963101, @grahamperrin wrote:

Thanks @karels for the pointer.

Follow-up to discussion in IRC,

I recall accepting the invitation to participate in this working group.

Thanks! My bad at https://github.com/freebsd/freebsd-doc/pull/271/commits/2b57c53ff2b0722674929a5ccdeac3a8f5fc97c9#diff-c20a2d27b62a1f972a9588a08fd1e8956345ba08e9b5c0417fd42573fcc0c772L71-R86.

FreeBSD bug 274342 – Bug reports in Bugzilla for FreeBSD do not begin in the open state, and the Problem Report Handling Guidelines article should be archived

For reference: https://docs.freebsd.org/en/articles/pr-guidelines/

"Jane Random BugBuster …

Submitted by: Graham Perrin <grahamperring@gmail.com>

Please have content in the Wayback Machine before committing.

English looks good to me.

Thanks @dbaio

In D41986#957815, @salvadore wrote:

… lists. …

In D37213#867100, @dbaio wrote:

and as clusteradm
only missing bugmeister review, IMHO, you can already commit this.

Might GENERIC.hints be in scope?