Freebsd 15.1. -p1 dirty ???

[mer]

The dirty comes from git and means changes that are not commited. Seems like someone or the build script just applied the patch against the git revision for 15.1 and then compiles, without doing a git commit. It's harmless but feels... dirty.

gitglossary(7)

"How do you like your git commits?"
"Dirty, like my martinis"

 

[bakul]

Yes, Re: 15.1-RELEASE-p1 has dirty tag set?:

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

This is not quite true:

$ uname -v
FreeBSD 15.0-RELEASE-p11 #0 -dirty: Tue Jun 30 03:40:34 UTC 2026 root@arm64-builder.daemonology.net:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC

 

[mer]

This is not quite true:

I'm guessing that 15.0-p11 changes were committed at the same time as 15.1-p1 changes so the same mistake was made, likely by the same person.

Why am I guessing that? Because 15.0-p10 kernel does not say "dirty".

 

[ondra_knezour]

I'm guessing that 15.0-p11 changes were committed at the same time as 15.1-p1 changes so the same mistake was made, likely by the same person.

Why am I guessing that? Because 15.0-p10 kernel does not say "dirty".

I would guess that "not true" in post you reply to regards the only amd64 part in DES's message.

 

[mer]

I would guess that "not true" in post you reply to regards the only amd64 part in DES's message.

I would guess that DES message was talking about 15.1 and bakul's post was about about 15.0-p11. Why even bring this up? -dirty has been explained (rbranco ) 15.0-p11 happened same as 15.1-p1 so same problem with the process.

 

[ondra_knezour]

My line of thought was

...and only for amd64...

... not quite true... -dirty ...arm64.aarch64/sys/GENERIC

 

[rmomota]

I see it too, also the latest version 15.0 before I upgraded has the same symptom.
After upgrade my wayfire desktop environment does not work anymore.
good I still have xfce4 as a backup environment that still work

update:
it's a SDDM bug not wayfire problem.