Build date: 1751407202 - Tue Jul  1 22:00:02 UTC 2025
Build cvs date: 1751401033 - Tue Jul  1 20:17:13 UTC 2025
Build id: 2025-07-02.1
Build tags: amd64-regress sysupgrade

Applied the following diff(s):
/home/anton/tmp/robsd/src-sys-em.diff
/home/anton/tmp/robsd/src-sys-uhidev-sispm.diff
/home/anton/tmp/robsd/src-sysupgrade.diff

P lib/libcrypto/asn1/t_x509.c
P lib/libcrypto/man/X509_print_ex.3
P lib/libcrypto/x509/x509.h
P regress/usr.bin/mandoc/man/blank/line.in
P regress/usr.bin/mandoc/man/blank/line.out_ascii
U regress/usr.bin/mandoc/man/blank/line.out_lint
P regress/usr.bin/mandoc/mdoc/Bx/args.in
P regress/usr.bin/mandoc/mdoc/Bx/args.out_ascii
P regress/usr.bin/mandoc/mdoc/Bx/args.out_markdown
P regress/usr.bin/mandoc/mdoc/Lk/font.out_ascii
P regress/usr.bin/mandoc/mdoc/Lk/link.out_ascii
P regress/usr.bin/mandoc/mdoc/Lk/noarg.out_ascii
P sys/arch/arm64/arm64/cpu.c
P sys/arch/arm64/include/armreg.h
P usr.bin/mandoc/man_validate.c
P usr.bin/mandoc/mdoc_man.c
P usr.bin/mandoc/mdoc_term.c
P usr.bin/tmux/tmux.1
M usr.sbin/bgpd/session.c
P usr.sbin/rpki-client/cert.c

commit wrrSXQCWFQWcPUyW
Author: schwarze
Date: 2025/07/01 20:17:13

  test .br before first .SH; related to man_validate.c rev. 1.130

  regress/usr.bin/mandoc/man/blank/line.in
  regress/usr.bin/mandoc/man/blank/line.out_ascii
  regress/usr.bin/mandoc/man/blank/line.out_lint

commit kkSAEFOHoWadqOPz
Author: schwarze
Date: 2025/07/01 20:06:13

  Ignore .br before the first .SH.
  For example, this occurs in the pod2man(1) preamble, which resulted in an
  additional, bogus blank line before the NAME section in all Perl manuals.
  This change makes output compatible with groff-1.23.

  usr.bin/mandoc/man_validate.c

commit 2ovqtFSPhai2P4dG
Author: schwarze
Date: 2025/07/01 19:31:52

  test unusual second arguments to .Bx

  regress/usr.bin/mandoc/mdoc/Bx/args.in
  regress/usr.bin/mandoc/mdoc/Bx/args.out_ascii
  regress/usr.bin/mandoc/mdoc/Bx/args.out_markdown

commit EVK1IB6sprnJzbuO
Author: tb
Date: 2025/07/01 19:12:08

  Use cert_parse_extensions() from cert_parse_ee_cert()

  Use the new helper for extension parsing from cert_parse_ee_cert() and
  delete the now redundant extension parsing. In particular we now parse
  and check the certificate policy for EE certs.

  Requiring that cert policies are actually present will come after
  completing the parsing switch in cert_parse_extensions().

  ok job

  usr.sbin/rpki-client/cert.c

commit DUBaHPfVCM6nX2Wk
Author: tb
Date: 2025/07/01 19:09:30

  rpki-client: split extension parsing out of cert_parse_pre()

  Extract a cert_parse_extensions() helper from cert_parse_pre() so it
  can be shared with cert_parse_ee_cert() as well. I haven't hooked this
  into cert_parse_ee_cert() yet because that makes the diff messy. This
  will be the next step.

  ok job

  usr.sbin/rpki-client/cert.c

commit aVyh9IzdnAyrgpNe
Author: schwarze
Date: 2025/07/01 16:41:53

  catch up with the .Lk formatting change in mdoc_term.c rev. 1.284

  regress/usr.bin/mandoc/mdoc/Lk/font.out_ascii
  regress/usr.bin/mandoc/mdoc/Lk/link.out_ascii
  regress/usr.bin/mandoc/mdoc/Lk/noarg.out_ascii

commit 75D62GOrq5NGnCpr
Author: schwarze
Date: 2025/07/01 16:38:21

  Stop setting the .Lk URI in bold font.

  The main reason for this change is compatibility with groff-1.23,
  which did the same change in

  groff commit e083b3df gbranden@ Sep 15, 2022
  [mdoc]: Add internal string `doc-Lk-font`.
  Use roman instead of (Courier) bold.

  This makes sense from a semantical perspective: a URI is not
  something typically associated with bold font (importance, seriousness,
  or syntactical keywords).  It also makes sense from a presentational
  perspective: a URI already stands out by its scheme:// prefix, does
  not need additional typographical emphasis, and may be long, in
  which case using bold font can look awkwardly heavy.

  There is no particular Unix or BSD tradition to pay deference to.
  It appears the .Lk macro was invented by Werner Lemberg here:

  groff commit d8e29a60 wl@ Sep 30, 2000
  commit message: "internal update"

  So it is unclear to me why bold font was chosen in the first place.

  Not using bold font also agrees better with how groff_man(7) has
  always been formatting URIs since the inception of the (former) .URL
  macro in this commit:

  groff commit 25992962 wl@ Jan 15, 2007
  tmac/an-ext.tmac: New file, containing extension macros

  usr.bin/mandoc/mdoc_man.c
  usr.bin/mandoc/mdoc_term.c

commit F31DT6eVLBssBowO
Author: dlg
Date: 2025/07/01 11:10:36

  report the AMU feature

  ok kettenis@

  sys/arch/arm64/arm64/cpu.c
  sys/arch/arm64/include/armreg.h

commit vAll1OjrBZdJ2JGB
Author: jsg
Date: 2025/07/01 08:54:50

  new sentence, new line

  usr.bin/tmux/tmux.1

commit 64yTy7qbbmXwh1fV
Author: tb
Date: 2025/07/01 06:47:56

  X509_print_ex.3: document X509_FLAG_NO_IDS

  ok job kenjiro

  lib/libcrypto/man/X509_print_ex.3

commit lVJkjb0iP0hrDjCP
Author: tb
Date: 2025/07/01 06:46:39

  X509_print: emit UIDs unless X509_FLAG_NO_IDS is set

  issuerUID and subjectUID are a curiosity introduced in X.509v2 before
  extensions were a thing. Their purpose is to help distinguishing certs
  with identical subject. They are rarely used and are MUST NOT use in
  the CA/BF baseline requirements. They do occasionally show up in test
  certificates and it is confusing that openssl x509 silently ignores
  them. Their encoding also makes them relatively hard to spot in the
  output of asn1 parsing tools.

  The output is identical to OpenSSL < 3 and BoringSSL, but due to some
  weird tweaks added leading up to OpenSSL 3 their output is no longer
  compatible with that. It is not entirely correct anyway. Since it is
  a (not further specified) bit string, you shouldn't be ignoring its
  unused bits...

  The X509_FLAG_NO_IDS flag has no effect for CSRs.

  discussed with beck
  ok job kenjiro (on an earlier version)

  lib/libcrypto/asn1/t_x509.c

commit CfC10veYqm0Kn9s1
Author: tb
Date: 2025/07/01 06:35:16

  x509.h: provide X509_FLAG_NO_IDS

  lib/libcrypto/x509/x509.h


P lib/mesa/mk/libgbm/Makefile

commit y8ofY13sEc8xBEkS
Author: jsg
Date: 2025/07/01 12:00:58

  move -lpthread out of a group so ld.bfd on sparc64 will create a NEEDED
  entry for it

  avoids undefined references to pthread_create, pthread_detach,
  pthread_join, that broke the build of qt5/qtbase on sparc64

  reported-by and ok tb@

  lib/mesa/mk/libgbm/Makefile