Freebsd 15.1. -p1 dirty ???

Did you reboot or is this before a reboot?
What does freebsd-version -kru show?

I did the same on my 15.1-RELEASE-p0, have not rebooted yet and freebsd-version shows (as I expect):
15.1-RELEASE-p1 <<<< kernel that will run on reboot
15.1-RELEASE <<<< currently running kernel
15.1-RELEASE-p1 <<<< Userland

uname -a shows (from the -p0 running kernel):
FreeBSD FBSDNUC 15.1-RELEASE FreeBSD 15.1-RELEASE releng/15.1-n283562-96841ea08dcf GENERIC amd64
 
Ok, so you did reboot.
I did "strings /boot/kernel/kernel | grep RELEASE" and get the same version string you show.
I'm not sure what it means but I'm sure someone will.
 
drsnx60 said:
uname says "dirty" after freebsd-update fetch install . Did I fail ? or why is machine labeled as dirty ?

uname -a
FreeBSD h7510 15.1-RELEASE-p1 FreeBSD 15.1-RELEASE-p1 #0 -dirty: Tue Jun 30 03:16:39 UTC 2026 root@amd64-builder.daemonology.net:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64
Click to expand...
This likely means the kernel was built while there were still some uncommitted files in the src tree. I see this in a VM updated with freebsd-update but don't see it in one updated with pkgbase.
 
I got several security announcements and updated. Then about 15 minutes later got some more, so for now, I'm waiting awhile I suspect that as bakul said, uncommitted files, but that's just a guess from me, not knowledge.
 
Also on 14.4:
Code: 
uname -a
FreeBSD system.co.nz 14.4-RELEASE-p7 FreeBSD 14.4-RELEASE-p7 #0 -dirty: Tue Jun 30 08:53:56 UTC 2026     root@amd64-builder.daemonology.net:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64
 
vuu_pn said:
Same thing with 14.4 after freebsd-update. Multiple reboots do not help.
Click to expand...
Reboots are not going to help. That's the version string embedded into the kernel, so until the kernel is changed, rebooting is not going to change anything.

I'm guessing that the people that need to know, know and are working on it and eventually frebsd-update fetch will return something.
Maybe a discussion is happening on the mailing lists
 
Yes, Re: 15.1-RELEASE-p1 has dirty tag set?:
Code: 
From: Dag-Erling_Smørgrav <des_at_FreeBSD.org>
Date: Wed, 01 Jul 2026 09:46:02 UTC

Brandon Allbery <allbery.b@gmail.com> writes:
> I just upgraded to 15.1-p1. When I log in or if I `uname -a`, the
> version shows "-dirty" after the version. Is this expected /
> intentional?

It is the unfortunate result of operator error when submitting the
patches to the freebsd-update build server.  Since only the metadata is
affected, and only for amd64, we will most likely just leave it be until
the next set of advisories.

DES
 
Same on 14.4

Code: 
> uname -a

FreeBSD planet 14.4-RELEASE-p7 FreeBSD 14.4-RELEASE-p7 #0 -dirty: Tue Jun 30 08:53:56 UTC 2026     root@amd64-builder.daemonology.net:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64


Erichans said:
It is the unfortunate result of operator error when submitting the patches to the freebsd-update build server. Since only the metadata is affected, and only for amd64, we will most likely just leave it be until the next set of advisories. DES
Click to expand...

Would have expected better than this from FreeBSD devs, epically bad level of quality control 🤷‍♂️
 
Oh, I am dirty too. Gotta take a bath 😂

Code: 
$ uname -a
FreeBSD freebsd.home.arpa 14.4-RELEASE-p7 FreeBSD 14.4-RELEASE-p7 #0 -dirty: Tue Jun 30 08:53:56 UTC 2026     root@amd64-builder.daemonology.net:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64
 
No here
14:17 [pkg:0] %> uname -a
FreeBSD MOON-BSD 15.1-RELEASE-p1 FreeBSD 15.1-RELEASE-p1 releng/15.1-n283582-0f691888dc56 GENERIC amd64
14:17 [pkg:0] %> freebsd-version -kru
15.1-RELEASE-p1
15.1-RELEASE-p1
15.1-RELEASE-p1
(pkg:0 It serves as an indicator of whether upgrades are needed.)
 
fjdlr said:
No here
14:17 [pkg:0] %> uname -a
FreeBSD MOON-BSD 15.1-RELEASE-p1 FreeBSD 15.1-RELEASE-p1 releng/15.1-n283582-0f691888dc56 GENERIC amd64
14:17 [pkg:0] %> freebsd-version -kru
15.1-RELEASE-p1
15.1-RELEASE-p1
15.1-RELEASE-p1
(pkg:0 It serves as an indicator of whether upgrades are needed.)
Click to expand...
Did you convert to pkgbase? If so that's why; the problem is only related to freebsd-update.
 
You must log in or register to reply here.
Back
Top