BSD Commit Log Search

   update to py3-cryptodome-4.0.1

   update to py3-passlib-1.9.4

   update to harper-2.13.0, from Alvar Penning (maintainer)

   Aligne these patches.

   Reduce diffs with upstreams. Comments and other aux files with
   no impact on the code. Most remaining diffs needs to be sent upstream.

   Add PORTROACH ignore:1, kf5 is no longer maintained by KDE

   Update to py3-pypdf-6.21.1.

   It's spelled x11-ssh-askpass

   Update to ibus-typing-booster-2.31.2.

   Update to libnotify-0.8.9.

   New home for ssh-ask-pass

   pkgconf regress: bump version to 3.0.9

   pkgconf: bump version to 3.0.9

   The introduction of stack protector support for gcc 4 on alpha some 14 years
   ago required the logical stack frame to be laid out in reverse order (this is
   a requirement of the MI stack protector code in gcc).

   This move, however, forgot to update the preconditions of the "*adddi_fp_hack"
   insn, which is used to perform specific stack or frame pointer adjustment in
   the prologue.

   The change in frame layout would make its preconditions never allow it to be
   used anymore, causing internal compiler errors when attempting to compile
   routines with more than about 32KB of locals.

   Such code appears to be rare enough that this issue hasn't been noticed until
   very recently by martijn@.

   ldd(1) has traditionally printed the command: header itself, before
   starting the program with LD_TRACE_LOADED_OBJECTS.  There are various
   circumstances where the program does not properly trace, so the output
   looks weird.  It is also different from the manual "env LD_TRACE_LOADED_OBJECTS="
   method.  This change makes ld.so print the command header itself.
   ok kettenis

   ld.so knows whether tracing is happening earlier, so the pledge
   "stdio rpath" can be moved upwards.
   ok kettenis

   using pledge execpromises here is pointless because ldd is just a wrapper
   around setenv LD_TRACE_LOADED_OBJECTS.  Because the setenv method is
   available to everyone, ld.so has to protect the process itself.
   ok kettenis

   libc initialization now aborts if a setuid/setgid program does not
   have the global variable _permit_setugid declaring that it is setuid/setgid.
   The more important packages have been fixed, and the long tail will be
   fixed by people who encounter this problem.
   ok sthen

   sys/alpha: allign _STACKALIGNBYTES with GCC expectation

   tested by martijn@ and miod@

   OK: deraadt@

   archivers/libarchive: update to 3.8.10

   update to gitlab-cli 1.123.0

   update to github-cli 2.102.0

   Handle empty USB HID responses that could otherwise lead to out of bounds
   memcpy().

   Report and diff from Acts1631.

   ok deraadt@

   update

   Update to xterm 412

   Update to libXtst 1.2.6

   Update to libXrender 0.9.13

   Update to libXpm 3.5.20

   Update to libXi 1.8.4

   Update to libX11 1.8.14