Add pkg-message and UPDATING

Update UPDATING as well.

I am considering also add this into UPDATING as well as in pkg-message: https://wrapper.tanukisoftware.com/doc/english/release-notes.html#3.6.0

In D53121#1213424, @otis wrote:

This also deserves a short notice in UPDATING.

Bugzilla does not contain any issues that ignoretime does not work. Weird, not never obviously used.

Simple patch (untested):

@@ -218,6 +218,11 @@
 auth_timeok(login_cap_t *lc, time_t t)
 {
     int     rc = 1; /* Default is ok */
+
+    /* Bypass time restrictions if ignoretime is set */
+    if (lc != NULL && login_getcapbool(lc, "ignoretime", 0)) {
+        return rc;
+    }

In D52991#1212123, @glebius wrote:

If it ever existed it existed in lib/libutil/login_ok.c and lib/libutil/login_times.c. Even the original import to FreeBSD does mention ignoretime.

In D52991#1211973, @otis wrote:

I can't find any references to these in sources, indeed.

Smeone from src should approve as well. Other than that, LGTM.

Anyone willing to review? This is a simple cleanup.

Any objections? Patch has been provided by upstream (maintainer) and improved by me.

Waitling for @pi, if we miss quarterly deadline I will MFH it.

Add changelog

Hope to hear from pi@ soon. This tool helped me to migrate a lot of accounts with ease.

In D52303#1196821, @jrtc27 wrote:

It does appear both macOS and GNU date support -Iseconds. However, my concern with this change is that such timestamps are rather uglier and less human-readable, which is less of a problem for build system messages but more so for uname. I note that Linux uses LC_ALL=C date output for its uname, running uname -a on an Ubuntu system.

Drop PORTREVISION

Bump revision

Example from Proxmox:

root@pve-1:~# uname -a
Linux pve-1.ppmd.siemens.net 6.14.8-2-pve #1 SMP PREEMPT_DYNAMIC PMX 6.14.8-2 (2025-07-22T10:04Z) x86_64 GNU/Linux

Just update the port

In D52303#1196821, @jrtc27 wrote:

It does appear both macOS and GNU date support -Iseconds. However, my concern with this change is that such timestamps are rather uglier and less human-readable, which is less of a problem for build system messages but more so for uname. I note that Linux uses LC_ALL=C date output for its uname, running uname -a on an Ubuntu system.

In D52303#1196819, @cperciva wrote:

In D52303#1196813, @michaelo wrote:

Interesting...I'd like to know how it could break it.

Well, date -I is not POSIX. So it might produce no output, or an odd error message instead.

Update UPDATING

In D52303#1196812, @cperciva wrote:

I like the idea, but this might break on cross-building from non-FreeBSD systems. @jrtc27 can you comment on this? I know you do such things.

Folks, any opinion on this? This is a readability and internationalization improvement.

Just noticed that I should update UPDATING as well.

Maintainer timeout is approaching, any opinion here?

Maintainers, any objections?

In D52329#1195479, @markj wrote:

In D52329#1195478, @michaelo wrote:

@markj , would you mind to backport it as well? Very useful!

Yes, that's what "MFC after" in the commit log message refers to.

@markj , would you mind to backport it as well? Very useful!

I am fine with the change as long as this is met: https://reviews.freebsd.org/D52158#1192019

Nice idea, hopefully this will be backported.

I agree with @jlduran, all three should be covered. I applied the patch locally and the issue is gone.

Already removed by @rene.

@des done

Waiting for a format approval from mentors.

In D52304#1194232, @ziaee wrote:

This is good with me since compression is stated as a default earlier in the page, but like @diizzy said, a more specific commit message for our readers would be expedient, like:

bsdinstall/zfsboot examples: zap compress comments

Remove compression comments from examples as zroot datasets are compressed by default since FreeBSD 1?.? [0].

[0] {$COMMITID}

add ref to default compression

In D52304#1194192, @diizzy wrote:

In D52304#1194191, @michaelo wrote:

In D52304#1194190, @diizzy wrote:

You might want to add a refence?

You mean https://github.com/freebsd/freebsd-src/blob/fb37e38fbe99039a479520b4b596f4bfc04e2a88/usr.sbin/bsdinstall/scripts/zfsboot#L52-L54?

More like historical, this has been the case since the inital commit of zfsboot
https://github.com/freebsd/freebsd-src/blob/cd88b8869f9b2c280b1de02608f52fdf497b4cb1/usr.sbin/bsdinstall/scripts/zfsboot

In D52304#1194190, @diizzy wrote:

You might want to add a refence?

Used the following search pattern: grep -r -e '$(date' -e '$( date' -e 'date' -e 'C date' --exclude '**/tests/**' --exclude '**/sys/contrib/**' --exclude '**/contrib/**' --exclude '**/tools/**' --exclude '**/crypto/**' . --color

@mikael, exp-run is complete. No related failures. Are we good to approve and merge this one?

Folks, any opinion on this? Waiting for the port maintainer...

Now waiting for the maintainer...

Generalize patching

You also forgot to delete the expired distrusted one.