avr-libc: fix PLIST with latest doxygen and depend on it

Bump PKGREVISION

(wiz)

doc: Updated comms/openobex to 1.7.2nb1

(wiz)

openobex: fix PLIST for latest doxygen, and depend on it

Bump PKGREVISION.

(wiz)

SDL2_sound: fix fetch stage

(wiz)

gtexinfo: explicitly enable perl XS

The configure check for enabling throws an error on NetBSD and
fails completely on macOS, perhaps this avoids the macOS problem.

(wiz)

cairo-gobject: fix some pkglint

(wiz)

htop: Fix options for selecting curses type

Users can now select ncurses for enabling unicode characters on NetBSD.
It was not sufficient (or even correct, most likely) to use "wide-curses"
for this.

(kim)

cairo: make buildlink3 logic for xcb match options.mk

(wiz)

cairo: turn off xcb on macOS too by default

since it implies x11

(wiz)

texlive-collection-latexextra: add tex-orcidlink

(markd)

add tex-orcidlink{,-doc}

(markd)

print: add tex-orcidlink{,-doc}

(markd)

tex-orcidlink{,-doc}: add version 1.0.4

This package provides a command to insert the ORCiD logo, which
is hyperlinked to the URL of the researcher whose iD was
specified.

(markd)

libkscreen: note required dependency on plasma-wayland-protocols

(markd)

Take MAINTAINER for highlight.

(schmonz)

Note libhighlight, highlight, p5-highlight updates.

(schmonz)

Update to 4.3. From the changelog:

- added support for Carbon
- added support for Fortran77 star comments comments (#208)
- added support for PowerShell block comments (#210)
- fixed Python formatted string pattern (#212)
- added new shell completion generation script (#137)
- W32: fixed Windows compilation headers (#138)

(schmonz)

doc: Updated filesystems/tahoe-lafs to 1.18.0

(gdt)

filesystems/tahoe-lafs: Update to 1.18.0

packaging changes: Drop explanation about python 2.7 being supported
by upstream and $MAINTAINER not wanting to deal with dependencies.

Upstream NEWS:

Release 1.18.0 (2022-10-02)
'''''''''''''''''''''''''''

Backwards Incompatible Changes
------------------------------

- Python 3.6 is no longer supported, as it has reached end-of-life and is no longer receiving security updates. (`#3865 <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3865>`_)
- Python 3.7 or later is now required; Python 2 is no longer supported. (`#3873 <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3873>`_)
- Share corruption reports stored on disk are now always encoded in UTF-8. (`#3879 <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3879>`_)
- Record both the PID and the process creation-time:

  a new kind of pidfile in `running.process` records both
  the PID and the creation-time of the process. This facilitates
  automatic discovery of a "stale" pidfile that points to a
  currently-running process. If the recorded creation-time matches
  the creation-time of the running process, then it is a still-running
  `tahoe run` process. Otherwise, the file is stale.

  The `twistd.pid` file is no longer present. (`#3926 <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3926>`_)

Features
--------

- The implementation of SDMF and MDMF (mutables) now requires RSA keys to be exactly 2048 bits, aligning them with the specification.

  Some code existed to allow tests to shorten this and it's
  conceptually possible a modified client produced mutables
  with different key-sizes. However, the spec says that they
  must be 2048 bits. If you happen to have a capability with
  a key-size different from 2048 you may use 1.17.1 or earlier
  to read the content. (`#3828 <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3828>`_)
- "make" based release automation (`#3846 <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3846>`_)

(gdt)

Updated net/grpc, net/py-grpcio, net/py-grpcio-testing, net/py-grpcio-tools

(adam)

grpc: updated to 1.49.1

v1.49.1

All

Update protobuf to v21.6 on 1.49.x.

v1.49.0

Core

Backport: "stabilize the C2P resolver URI scheme" to v1.49.x.
Bump core version.
Update OpenCensus to HEAD.
Update protobuf submodule to 3.21.5.
Update third_party/protobuf to 3.21.4.
[core] Remove GRPC_INITIAL_METADATA_CORKED flag.
HTTP2: Fix keepalive time throttling.
Use AnyInvocable in EventEngine APIs.

Python

Support Python 3.11
Add type stub generation support to grpcio-tools.

(adam)

dar: fix dar-int32 option build by using DARBITS in PLIST

(nros)

doc: Updated archivers/dar to 2.7.7

(nros)

Update archives/dar to version 2.7.7

Removed patch-a* to use the new
naming convention.
This version requires c++14 so
the patch concerning vector.assign()
missing in sunpro has been removed.
src/libdar/mask_list.hpp could not
be patched and the my_char method
does not exist anywhere in the
sources so the patch has been removed.
This version includes autotools
changes that have AM_LDFLAGS and
looks for getopt in unistd.h.
Added extra buildlink files so that
all deps are found.

Changes from Changelog:

from 2.7.6 to 2.7.7
- added support for sequential reading more of sliced backup, to
  accommodate tape support used with slices (at the opposite of dar_split)
- fixing few typos in doc
- making libdar more tolerant when calls to fadvise fail

from 2.7.5 to 2.7.6
- adding -f option to dar_cp
- adding static version of dar_cp (dar_cp_static) as compilation outcome
- added FAQ for tape usage with dar
- fixing error in libdar header file installation
- fixed bug met when interrupting the creation of a block compressed
  backup (always used by lzo compression and by other algorithm only
  when performing multi-threaded compression)
- typo fixes in documentation
- fixed message in lax mode used to obtain from the user the archive format
  when this information is corrupted in the archive.
- fixing lax mode condition that popped up without being requested
- fixing bug met when reading slice an special block device by mean of
  a symlink
- adapting sanity checks to the case of a backup read from a special
  device in sequential-read mode.
- fixed bug that lead dar to report CRC error while reading a backup
  from a pipe with the help of an isolated catalogue
- adding -V option to dar_split (was using -v) for homogeneity with
  other commands

from 2.7.4 to 2.7.5
- fixed double free error met when deciphering an archive with a
  wrong password/passphrase and when multi-threading is used.

from 2.7.3 to 2.7.4
- fixed excessive context control that led libdar to report a bug
  when an file-system I/O error was returned by the operating system
- fixed mini-digits auto-detection, which only worked when slice number 1
  was present, even if subsequent slices could be used to detect its
  value
- fixed typos and minor incoherence in documentation
- update version information to display libthreadar barrier implementation
  used, info available since its release 1.4.0

from 2.7.2 to 2.7.3
- fixed bug met when restoring files in sequential-read mode and feeding
  the backup to dar on its stdin: When dar had to remove a file that had
  been deleted at the time of the backup since the backup of reference
  was made, dar aborted the restoration reporting it could not skip
  backward on a pipe.
- adding call to kill() then join() in destructor of class slave_thread
  and fichier_libcurl to avoid the risk of SEGFAULT in rare conditions
  under Cygwin (Windows)
- fixed several typos in bug, messages and comments
- fixed script used to build windows binary to match recent cygwin dll
- fix spelling and improved clarity in dar_split messages

from 2.7.1 to 2.7.2
- fixed bug met when a user command returns an error while dar is
  saving fsa attributes of inodes (this conjunction make it an infrequent
  situation)
- fixed typo in documentation
- fixed remaining bug from 2.7.1 met when compiling dar/libdar with a
  compiler (clang-5.0 here) that requires a flag to activate C++14 support
  while complaining (for a good reason) when this flag is passed too while
  compiling C code.
- fixed self reported bug escape.cpp line 858 met when using lzo compression
  or multi-threaded compression while creating a backup to stdout.
- fixed bug met when creating a backup to stdout that lead libdar to corrupt
  data when trying to re-save a file uncompressed due to poor compression
  result
- fixed minor bug met when setting --mincompr to zero and using
  block_compressor (lzo algo or any algo in block compression): empty files
  were reported as truncated due to the lack of block header (compressed
  empty file being stored as an empty file)

from 2.7.0 to 2.7.1
- fixed compilation script to require support for C++14 due to new features
  introduces in 2.7.0 that rely on modern C++ constructions. Updated
  documentation accordingly about this updated requirement.
- fixed missing included header for compilation to suceed under MacOS X
- fixed typo in man page
- adding minor feature: storing the backup root (-R option) in the archive
  to be able to restore 'in place' thanks to the new -ap option that
  sets the -R path to the one stored in the archive.
- merging fixes an enhancements brought by release 2.6.15

from 2.6.x to 2.7.0
- using the truncate system call whenever possible in place of skipping
  back in the archive, when file need to re-save uncompressed,
  or when file has changed while it was read for backup
- improved slice name versus base name error, now substituting (rather than
  just asking the user) the first by the later when else it would lead
  to an execution error.
- auto-detecting min-digits at reading time in complement of the feature
  listed just above
- added the possibility to specify a gnupg key by mean of its key-id in
  addition to the email address it may be associated to, both for
  asymmetrical encryption and archive signing.
- added -b option to dar_split to set the I/O block size
- added -r option to dar_split to limit the transfer rate
- added -c option to dar_split to limit the number of tape to read
- new feature: zstd compression algorithm added
- replaced old and experimental multi-threaded implementation by
  production grade one. -G option may now receive an argument on
  command line for fine tuning. libdar API has been updated
  accordingly.
- added multi-threaded compression when using the new per block
  compression mode, the legacy streaming compression mode is still
  available (see both -G and -z option extended syntax).
- added lz4 compression algorithm.
- removed some deprecated/duplicated old options (--gzip,...)
- enhanced the delta signature calculation providing mean for the user
  to adapt the signature block size in regard to the file's size to
  delta-sig. "--delta sig" option received an extended syntax.
- increased timestamp precision from microsecond to nanosecond when the
  operating system supports it. It is still possible to use configure
  --enable-limit-time-accuracy=us at compilation time to use microsecond
  or even second accuracy even if the OS can support finer precision.
- added argon2 hashing algorithm for key derivation function (kdf) which
  becomes the default if libargon2 is available, else it defaults to sha1
  as for 2.6.x. When argon2 is used, kdf default iteration count is
  reduced to 10,000 (and stays 200,000 with sha1). This can be tuned
  as usual with --kdf-param option.
- adding support for statx() under Linux which let libdar save file's
  birthtime. Unfortunately unlike under BSD systems (FreeBSD, MACoS X,
  and so on), the utime/utimes/timensat call do not set birthtime, so
  you cannot restore birthtime on Linux's unlike under BSD systems
- AES becomes the default when gnupg is used without additional
  algorithm.
- new implementation of the libcurl API use for more efficient reuse of
  established sessions.
- You can now exclude/include per filesystem rather than just sticking
  to the current filesystem or ignoring filesystem boundary. -M option
  can now receive arguments.
- new feature: dar_manager can now change the compression algorithm of
  an existing database.
- Added a benchmark of dar versus tar and rsync for different use cases.
- documentation review, update, cleanup, restructured and beautification.

from 2.6.15 to 2.6.16
- fixed bug met when restoring files in sequential-read mode and feeding
  the backup to dar on its stdin: When dar had to remove a file that had
  been deleted at the time of the backup since the backup of reference
  was made, dar aborted the restoration reporting it could not skip
  backward on a pipe.
- adding call to kill() then join() in destructor of class slave_thread
  and fichier_libcurl to avoid the risk of SEGFAULT in rare conditions
  under Cygwin (Windows)
- fixed bug met when removing tape marks (-at option) and due to poor
  compression, dar skips back to re-save file uncompressed leading to
  self reported bug (due to an error in the sanity check).
- fixing error message display by dar when -y option is used with another
  command (-c/-t/-l/-d/-x/-+/-C)

from 2.6.14 to 2.6.15
- fixed error message formatting error leading message to contain garbage
  in place of system error information.
- fixing bug (internal error) met while trying restoring files and dirs
  without sufficient write permission on the destination directory tree
  to perform the operation.
- adding minor feature to avoid restoring Unix sockets (-au option)
- fixing dar-catalogue.dtd

from 2.6.13 to 2.6.14
- script used to build dar windows binary has been fixed to have the
  official default etc/darrc config file usable and used out of the
  box.
- fixed bug met when removing slices of an old backup located on
  a remote sftp server
- fixed bug in cache layer met when writing sliced backup to a remote
  ftp or sftp repository
- enhancement to the -[ and -] options to work as expected when "DOS"
  formatted text file is provided as a file listing.

from 2.6.12 to 2.6.13
- fixed compilation warning in testing routine (outside libdar and dar)
- due to change in autoconf, the --sysconfdir path (which defaults to
  ${prefix}/etc) was read as an empty string, leading dar to look for
  darrc system file at the root of the filesystem (/darrc)
- fixed bug that should occur in extremely rare conditions (it has been
  discover during 2.7.0 validation process): compression must be used,
  no ciphering, no hashing, file changed at backup time or had a poor
  compression ratio, was not saved at slice boundary, the previous
  entry had an EA saved but no FSA or an unchanged FSA. In such
  conditions are all met, dar tries to resave the file in place, but
  partially or totally overwites the EAs of the previous entry leading
  to archive testing to fail for these EA (though the archive could be
  finished without error).
- fixed bug met when case insensitive mask is requested (-an option)
  and locale of file to restore or backup is not the one the dar binary
  is run with.

from 2.6.11 to 2.6.12
- fixed regression met in 2.6.11 when generating encrypted archives

from 2.6.10 to 2.6.11
- fixing bug in dar_manager libdar part, met when the two oldest entries
  for a file are recorded as unchanged (differential backup).
- fixed typo in dar_manager man page
- updated lax mode to ignore encryption flag found in header and trailer
- fixed two opposite bugs in strong encryption code that annihilated
  each other, by chance
- fixing bug met when merging an archive an re-compressing the data
  with another algorithm that gives a less good result, this condition
  lead the merging operation to fail reporting a CRC mismatch
- improving archive header code to cope with unknown flags

from 2.6.9 to 2.6.10
- update the configure script to handle some undocumented --enable-*
  options that existed but were not expected to be used.
- fixed spelling in darrc comments
- fixed bug in dar_split that could occur in very rare conditions
- fixed EA support build failure due to what seems to be a change
  in Linux kernel header
- fixed symbol conflict with s_host of in.h on omniOS platform

from 2.6.8 to 2.6.9
- fixed some obvious bug when running doxygen (inlined documentation)
- fixing configure.ac to detect xattr.h system header when it is
  located in /usr/include/sys like under Alpine Linux distro (musl libc)
- fixed typo in symbol name "libdar.archive_summary" in python binding
- fixed bug met when testing an archive in sequential-read mode leading
  dar to skip back to test deleted inode which is useless and may lead
  to failure if the archive is read from a pipe
- adding *.zst files as excluded from compression when using the
  predefined target "compress-exclusion"
- fixed text diagram alignment in documentation and spelling errors
- moving date_past_N_days script to doc/sample with other scripts

from 2.6.7 to 2.6.8
- fixing bug leading binary delta failed to be read from an archive in
  some quite rare condition.
- fixed bug that was not listing file with delta path when filtering out
  unsaved inodes
- updated source package for the python binding tutorial document be
  installed with the rest of the documentation
- adding date_past_N_days helper script to backup only files later than
  "today minus N days"
- incorporated the "args" support built script in dar source package

from 2.6.6 to 2.6.7
- fixing shell_interaction_emulator class declaration to avoid compilation
  errors and warning under MacOS
- fixed bug: dar failed creating an archive on its standard output
  reporting the error message "Skipping backward is not possible on a pipe"
- new feature: added python binding to libdar!

from 2.6.5 to 2.6.6
- fixing script that builds windows binary packages to include missing
  cygwin libraries
- fixing bug: dar_manager batch command (-@ option) contains a inverted
  test in a sanity check, leading the execution to systematically abort
  reporting an internal error message.
- fixed message error type when asymmetrical encryption is requested and
  gpgme has not been activated at compilation time
- fixed dar/libdar behavior when gpg binary is not available and gpgme
  has been activated at compilation time. Instead of aborting, dar now
  signal the gpgme error and proposes to retry initialization without
  gpgme support. This makes sense for dar_static binary which stays
  usable in that context when all options have been activated

from 2.6.4 to 2.6.5
- fixed bug: dar crashed when the HOME environment variable was not
  defined (for example running dar from crontab)
- removed useless skip() in cache layer
- cache layer improvement, flushing write pending data before asking
  lower layer about skippability
- fixed bug met when several consecutive compressed files were asked to
  be compressed and failed getting reduced in size by libdar. In that
  situation as expected, libdar tries to skip backward and stores the
  file uncompressed. However the cache layer was introducing an offset
  of a few bytes leading the next file to be written over the end of the
  previous one, which dar reported as data corruption when testing the
  archive.
- updating licensing information with the new address of the FSF
- clarifying message about possibly truncated filename returned by the
  operating system

from 2.6.3 to 2.6.4
- fixed display bug indicating delta signatures were about to be
  calculated even when this was not the case.
- updating dar man page about the fact aes256 replaced blowfish as
  the default strong encryption algorithm
- bug fix: -D option used at creation time was not adding escape mark
  of skipped directories. This lead the empty directories that would
  replace each skipped one to be inaccessible and unable to be restored
  only in sequential read mode (it worked as expected in direct mode)

from 2.6.2 to 2.6.3
- feature enhancement: added option to specify the block size used to
  create delta signatures.
- feature enhancement: added the ability to provide login for sftp/ftp
  remote access, that contain @ and other special characters.
- fixed bug in dar_xform, leading dar not finding source archive if
  destination was not placed in the same directory as source

from 2.6.1 to 2.6.2
- fixed incoherence in documentation
- updating in-lined help information (-h option)
- fixed unexpected behavior of the dar command-line filtering mechanism
  met when the provided path to -P or -g options was ending with a slash
- renaming 'path operator + (std::string)' as method append() to avoid
  compiler using it when a std::string need first to be converted to path
  before adding it to an existing path.
- adding check test to detect when path::append() is used to add a path
  instead of a filename to an existing path object.
- adding a warning when restoring a Unix socket if the path to that
  socket is larger than what the sockaddr_un system structure can handle
- fixing bug due to Linux system removing file capabilities (stored as
  EA) when file ownership is changed. Though restoring EA after ownership
  may lead to the impossibility to restore them due to lack of permission
  when dar/libdar is not run as root. Thus we try restoring EA a second
  time after ownership restoration. This is not efficient but restores
  the file as close as possible to their original state whatever
  permission dar has been granted for a restoration operation.

from 2.6.0 to 2.6.1
- fixed error in man page
- fixing bug in the routine removing files for local filesystem, used at
  archive creation time to remove an existing archive (after user
  confirmation), or at restoration time used to remove file that had been
  removed since the archive of reference was done. The file to remove was
  always removed from the current directory (missing the path part), most
  of the time this was leading to the error message "Error removing file
  ...: Not such file or directory". It could also lead to incorrectly
  removing files (not directory) located in the directory from which
  dar was run.
- fixing bug met while repairing an archive containing delta signature
  for unsaved files
- merging patch from ballsystemlord updating list of file extension
  not to compress (see compress-exclusion defined in /etc/darrc)
- review cat_delta_signature implementation in order to be able to fix
  memory consumption problem when delta signature are used
- fixed missing mark for data CRC when the data is a delta patch, leading
  sequential reading to fail when a delta patch was encountered
- fixed bug in XML output about deleted entries
- fixed XML output to be identical to the one of dar 2.5.x for deleted
  entries.
- Adding the deleted date in 'mtime' field for deleted entries in XML
  output
- fixing bug in xz/lzma routine wrongly reporting internal error when
  corrupted data was met
- fixed code for compilation with clang to succeed (it concerns MAC OS X
  in particular)
- fixed inconsistencies in libdar API that avoided gdar to compile with
  libdar released in 2.6.0

from 2.5.x to 2.6.0
- new feature: support for binary delta in incremental/differential backups
  (relying on librsync)
- new feature: support ftp/sftp to read an archive from a cloud storage.
  (relying on libcurl)
  reading is optimized to not transfer a whole slice but only the needed
  part to proceed to the operation (restoration, listing, and so on)
- new feature: support ftp/sftp to write an archive eventually with hash
  files to a remote cloud storage (relying on libcurl)
- modified behavior: While creating a single sliced archive, DUC file is
  now executed unless user interrupted dar/libdar. This to stay coherent
  with multi sliced archive behavior
- new feature: display filters nature (-vmasks option)
- new feature: follow some symlinks as defined by the --ignored-as-symlink
  option
- new feature: one can define the compression algorithm a dar_manager
  database will use. This choice is only available at database creation
  using the new dar_manager's -z option. In particular "-z none" can be
  used to avoid using compression at all
- repair mode added to re-create a completed archive (suitable for direct
  access mode and merging) from an interrupted one due to lack of disk
  space, power outage or other reasons leading to similar problem.
- Dar can now only save metadata inode change without re-saving the whole
  file if its data has not changed. Dar_manager also handle this by
  restoring the full backup and then the inode metadata only when
  necessary.
- In regard to previous point, if you want to keep having dar saving the
  data when only metadata has changed use --modified-data-detection option
- moved dar_slave code into libdar as class libdar::libdar_slave
- moved dar_xform code into libdar as class libdar::libdar_xform
- added libdar_slave and libdar_xform in libdar API
- modified dar_xform and dar_slave to rely on new libdar API
- API: simplified user_interface class
- API: using std::shared_ptr and std::unique_ptr to explicitly show the
  ownership of the given pointed objects (C++11 standard)
- API: simplified class archive to only require user_interaction at
  object construction time
- API: simplified class database to only require user_interaction at
  object construction time
- API: making enum crypto_algo an C++11 "enum class" type
- security refresh: default crypto algo is now AES256. As you do not
  need anymore since 2.5.0 to specify the -K option when reading an
  archive this should not bring any backward compatibility issue
- security refresh: adding salt per archive (one is still present per
  block inside an archive)
- security refresh/new feature: adding option --kdf-param to define
  the iteration count for key derivation, which now defaults to 200,000
  and hash algorithm used to derived key, still using sha1 by default
- slide effect of previous feature due to starvation of free letters
  to add a new command, the -T option with argument is no more
  available, one need to provide explicitly the desired argument
- security refresh: improving seed randomization for the pseudo-random
  generator used in elastic buffers
- feature enhancement: activate needed Linux capabilities in the
  "effective" set if it is permitted but not effective. This concerns
  cap_chown at restoration time, cap_fchown for furtive read mode,
  cap_linux_immutable to restore the immutable flag, and cap_sys_
  resource to set some linux FSA. This let one set the capabilities
  for dar binary only in the "permitted" set, capabilities will then be
  allowed only for users having them in the "inheritable" set of their
  calling process (usually a shell), without root privilege need.
- the ./configure --enable-mode option now defaults to 64, which
  will setup a libdar64 in place of infinint based libdar by default.
  You can still build a infinint based libdar by passing
  --enable-mode=infinint to the ./configure script.

from 2.5.21 to 2.5.22
- removed useless skip() in cache layer
- cache layer improvement, flushing write pending data before asking
  lower layer about skippability
- fixed bug met when several consecutive compressed files were asked to
  be compressed and failed getting reduced in size by libdar. In that
  situation as expected, libdar tries to skip backward and stores the
  file uncompressed. However the cache layer was introducing an offset
  of a few bytes leading the next file to be written over the end of the
  previous one, which dar reported as data corruption when testing the
  archive.
- updating licensing information with the new address of the FSF
- fixing bug met when restoring file having FSA but EA and overwriting
  an existing file in filesystem
- clarifying message about possibly truncated filename returned by the
  operating system

from 2.5.20 to 2.5.21
- bug fix: -D option used at creation time was not adding escape mark
  of skipped directories. This lead the empty directories that would
  replace each skipped one to be inaccessible and unable to be restored
  only in sequential read mode (it worked as expected in direct mode)

from 2.5.19 to 2.5.20
- adding a warning when restoring a unix socket if the path to that
  socket is larger than what the sockaddr_un system structure can handle
- fixing bug due to Linux system removing file capabilities (stored as
  EA) when file ownership is changed. Though restoring EA after ownership
  may lead to the impossibility to restore them due to lack of permission
  when dar/libdar is not run as root. Thus we try restoring EA a second
  time after ownership restoration. This is not efficient but restores
  the file as close as possible to their original state whatever
  permission dar has been granted for a restoration operation.
- fixing compilation problem with recent clang++ compiler

from 2.5.18 to 2.5.19
- fixed compilation issue on system that to not have ENOATTR defined
- fixed compilation warning about deprecated dynamic exception
  specifications in C++11
- fixing bug in xz/lzma routine wrongly reporting internal error when
  corrupted data was met
- fixed compilation warning with gcc about deprecated readdir_r system
  call

from 2.5.17 to 2.5.18
- fixed compilation issue in context where EA are not supported
- fixed typo in dar man page (--sequential-mode in place of
  --sequential-read)
- moved the "no EA support warning" trigger when restoring an archive
  later in the EA restoration process, in order to have the possibility
  thanks to the -u "*" option to restore an archive containing EA using a
  dar/libdar without EA support activated at compilation time,
- at restoration time, avoiding issuing an "EA are about to be
  overwritten" warning when the in place file has in fact not only
  one EA set.

from 2.5.16 to 2.5.17
- bug fix: dar failed to restore EA when file permission to restore
  did not included user write access. Fix consists in temporarily
  adding user write access in order to restore EA and removing this
  extra permission afterward if necessary
- updated FAQ
- fixed typos in dar man page
- fixed bug met when writing slices to a read-only filesystem
- fixed compilation problem under Solaris
- fixed typos in dar man page
- bug fix: self reporting bug in filtre.cpp line 2932 or 2925 depending
  or dar's version (report occurs in a normal but rare condition that
  was not imagined by developer, leading dar to abort the backup)
- bug fix: wrong evaluation of possibility to seek backward in the
  escape layer (layer managing tape marks) which lead to useless but
  harlmess skip trials in some rare conditions.

from 2.5.15 to 2.5.16
- bug fix: while rechecking sparse file (-ah option) during a merging
  operation, dar wrongly reported CRC mismatch for saved plain files
- fixed man page about sparse-file handling while merging: To remove
  sparse file datastructure during a merging operation you need to
  set --sparse-file-min-size to a valuer larger than all file sizes
  contained in the archive (for example 1E for one exabyte)
- bug fix: met when using compression and creating the archive to
  dar's standard output (ssh) and leading files to be corrupted in the
  archive and reported as such.
- optimisation of escape_sequence skippability (avoids trying skipping
  and failing for some corner cases, when we can detect it does even
  not worth trying)

from 2.5.14-bis to 2.5.15
- fixing self report bug message met when trying to create an isolated
  catalogue into a directory that does not exist
- adding slice overwriting verification before creating a isolated
  catalogue, to be coherent with other operations creating an archive
  (backup and merging)
- storage size of compressed files was often wrongly stored in archive
  (shorter than reality), the only impact took place at archive listing
  time where the compression ratio displayed was better than reality
- fixed auto-detected bug condition triggered when -Tslicing is used
  with --sequential-read. Both options are not compatible and have been
  excluded by a nicer message than this auto-detection bug message.

from 2.5.14 to 2.5.14-bis
- avoiding using the syncfs() system call in dar_split when the
  platform does not support it (replacing it by sync() in that case
  for compilation to be successful)

from 2.5.13 to 2.5.14
- made libgcrypt built-in memory guard be initialized before obtaining
  ligcrypt version, to respect libgcrypt usage (but no problem was seen
  nor reported about this inconsistency)
- fixed syntax error in XML listing output (EA_entry and Attributes
  tags)
- fixed typos in dar man page
- Updating Tutorial for restoration
- fixed bugs in dar_split: cygwin support, filedescriptors were not
  explicitly closed at end of execution, allocating buffer on heap
  rather than in the stack for better size flexibility, avoiding buffer
  size to be greater than SSIZE_MAX.
- added -s option to dar_split in order to disable the by default SYNC
  write that was used and which caused poor performance. To keep the
  same behavior as the older dar_split (and its poor performances) you
  need now using -s option.
- dar_split enhancement: added call to syncfs before closing the file
  descriptor in split_output mode
- fixed bug in dar_split that was did not lead dar_split to completely
  fulfill an device before asking for user to change the media when
  used in split_output mode, this was sometimes leading dar reporting
  file as corrupted at dar_split at media boundary.
- added feature in dar_split to show the amount of data written since
  the last media change

from 2.5.12 to 2.5.13
- added -az option to automatically nullify negative dates returned from
  the system in the archive under creation (filesystem is not modified)
- included the birthtime (HFS FSA) into the negative dates handling
- modified behavior: dar now fails upon unknown option instead of warning
  the option is unknown and thus ignored
- bug fix: dar 2.5.12 and below in 2.5.x branch could not read archive
  generated by dar 2.4.x and below (unless in infinint compilation mode)
  when the old archive included a file which date(s) was returned by the
  system as a negative integer at the time of the backup. Note that if
  dar can now read old archive in that particular case, such date stay
  recorded in the dar archive as very far in the future and not in the
  past, because 2.4.x and below blindly assumed the system would always
  return a positive integer as number of second since 1970. Since 2.5.12
  release, when the system provides a negative date the date is assumed
  as zero (Jan 1970) with user agreement.
- fixed missing throw in tools.cpp (exception condition was not reported)

from 2.5.11 to 2.5.12
- documenting in man page the limitation of -[ and -] options concerning
  the maximum line length that could be used in a listing file. This
  limitation was only described in doc/Limitations.html
- dar now aborts if a line exceeding 20479 bytes is met in a listing file
- improved error message issued when a file listing (-[ or -] option) is
  missing for it provides the missing filename in the error message
- improved error message issued when a line of a file listing exceeds
  20479 characters for it display the start of that line
- fixed bug in file listing (-[ option) leading some directories and their
  content to be excluded in a somehow rare condition
- improved behavior when dar reads a negative date. Instead of aborting
  it now asks the user if it can substitute such value by zero
- improved behavior when dar is asked to read an archive located in a
  directory that does not exist. DUC file passed to -E option is now
  properly run in that case too and has the possibility for example to
  create that directory and download requested file

from 2.5.10 to 2.5.11
- minor feature: displays the archive header which is never ciphered and
  aborts. This feature is activated while listing archive content and
  adding the -aheader option. This brings the side effect to invert two
  lines in the archive summary (dar -l archive -q) "catalogue size" and
  "user comment".
- adding date format info for -w option in "dar_manager -h" usage help
- fixed several mistakes in tools.cpp leading compilation to fail under
  certain environments
- fixed a typo in filesystem.cpp and portability issue that lead
  compilation to fail under openbsd 6.0
- fixed bug in the filtering mechanism relying on file listing (-[ and
  -] options) that could not find an entry in the listing upon certain
  condition leading a file not being excluded as requested or not
  included as requested

from 2.5.9 to 2.5.10
- fixed bug: -r option (only more recent overwriting policy) was
  considering a file to be more recent when it had the exact same date as
  the file in place.
- updating documentation about requirements for compiling dar from sources
- fixed bug: bug met when restoring of a file that has the immutable
  flag set. Dar/libdar failed restoring such file in the context of
  differential/incremental backup. The fix consists of the removal of the
  immutable flag from filesystem before restoring the new version of the
  file's data, then setting back the immutable flag afterward.
- updating FAQ with description of the way dar uses lzo compression
  compared to the lzop program
- fixed bug: aborting an archive was leading to an unreadable archive in
  direct mode, most of the time when strong encryption was used
- minor new feature: added two flavors of lzo algorithm: lzop-1 and lzop-3
  in order to match compression levels 1 and 3 of the lzop command

from 2.5.8 to 2.5.9
- fixed typos in documentation about dar internal use of symmetric
  encryption
- fixed bug: merging operation could wrongly melt different unrelated hard
  linked inodes when merging using an archive which results from a previous
  merging operation.
- fixed bug: aborting an archive was sometimes leading to an unreadable
  archive in direct mode (was readable only in --sequential-read mode)
- fixed bug: libgpgme was only present at linking time of final binaries
  (dar, dar_slave, dar_xform, dar_manager, dar_cp, dar_split), not at
  linking time of libdar, which caused problem under Linux Rosa distro
  where the "no-undefined" flag is passed to the linker.
- minor new feature: -ay option has been added to display sizes in bytes
  instead of the default which uses the largest possible unit (Kio, Mio,
  and so on.)

from 2.5.7 to 2.5.8
- fixed double memory release occurring in a particular case of read error
- improving robustness of FSA code against data corruption
- fixed bug: DAR_DUC_PATH was not used with -F and -~ options
- new feature: added -aduc option to combine several -E options using the
  shell '&&' operator rather than the shell ';' operator. The consequence
  is that with -aduc option a non zero exist status of any script (and not
  only of the script given to the last -E option) will lead dar to report
  the error.
- man page updated about combination of several -E options
- fixed bug: merging partial FSA led to self reported bug in cat_inode.cpp
  at line 615

from 2.5.6 to 2.5.7
- fixed bug leading dar to not include directories given to -g option nor
  to exclude directories given to -P option when at the same time the
  directory given to -R option starts by a dot ("-R ./here" in place of
  "-R here")
- bug fix and speed improvement: under certain circumstances dar was
  reading several times the data at slice boundary, leading dar to ask for
  slice N then N-1 then again N, this caused sub-optimal performance and
  was triggering user script unnecessarily

from 2.5.5 to 2.5.6
- added speed optimization when comparing dates with hourshift flexibility
  (-H option)
- fixed bug met when using as reference an archive generated by dar 2.5.4
  or older, bug that lead dar saving almost all file even those that did
  not change.

from 2.5.4 to 2.5.5
- fixed message displayed when reading old archives
- fixed bug that avoided dar-2.5.x code to read old archive format when
  special allocation was set (by defaut) at compilation time
- disabling special-alloc by default reducing memory footprint
- fixed error in FAQ about the way ctime/atime/mtime are modified during
  normal operating system life.
- new implementation of class datetime with better memory footprint
- avoding storing sub-microsecond part of date to preserve limitint
  ability to store large dates
- moving field cat_inode::last_cha from pointer-to-field to plain field
  of the class, this slightly reduce catalogue memory footprint.
- fixing bug in the returned exit status when dar failed executing DUC
  command due to system error (now returning the expected code 6 in that
  case too)

from 2.5.3 to 2.5.4
- fixing missing included files for libdar API
- removed extra try/catch block introduced by commit
  72da5cad5e52f959414b3163a2e2a320c2bc721e
- removed sanity check that caused problem when writing an archive to a
  FUSE based filesystem.
- fixing non call of the -E script/command after last slice creation,
  when encryption or slice hashing was used
- fixed bug in dar_manager: archive permutation in database lead libdar
  to check an archive number of range under certain circumstances
- fixed inversion of the condition triggering a warning about archive
  date order in a dar_manager database while moving an archive within a
  database
- fixed typos in documentation
- catalogue memory optimization, with the drawback to limit the number of
  entry in an archive to the max integer supported by the libdar flavor
  (32 bits/64 bits/infinint).
- fix configure script to temporarily rely on LIBS rather LDFLAGS to
  check for gpgme availability
- removed order dependency between -A and -9 options of dar_manager: -9
  can now be specified before or after -A option.
- resetting to "false" the "inode_wrote" flag of hard link data-structure
  before testing and merging. Merging a previously tested archive or
  testing a second time would not include hard linked inode in the
  operation. This situation does not occurs with dar but could succeed
  with some external tools that keep the catalogue in memory to perform
  different operations on it.
- fixed bug in the routine that detects existing slices to warn the user
  and/or avoid overwriting, bug that lead dar to "bark" when an archive
  base name started by a + character.
- avoiding to use AM_PATH_GPGME in configure script when gpgme.m4 is not
  available
- adding new methods in libdar API to obtain the archive offset and
  storage size of saved files (class list_entry)
- adding new method in libdar API to translate archive offset to file
  offset (class archive)
- reporting a specific error message when filename returned by the system
  has the maximum length supported by the system itself, assuming
  filename has been truncated

from 2.5.2 to 2.5.3
- Fixing a 2.5.x build issue met when a 2.4.x libdar library is already
  installed in an FreeBSD system.
- Improving message and behavior of libdar in lax mod when a truncated
  archive is read
- Fixing self reported bug at "tronconneuse.cpp line 561" met while
  reading truncated/corrupted archive
- Fixed not closed filedescriptors, met when saving a filesystem that has
  not ExtX FSA available
- Fixing configure script to be more robust in front of system where
  gpgme.h is installed in a non standard path and user did not provide
  coherent CPPFLAGS, LDFLAGS before calling ./configure
- Displaying CRC values when listing isolated catalog as XML output
- Fixing compilation issue when system does not provide strerror_r() call
- Avoiding warning about FSA absence when fsa-scope is set to "none"
- Adding --disable-fadvise option to configure script for those that want
  back full pressure from dar on the system cache (same behavior as 2.4.x)
- Fixing bug, fadvise() called a wrong time making it having no effect
- updating FAQ about comparative performance from 2.4.x to 2.5.x
- optimization: reduced the number of call to dup() at libdar startup
- improvement: printing file type on verbose output
- new feature: added %t macro reflecting the inode type in dar's
  --backup-hook-execute option

from 2.5.1 to 2.5.2
- fixed bug met when permission is denied while reading or writing slices
- fixing bug that avoided creating an archive at the root of the filesystem
- fixing bug met in rare situation while reading in sequential-read mode
  an archive encrypted using gnupg encryption. In that situation libdar
  may fail reading the archive (but succeeds in normal read mode) issuing
  an obscure message (message has also been fixed).
- code simplification, removing field reading_verion from class crypto_sym
  as its parent class tronconneuse already have such information
- removed extra newline displayed by dar at end of execution
- fixed bug avoiding dar to properly read an entry (reporting CRC error)
  when specific sequence of character (start of escape sequence) fall at
  end of the read buffer of the escape layer.
- speed optimization for datetime class
- fixed bug that avoided dar reading archives in sequential read mode
  while reading from a pipe
- fixed bug in non regression test routine provided beside dar/libdar
- fixing display message showing not always in the correct context
- fixing case inversion leading the cache layer not to be used when
  necessary and used when useless while reading an archive
- improved heuristic in dar_manager to determine the date a file has been
  deleted.

from 2.5.0 to 2.5.1
- fixed display bug in dar_manager met when using -o option and adding
  options for dar that does not exist for dar_manager (like -R option)
- reactivating disabled (by mistake) optimization for some read-only dar
  manager database operations
- fixing compilation issue with dar against gcc 4.9.2
- fixing syntax error in dar_manager message
- fixed bug that forbade dar_manager to write down modified database
  when only database header was modified (-o, -b, -p switches).
- adding dar_manager database format version information with -l option
- fixed libdar inability to read dar_manager's database format version 4
- adapting code to build under cygwin environment, where thread_local seems
  broken
- fixed output to stderr in place of stdout for Licensing information
- fixed bug met when permission is denied while reading or writing slices
- fixing bug that avoided creating an archive at the root of the filesystem

from 2.4.x to 2.5.0
- added support for posix_fadvise()
- added entrepot class hierarchy to support in the future other storage
  types than local filesystem for slices
- API: added access to the entrepot through the API
- modified class hash_fichier for it becomes entrepot independent
- API: extended libdar API with an additional and more simple way to read
  an archive: archive::get_children_in_table() method, see
  doc/API_tutorial.html for details
- added support for extX (see lsattr(1)) and HFS+ (birthtime date)
  Filesystem Specific Attributes (FSA).
- dar is now able to skip backward when a file is found to be "dirty" at
  backup time. This avoids wasting space in archive but is only possible if
  the backward position is located in the current slice and no slice
  hashing nor strong encryption is used. Of course if the archive is
  written to a pipe or to stdout, skipping back to retry saving data at the
  same place is neither possible, --retry-on-change option stays possible
  in that cases at the cost of data duplication (wasted bytes amount, see
  --retry-on-change man page).
- by default dar now performs up to 3 retries but do not allow for wasting
  bytes if file has changed at the time it was read for backup,
  this can be modied using --retry-on-change option.
- With the same constraints as for a changing file, if a file is saved
  compressed but its compressed data uses more space than uncompressed,
  the file's data is resaved as uncompressed. However, if skipping backward
  is not possible, data is kept compressed.
- if system provides it, dar uses "Linux capabilities" to check for the
  ability to set file ownership when dar is not run as root. This allows dar
  to restore ownership when allowed even when it is not run as superuser.
- removing dar-help tool used to build dar -h messages. That tool became
  useless for a long time now.
- added several more specific verbosity options: -vm, -vf and -vt
- added support for microsecond timestamps (atime, mtime, ctime, birthtime)
- Using lutime() to restore atime/mtimes of symlink on systems that support
  it.
- API: removed backward compatible API for old libdar 4.4.x
- API: simplified implementation of archive isolation thanks to isolation
  evolution features brought by release 2.4.0. Memory requirement is now
  devided by two compared to releases of previous branch (2.4.x).
- dar has been updated to use this new API for archive isolation
- added exclude-by-ea feature to avoid saving inodes that have a particular
  user defined EA set.
- added comparison of an isolated catalogue with a filesystem, relying on
  embedded data CRC and inode metadata in absence of the saved data.
- The new archive format (version 9) holds the ciphering algorithm used
  at creation time, only the passphrase is now required at reading time and
  -K option may be ignored which will lead dar to prompt for passphrase.
- Adding support for public key encryption (GnuPG) supporting several
  encryption keys/recipients for a given archive
- Adding support for public key signature when public key encryption is used
- While listing archive contents, directories now show the size and average
  compression ratio of the data they contain
- Archive summary (-l with -q options) now reports the global compression
  ratio
- added the -vd switch to only display current directory under process for
  creation, diff, test, extraction and merging operations
- added xz/lzma compression support
- added -Tslicing listing option to show slice location of files inside
  an archive archive.
- isolated catalogues now keep a record of the slicing layout of their
  archive of reference in order to provide -Tslicing feature when used
  on the isolated catalogue alone.
- However if an archive has been resliced (using dar_xform) after its
  isolated catalogue has been generated, using -Tslicing option with the
  isolated catalogue would give wrong information. To overcome that, it
  is possible to specify what is the new slicing of the archive of
  reference by using the -s and -S options in conjunction with -Tslicing
- added dar_split command to provide on-fly multi-volume archive support
  for tape media
- experimental feature to have libdar using several threads (not activated
  by default due to poor performance gain)
- dar now aborts when a given  user target cannot be found in included file
- added sha512 hashing algorithm beside already available md5 and sha1, the
  generated hash file can be used with 'sha512sum -c <file>' command
- removed useless --jog option for memory management
- removed previously deprecated -y/--bzip2 command, bzip2 compression
  remains available using -z option (-zbzip2 or --compression=bzip2)
- replaced SHA1 by SHA224 to generate IV for encryption blocks, this
  slightly improves randomness of IV and stay available when libgcrypt is
  run in FIPS mode

from 2.4.23 to 2.4.24
- fixed bug: merging operation could wrongly melt different unrelated hard
  linked inodes when merging using an archive which results from a previous
  merging operation.

from 2.4.22 to 2.4.23
- fixed bug leading dar to not include directories given to -g option nor
  to exclude directories given to -P option when at the same time the
  directory given to -R option starts by a dot ("-R ./here" in place of
  "-R here")

from 2.4.21 to 2.4.22
- fixing bug in the returned exit status when dar failed executing DUC
  command due to system error (now returning the expected code 6 in that
  case too)

from 2.4.20 to 2.4.21
- removed sanity check that caused problem when writing an archive to a
  FUSE based filesystem.
- fixed bug in dar_manager: archive permutation in database lead libdar
  to check an archive number out of range under certain circumstances
- fixed inversion of the condition triggering a warning about archive
  date order in a dar_manager database while moving an archive within a
  database
- removed order dependency between -A and -9 options of dar_manager: -9
  can now be specified before or after -A option.
- resetting to "false" the "inode_wrote" flag of hard link datastructure
  before testing and merging. Merging a previously tested archive or
  testing a second time would not include hard linked inode in the
  operation. This situation does not occurs with dar but could succeed
  with some external tools that keep the catalogue in memory to perform
  different operations on it.
- fixed bug in the routine that detects existing slices to warn the user
  and/or avoid overwriting, bug that lead dar to "bark" when an archive
  base name started by a + character.

from 2.4.19 to 2.4.20
- fixed display bug in dar_manager met when using -o option and adding
  options for dar that does not exist for dar_manager (like -R option)
- reactivating disabled (by mistake) optimization for some read-only dar
  manager database operations
- fixing compilation issue with dar against gcc 4.9.2
- fixing syntax error in dar_manager message
- fixing bug that avoided creating an archive at the root of the filesystem

from 2.4.18 to 2.4.19
- fixed missing quote in dar_par.dcf which is called by the par2 directive
- fixed bug in dar_manager's -u option, not displaying most recent files of
  an archive when they have been marked as removed in a more recent archive
  of the same dar_manager database.
- fixed bug met while restoring in sequential read mode a file having
  several copies (was modified at the time it was saved and retry-on-change
  was set).

from 2.4.17 to 2.4.18
- Initial Vector used for strong encryption was set with pseudo-random data
  generated using SHA1 message digest and blowfish cipher, which are not
  available when ligcrypt is running in FIPS mode. Since 2.4.18 we now use
  SHA256 and AES256 for IV assignment in order to have libdar compatible
  with FIPS mode. For data encryption nothing changes: the cipher specified
  (-K, -J, -$ options on CLI) are used as before.
- fixing bug met when performing archive isolation in sequential-read mode,
  If an archive corruption or truncated archive leads an inode to not have
  its CRC readable, dar aborts and issues a BUG report.
- updating list of project relying on dar/libdar

from 2.4.16 to 2.4.17
- fixing issue when case insensitive comparison was requested and invalid
  wide char for the current local was met in a filename. In such situation
  the corresponding file was never saved before (considering a filesystem
  error for that file), while now the ASCII case insensitivity is used
  as fallback.

from 2.4.15 to 2.4.16
- fixing archive listing displayed information for catalogue size when
  archive is read in --sequential-read mode
- fixing bug that avoided dar releases 2.4.x up to 2.4.15 to read encrypted
  archive generated by dar release 2.3.x and below
- adding informational note at the end of ./configure script execution
  when --enable-mode has not been used.
- adding support for case sensitivity in filename comparison (-an option)
  for other character sets than POSIX/C locale like Cyrillic for example.
- fixing bashisms in doc/samples scripts

from 2.4.14 to 2.4.15
- fixing bug met when reading an encrypted archive in sequential mode
- fixing bug met when reading an encrypted archive in sequential mode from
  an anonymous pipe
- changed option '-;' to -9 as '-;' does not work on all systems with getopt
  (only long option equivalent --min-digits worked) for dar, dar_cp,
  dar_manager, dar_xform and dar_slave commands.
- fixing bug met when restoring deleted files in sequential read mode and
  some directory where they should be "restored" are not readable or
  could not be restored earlier
- adding extra buffer to handle sequential read of encrypted archive
  when the last crypto block contains some but not all clear data after
  encrypted one (the archive trailer).
- fixing compilation issue using clang
- fixing bug that prevents using -~ option with on-fly catalogue isolation
  in order to execute an user command once on-fly isolation has completed
- added some autoconf magic to determine the correct (BSD/GNU) flag to
  use with sed in order to activate regular expression parsing
- new implementation of mask_list class which is compatible with libc++
- fixed bug met on FreeBSD with dar_xform where the system provides a
  standard input file descriptor in read-write instead of read-only mode.

from 2.4.13 to 2.4.14
- limiting memory consumption of the cache layer to stay below 10 MiB, under
  certain circumstances (very large archive), it could grow up to an insane
  value like 50% or the available RAM. reducing to 10 MiB does not impact
  performance in a noticeable manner while it avoids system to swap out due
  to the libdar cache layer becoming huge.
- added --with-pkgconfigdir to define an alternative path for libdar
  pkgconfig file (to ease portability to FreeBSD)
- modified some Makefile.am for better FreeBSD support
- fixed display bug in XML listing output concerning hard linked inodes
- fixing typo in man page
- fixing bug met while isolating a catalogue in --sequential-read mode.
  Using such isolated catalogue lead dar report an error about inaccessible
  EA.
- displaying compression rate for sparse files even when they are
  uncompressed, sparse file detection also leads to compress files
- fixing bug that lead libdar to fail comparing an inode having EA when
  comparison is done in --sequential-read mode
- fixing display bug in in ligcrypt check of configure script for minimum
  required version
- fixing 'make clean' to remove some forgotten files generated by 'make'

(nros)

doc: Added devel/libthreadar version 1.4.0

(nros)

Add libthreadar version 1.4.0 to pkgsrc-current

libthreadar provides C++ classes for manipulating threads and
propagating back exception from thread to parent thread when the
parent calls the join() method.

(nros)

doc: Updated graphics/p5-PerlMagick to 7.1.0.49

(wiz)

doc: Updated graphics/ImageMagick to 7.1.0.49

(wiz)

ImageMagick, p5-PerlMagick: update to 7.1.0.49

Upstream provides no summaries any longer, just lists of commits, see
https://github.com/ImageMagick/Website/blob/main/ChangeLog.md

(wiz)

doc: Updated shells/bash to 5.2

(wiz)

bash: update to 5.2.

This is a terse description of the new features added to bash-5.2 since
the release of bash-5.1.  As always, the manual page (doc/bash.1) is
the place to look for complete descriptions.

1. New Features in Bash

a. The bash malloc returns memory that is aligned on 16-byte boundaries.

b. There is a new internal timer framework used for read builtin timeouts.

c. Rewrote the command substitution parsing code to call the parser recursively
  and rebuild the command string from the parsed command. This allows better
  syntax checking and catches errors much earlier. Along with this, if
  command substitution parsing completes with here-documents remaining to be
  read, the shell prints a warning message and reads the here-document bodies
  from the current input stream.

d. The `ulimit' builtin now treats an operand remaining after all of the options
  and arguments are parsed as an argument to the last command specified by
  an option. This is for POSIX compatibility.

e. Here-document parsing now handles $'...' and $"..." quoting when reading the
  here-document body.

f. The `shell-expand-line' and `history-and-alias-expand-line' bindable readline
  commands now understand $'...' and $"..." quoting.

g. There is a new `spell-correct-word' bindable readline command to perform
  spelling correction on the current word.

h. The `unset' builtin now attempts to treat arguments as array subscripts
  without parsing or expanding the subscript, even when `assoc_expand_once'
  is not set.

i. There is a default value for $BASH_LOADABLES_PATH in config-top.h.

j. Associative array assignment and certain instances of referencing (e.g.,
  `test -v' now allow `@' and `*' to be used as keys.

k. Bash attempts to expand indexed array subscripts only once when executing
  shell constructs and word expansions.

l. The `unset' builtin allows a subscript of `@' or `*' to unset a key with
  that value for associative arrays instead of unsetting the entire array
  (which you can still do with `unset arrayname'). For indexed arrays, it
  removes all elements of the array without unsetting it (like `A=()').

m. Additional builtins (printf/test/read/wait) do a better job of not
  parsing array subscripts if array_expand_once is set.

n. New READLINE_ARGUMENT variable set to numeric argument for readline commands
  defined using `bind -x'.

o. The new `varredir_close' shell option causes bash to automatically close
  file descriptors opened with {var}<fn and other styles of varassign
  redirection unless they're arguments to the `exec' builtin.

p. The `$0' special parameter is now set to the name of the script when running
  any (non-interactive) startup files such as $BASH_ENV.

q. The `enable' builtin tries to load a loadable builtin using the default
  search path if `enable name' (without any options) attempts to enable a
  non-existent builtin.

r. The `printf' builtin has a new format specifier: %Q. This acts like %q but
  applies any specified precision to the original unquoted argument, then
  quotes and outputs the result.

s. The new `noexpand_translations' option controls whether or not the translated
  output of $"..." is single-quoted.

t. There is a new parameter transformation operator: @k. This is like @K, but
  expands the result to separate words after word splitting.

u. There is an alternate array implementation, selectable at `configure' time,
  that optimizes access speed over memory use (use the new configure
    --enable-alt-array-implementation option).

v. If an [N]<&WORD- or [N]>&WORD- redirection has WORD expand to the empty
  string, treat the redirection as [N]<&- or [N]>&- and close file descriptor
  N (default 0).

w. Invalid parameter transformation operators are now invalid word expansions,
  and so cause fatal errors in non-interactive shells.

x. New shell option: patsub_replacement. When enabled, a `&' in the replacement
  string of the pattern substitution expansion is replaced by the portion of
  the string that matched the pattern. Backslash will escape the `&' and
  insert a literal `&'.

y. `command -p' no longer looks in the hash table for the specified command.

z. The new `--enable-translatable-strings' option to `configure' allows $"..."
  support to be compiled in or out.

aa. The new `globskipdots' shell option forces pathname expansion never to
    return `.' or `..' unless explicitly matched. It is enabled by default.

bb. Array references using `@' and `*' that are the value of nameref variables
    (declare -n ref='v[@]' ; echo $ref) no longer cause the shell to exit if
    set -u is enabled and the array (v) is unset.

cc. There is a new bindable readline command name:
    `vi-edit-and-execute-command'.

dd. In posix mode, the `printf' builtin checks for the `L' length modifier and
    uses long double for floating point conversion specifiers if it's present,
    double otherwise.

ee. The `globbing' completion code now takes the `globstar' option into account.

ff. `suspend -f' now forces the shell to suspend even if job control is not
  currently enabled.

gg. Since there is no `declare -' equivalent of `local -', make sure to use
    `local -' in the output of `local -p'.

(wiz)

doc: Updated devel/readline to 8.2

(wiz)

readline: update to 8.2.

New Features in Readline

a. There is now an HS_HISTORY_VERSION containing the version number of the
  history library for applications to use.

b. History expansion better understands multiple history expansions that may
  contain strings that would ordinarily inhibit history expansion (e.g.,
  `abc!$!$').

c. There is a new framework for readline timeouts, including new public
  functions to set timeouts and query how much time is remaining before a
  timeout hits, and a hook function that can trigger when readline times
  out. There is a new state value to indicate a timeout.

d. Automatically bind termcap key sequences for page-up and page-down to
  history-search-backward and history-search-forward, respectively.

e. There is a new `fetch-history' bindable command that retrieves the history
  entry corresponding to its numeric argument. Negative arguments count back
  from the end of the history.

f. `vi-undo' is now a bindable command.

g. There is a new option: `enable-active-region'. This separates control of
  the active region and bracketed-paste. It has the same default value as
  bracketed-paste, and enabling bracketed paste enables the active region.
  Users can now turn off the active region while leaving bracketed paste
  enabled.

h. rl_completer_word_break_characters is now `const char *' like
  rl_basic_word_break_characters.

i. Readline looks in $LS_COLORS for a custom filename extension
  (*.readline-colored-completion-prefix) and uses that as the default color
  for the common prefix displayed when `colored-completion-prefix' is set.

j. Two new bindable string variables: active-region-start-color and
  active-region-end-color. The first sets the color used to display the
  active region; the second turns it off. If set, these are used in place
  of terminal standout mode.

k. New readline state (RL_STATE_EOF) and application-visible variable
  (rl_eof_found) to allow applications to detect when readline reads EOF
  before calling the deprep-terminal hook.

l. There is a new configuration option: --with-shared-termcap-library, which
  forces linking the shared readline library with the shared termcap (or
  curses/ncurses/termlib) library so applications don't have to do it.

m. Readline now checks for changes to locale settings (LC_ALL/LC_CTYPE/LANG)
  each time it is called, and modifies the appropriate locale-specific display
  and key binding variables when the locale changes.

(wiz)

doc: Updated sysutils/dbus to 1.14.2

(wiz)

dbus: update to 1.14.2.

dbus 1.14.2 (2022-09-26)
========================

Fixes:

• Fix build failure on FreeBSD (dbus!277, Alex Richardson)

• Fix build failure on macOS with launchd enabled
  (dbus!287, Dawid Wróbel)

• Preserve errno on failure to open /proc/self/oom_score_adj
  (dbus!285, Gentoo#834725; Mike Gilbert)

• On Linux, don't log warnings if oom_score_adj is read-only but does not
  need to be changed (dbus!291, Simon McVittie)

• Slightly improve error-handling for inotify
  (dbus!235, Simon McVittie)

• Don't crash if dbus-daemon is asked to watch more than 128 directories
  for changes (dbus!302, Jan Tojnar)

• Autotools build system fixes:
  · Don't treat --with-x or --with-x=yes as a request to disable X11,
    fixing a regression in 1.13.20. Instead, require X11 libraries and
    fail if they cannot be detected. (dbus!263, Lars Wendler)
  · When a CMake project uses an Autotools-built libdbus in a
    non-standard prefix, find dbus-arch-deps.h successfully
    (dbus#314, Simon McVittie)
  · Don't include generated XML catalog in source releases
    (dbus!317, Jan Tojnar)
  · Improve robustness of detecting gcc __sync atomic builtins
    (dbus!320, Alex Richardson)

• CMake build system fixes:
  · Detect endianness correctly, fixing interoperability with other D-Bus
    implementations on big-endian systems (dbus#375, Ralf Habacker)
  · When building for Unix, install session and system bus setup
    in the intended locations
    (dbus!267, dbus!297; Ralf Habacker, Alex Richardson)
  · Detect setresuid() and getresuid() (dbus!319, Alex Richardson)
  · Detect backtrace() on FreeBSD (dbus!281, Alex Richardson)
  · Don't include headers from parent directory (dbus!282, Alex Richardson)
  · Distinguish between host and target TMPDIR when cross-compiling
    (dbus!279, Alex Richardson)
  · Fix detection of atomic operations (dbus!306, Alex Richardson)

Tests and CI enhancements:

• On Unix, skip tests that switch uid if run in a container that is
  unable to do so, instead of failing (dbus#407, Simon McVittie)

• Use the latest MSYS2 packages for CI
  (Ralf Habacker, Simon McVittie)

(wiz)

Updated comms/py-rich, devel/py-jaraco.classes

(adam)

py-jaraco.classes: updated to 3.2.3

v3.2.3
Enabled badge with link to docs in the readme.

(adam)

py-rich: updated to 12.6.0

12.6.0 - 2022-10-02

Added

Parse ANSI escape sequences in pretty repr
Add support for FORCE_COLOR env var
Allow a max_depth argument to be passed to the install() hook
Document using None as name in __rich_repr__ for tuple positional args
Add font_aspect_ratio parameter in SVG export https://github.com/Textualize/rich/pull/2539/files
Added Table.add_section method.

Fixed

Handle stdout/stderr being null
Fix NO_COLOR support on legacy Windows
Fix pretty printer handling of cyclic references
Fix missing mode property on file wrapper breaking uploads via requests
Fix mismatching default value of parameter ensure_ascii
Remove unused height parameter in Layout class
Fixed exception in Syntax.rich_measure for empty files

Changed

Removed border from code blocks in MarkdownCVS: ----------------------------------------------------------------------

(adam)

Updated databases/sqlite3, databases/sqlite3-docs, databases/sqlite3-tcl, devel/lemon

(adam)

sqlite3: updated to 3.39.4

Changes in version 3.39.4 (2022-09-29):

Fix the build on Windows so that it works with -DSQLITE_OMIT_AUTOINIT
Fix a long-standing problem in the btree balancer that might, in rare cases, cause database corruption if the application uses an application-defined page cache.
Enhance SQLITE_DBCONFIG_DEFENSIVE so that it disallows CREATE TRIGGER statements if one or more of the statements in the body of the trigger write into shadow tables.
Fix a possible integer overflow in the size computation for a memory allocation in FTS3.
Fix a misuse of the sqlite3_set_auxdata() interface in the ICU Extension.

(adam)

Updated devel/libebml, multimedia/libmatroska

(adam)

libmatroska: updated to 1.7.0

Version 1.7.0 2022-09-30

* A C++14 compliant C++ compiler is now required.
* libEBML v1.4.3 is now required.
* Remove Coremake project files
* Add `KaxInternalBlock::GetRelativeTimestamp()` to access unscaled
  block timestamps.
* Fixed problems with the generated `pkg-config` files if any of the
  installation paths are absolute.
* Added several enums in `namespace libmatroska` for the various
  elements that are constrained to a set of options:
  `MatroskaTrackType`, `MatroskaTrackEncodingCompAlgo`,
  `MatroskaChapterTranslateCodec`, `MatroskaTrackTranslateCodec`,
  `MatroskaVideoFlagInterlaced`, `MatroskaVideoFieldOrder`,
  `MatroskaVideoStereoMode`, `MatroskaVideoAlphaMode`,
  `MatroskaVideoOldStereoMode`, `MatroskaVideoDisplayUnit`,
  `MatroskaVideoAspectRatioType`, `MatroskaVideoMatrixCoefficients`,
  `MatroskaColourChromaSitingHorz`, `MatroskaColourChromaSitingVert`,
  `MatroskaVideoRange`, `MatroskaVideoTransferCharacteristics`,
  `MatroskaVideoPrimaries`, `MatroskaVideoProjectionType`,
  `MatroskaAudioEmphasis`, `MatroskaTrackPlaneType`,
  `MatroskaContentEncodingScope`, `MatroskaContentEncodingType`,
  `MatroskaContentEncodingAlgo`, `MatroskaAESSettingsCipherMode`,
  `MatroskaContentSignatureAlgo`, `MatroskaContentSigHashAlgo`,
  `MatroskaChapterSkipType`, `MatroskaChapterProcessTime` and
  `MatroskaTargetTypeValue`.
* Updated the semantics to the latest specifications, deprecating the
  following elements by preventing code to write them:
  `KaxClusterSilentTracks`, `KaxClusterSilentTrackNumber`,
  `KaxSlices`, `KaxReferenceFrame`, `KaxReferenceOffset`,
  `KaxReferenceTimeCode`, `KaxTrackTimecodeScale`,
  `KaxCodecDecodeAll`, `KaxVideoAspectRatio`, `KaxTrickTrackUID`,
  `KaxTrickTrackSegmentUID`, `KaxTrickTrackFlag`,
  `KaxTrickMasterTrackUID`, `KaxTrickMasterTrackSegmentUID`,
  `KaxContentSignature`, `KaxContentSigKeyID`, `KaxContentSigAlgo` and
  `KaxContentSigHashAlgo`.
* Updated the semantics to the latest specifications, making the
  following elements mandatory (but having default values):
  `KaxCodecDelay`, `KaxVideoPixelCropBottom`, `KaxVideoPixelCropTop`,
  `KaxVideoPixelCropLeft`, `KaxVideoPixelCropRight`,
  `KaxVideoBitsPerChannel`, `KaxCueCodecState`,
  `KaxTagTargetTypeValue`, `KaxTrackLanguage`, `KaxVideoStereoMode`,
  `KaxVideoAlphaMode`, `KaxEditionFlagOrdered`,
  `KaxVideoChromaSitHorz`, `KaxVideoChromaSitVert`,
  `KaxVideoColourRange`, `KaxVideoColourMatrix`,
  `KaxVideoColourTransferCharacter`, `KaxVideoColourPrimaries` and
  `KaxVideoDisplayUnit`.
* Updated the semantics to the latest specifications, removing the
  default values from the following elements: `KaxCueBlockNumber`,
  `KaxFlagHearingImpaired`, `KaxFlagVisualImpaired`,
  `KaxFlagTextDescriptions`, and `KaxFlagOriginal`.
* Updated the semantics to the latest specifications, adding the
  following new elements: `TagDefaultBogus` (as a placeholder for
  accidentally used but wrong EBML ID 0x44b4), `KaxEmphasis`,
  `KaxChapterSkipType`, `KaxEditionDisplay`, `KaxEditionString` and
  `KaxEditionLanguageIETF`.

(adam)

libebml: updated to 1.4.3

Version 1.4.3 2022-09-30

* A C++14 compliant C++ compiler is now required.
* Fix compilation with g++ 11.
* Remove Coremake project files
* Updated the bundled utf8cpp to v3.2.1.
* Fixed several problems in `EbmlBinary:` potential segfault by
  writing to a `nullptr`, potential memory leak under certain error
  conditions.
* Fixed problems with the generated `pkg-config` files if any of the
  installation paths are absolute.

(adam)

py-cryptodome: Fails with a compiler defaulting to c89

(nia)

gst-plugins1-bad: Fails with compiler defaulting to c89.

(nia)

doc: Updated sysutils/dusage to 0.3.3

(pin)

sysutils/dusage: update to 0.3.3

- Audit: Reference centralized repository
- Fix: Clippy warnings
- Colorize: Split to seprate structs
- Cargo: Use latest clap

(pin)

Updated multimedia/handbrake

(adam)

handbrake: switch to stable x264; fix build on Darwin; fix PLIST when gtk3 option is disabled; pkglint fixes; bump revision

(adam)

Updated misc/stellarium, time/py-pytz

(adam)

py-pytz: updated to 2022.4

2022.4:
Unknown changes

(adam)

stellarium: updated to 1.0

1.0 [2022-10-01]
The Stellarium team did it. Stellarium 1.0 is here!

What makes this 1.0?

- After more than 20 years of development the program is finally accurate
  enough for historical application.
- This is the first release based on the Qt6 framework, so the project is
  safe for future development. These packages are tagged with a version
  number like 1.22.3.
- We keep releasing Qt5-based packages for legacy or obsolete systems.
  This may include many Windows users who have to run ANGLE mode.
  These packages are tagged with a version number like 0.22.3.

What is new for users?

- A new, much better skylight model (Not for MacOS and OpenGL ES2 systems,
  sorry.)
- Many details around eclipses
- Updated Observation List features
- New features in AstroCalc tool
- HiDPI improvements
- Better dithering
- Able to use Windows location service (Windows)
- New skyculture: Samoan
- Updated several skycultures
- Updates in Angle Measure, Satellites, Oculars, Remote Control, Pulsars
  plugins
- Many more bugfixes.

(adam)

posgresql*: Restore MAKE_JOBS_SAFE=no

(nia)

doc: Updated databases/p5-App-Sqitch to 1.3.1

(schmonz)

Update to 1.3.1. From the changelog:

- Fixed a bug introduced in v1.3.0 where the Postgres engine would
  always pass the port to `psql`, thus ignoring the `PGPORT` environment
  variable. Thanks to Cam Feenstra for the spot (#675)!
- Fixed test failures on OSes where the local time zone cannot be
  determined. Thanks to Slaven Rezić for the test reports, and to
  Dave Rolsky for the solution (#672).
- Updated the MySQL deploy/revert lock to be specific to the target
  database. This allows multiple instances of Sqitch to run at the
  same time on the same server as long as they're connecting to different
  databases. Thanks to Dmytro Kh for the report and discussion of the
  options (#670).
- Fixed test failures where DBD::Mem was not installed. Likely only
  occurred on some CPAN Testers nodes. Thanks to Slaven Rezić for those
  (#673).
- Banned the backslash character (`\`) in change and tag names. It would
  be ignored on Unix-style systems, but create unexpected subdirectories
  on Windows systems.
- Banned the slash character (`/`) in tag names. They're still allowed
  in change names to enable script organization, but can wreak havoc
  when used in tag names. Thanks to @ewie for the report (#680)!

(schmonz)

doc: Updated devel/py-approvaltests to 6.2.0

(schmonz)

Update to 6.2.0. From the changelog:

DateScrubber:
- You can now easily create a date scrubber.

SimpleLogger log_to_string is thread safe:
- log_to_string, by default, now will log 1 string per thread. Allowing
  multithreaded testing

(schmonz)

pyversion.mk: Define PYPKGPREFIX in error case

The specification for pyversion.mk says that it defines PYPKGPREFIX
and PYVERSSUFFIX.  Various buildlink files rely on these being
defined, as they are tested without guarding them for being empty.

When there is no valid python version, _PYTHON_VERSION was set to
"none", and PKG_FAIL_REASON defined, so the user gets a reasonable
error.  However, if a buildlink3 uses an unguarded PYPKGPREFIX, a
syntax error results, and the PKG_FAIL_REASON is not display.

This commit defines the two variables to "none" in the case of no
valid version, mirroring the treatment of _PYTHON_VERSION and
correcting a failure to follow the specification.  In this case the
build is going to fail one way or another, but it's vastly better to
have a useful error message.

(Tested earlier, but deferred during freeze.)

(gdt)

doc/TODO: + stellarium-1.0, zola-0.16.1.

(wiz)

Set liblzo LICENSE

(nros)

doc: Updated emulators/suse15_gtk3 to 15.5nb1

(wiz)

suse15_gtk3: run update-mime-database during INSTALL

Bump PKGREVISION.

(wiz)

doc: Updated net/dhcpcd-qt to 0.7.8

(nros)

doc: Updated net/dhcpcd-gtk to 0.7.8

(nros)

doc: Updated net/dhcpcd-icons to 0.7.8

(nros)

Update dhcpcd-ui based packages to version 0.7.8

Remove dead master sites.

Notable changes from git:
Add Support for dhcpcd NOCARRIER_ROAMING.

(nros)

doc: Updated net/dhcpcd-dbus to 0.6.1

(nros)

Update net/dhcpcd-dbus to version 0.6.1

Fix master sites.
Changelog could not be found for changes.

(nros)

pkglint fixes

(nros)

doc: Updated net/dhcpcd to 9.4.1

(nros)

Update net/dhcpcd to version 9.4.1

Fix MASTER_SITES.
Notable changes from git log:
Better RFC 4707 conformance.
Fix getting interface VLANID on *BSD.
Fix Compile on DragonFlyBSD.

(nros)

mkvtoolnix: put PKG_SUGGESTED_OPTIONS instead of PKG_DEFAULT_OPTIONS

(adam)

crypto++ updated to version 8.7.0

(nros)

doc: mention new suse15_* packages

(wiz)