Pydicom is a pure Python package for working with DICOM files such as medical
images, reports, and radiotherapy objects.

Pydicom makes it easy to read these complex files into natural pythonic
structures for easy manipulation. Modified datasets can be written again to
DICOM format files.

Packaged by Eric A. Borisch via #37, thank you Eric!

### 1.2.5 / 2018-10-16

New features:

* Add mvderwin and derwin methods to Window.  Pull request #37 by meschbach.
* Add documentation link.  Pull request #39 by atshakil.

Bug fixes:

* Favor ncursesw over curses.  Pull request #40 by DivineDominion.

* pkgsrc change: add "USE_LANGUAGES= # none" line.

1.0.1 (2019-01-16)

Merged Pull Requests

* Update expeditor config and order gemfile #38 (tas50)

1.0.0 (2019-01-16)

Merged Pull Requests

* mixlib-archive-tar create corrupt archives on Windows #37 (kenmacleod)
* Require Ruby 2.4+ and bump to version 1.0 #36 (lamont-granquist)

0.4.19 (2018-12-12)

Merged Pull Requests

* Don't ship the readme in the gem artifact #35 (tas50)

0.4.18 (2018-10-15)

Merged Pull Requests

* Misc tweaks to gemfile / gemspec #32 (tas50)
* Add a mingw32 specific gemspec to limit files shipped on *nix #33 (tas50)

Update archivers/ruby-minitar to 0.9.

## 0.9 / 2019-09-04

*   jtappa added the ability to skip fsync with a new option to Minitar.unpack
    and Minitar::Input#extract_entry. Provide `:fsync => false` as the last
    parameter to enable. Merged from a modified version of PR [#37][].

## 0.8 / 2019-01-05

*   inkstak resolved an issue introduced in the fix for [#31][] by allowing
    spaces to be considered valid characters in strict octal handling. Octal
    conversion ignores leading spaces. Merged from a slightly modified version
    of PR [#35][].

*   dearblue contributed PR [#32][] providing an explicit call to #bytesize for
    strings that include multibyte characters. The PR has been modified to be
    compatible with older versions of Ruby and extend tests.

*   Akinori MUSHA (knu) contributed PR [#36][] that treats certain badly
    encoded regular files (with names ending in `/`) as if they were
    directories on decode.

## 0.7 / 2018-02-19

*   Fixed issue [#28][] with a modified version of PR [#29][] covering the
    security policy and position for Minitar. Thanks so much to ooooooo\_q for
    the report and an initial patch. Additional information was added as
    [#30][].

*   dearblue contributed PR [#33][] providing a fix for Minitar::Reader when
    the IO-like object does not have a `#pos` method.

*   Kevin McDermott contributed PR [#34][] so that an InvalidTarStream is
    raised if the tar header is not valid, preventing incorrect streaming of
    files from a non-tarfile. This is a minor breaking change, so the version
    has been bumped accordingly.

*   Kazuyoshi Kato contributed PR [#26][] providing support for the GNU tar
    long filename extension.

*   Addressed a potential DOS with negative size fields in tar headers
    ([#31][]). This has been handled in two ways: the size field in a tar
    header is interpreted as a strict octal value and the Minitar reader will
    raise an InvalidTarStream if the size ends up being negative anyway.

Switch from qt4 to qt5. Remove the qt4 option.

CHANGELOG
=========
BibleTime 2.11.2
The BibleTime team is proud to announce the immediate availability of BibleTime version 2.11.2 which is the second bugfix release in the stable 2.11 series of BibleTime.

All users of BibleTime are encouraged to upgrade, especially users still using BibleTime version 2.10 or earlier.

Notable changes since 2.11.1:

    Updated translations.
    Improved compatibility with Qt 5.11 (including bug #140)
    Fixed crash when clicking on "full syntax" (bug #134)
    Fixed Mag not always working with Hebrew / Strongs (bug #132)
    Fixed BibleTime startup on some versions of Windows (bug #119)
    Fixed Bookshelf Wizard buttons not being translated (bug #131)
    Fixed application icon directory to match the FreeDesktop standard
    Fixed bug which prevented installing of works (bug #124)

BibleTime 2.11.1
The BibleTime team is proud to announce the immediate availability of BibleTime version 2.11.1 which is the first bugfix release in the stable 2.11 series of BibleTime.

All users of BibleTime are encouraged to upgrade, especially users still using BibleTime version 2.10 or earlier.

Notable changes since 2.11.0:

    Enhanced packaging for Windows.
    Enhanced some error messages.
    Updated translations. Thanks to all translators!.
    Improved build-time detection of Qt WebEngine.
    Fixed crash with Qt 5.9 (workaround for QTBUG-61213).
    Fixed apocryphal books not being properly displayed (#12).
    Fixed paragraphs being displayed incorrectly (#37).
    Fixed some greek dictionary modules not working in mag (#52).
    Fixed windows not starting on some Windows 7 computers (#90).
    Fixed a bug which hindered changing to second tab in Tabbed view (#91)
    Fixed Qt "More Info..." tab being blank (#92)
    Fixed crash when closing module display window with Qt 5.8 (#94)
    Fixed images not being displayed (#95).
    Fixed reloading of "All Text Windows" shortcuts not working (#102).
    Fixed problem with Save - Yes/No dialog and editing a Personal commentary (#105).

BibleTime 2.11.0
Thanks to the great mercy of our Savior and Lord, king Jesus Christ, the BibleTime team is yet again pleased to announce the immediate availability of BibleTime version 2.11.0, which is the first full release in the the stable 2.11 series of BibleTime.

All users of BibleTime are encouraged to upgrade, including users of the BibleTime version 2.10 series.

Notable changes since the 2.10 series:

    Redesigned bookshelf manager
    Many bugfixes and optimizations

Build requirements changes:

    A C++11 compiler is now required
    Qt 5 or later is now required
    xml-po is no longer required

BibleTime 2.11 RC 2
The BibleTime team is proud to announce the immediate availability of BibleTime version 2.11 RC 2, which is the second release candidate in the stable 2.11 series of BibleTime, with a number of bugs fixed since RC 1.

Notable changes since the 2.10 series:

    Many bugfixes and optimizations
    Redesigned bookshelf manager

Build requirements changes:

    A C++11 compiler is now required
    Qt 5 or later is now required
    xml-po is no longer required

BibleTime 2.11 RC 1
The BibleTime team is proud to announce the immediate availability of BibleTime version 2.11_rc1,
which is the first release candidate in the stable 2.11 series of BibleTime.

Notable changes since the 2.10 series:

    Many bug fixes and optimizations
    Redesigned bookshelf manager

Build requirements changes:

    A C++11 compiler is now required
    Qt 5 or later is now required
    xml-po is no longer required

BibleTime 2.11 beta 1
The BibleTime team is proud to announce the immediate availability of BibleTime version 2.11_beta1,
which is the first (and only) beta release in the stable 2.11 series of BibleTime.

Notable changes since the 2.10 series:

    Many bug fixes and optimizations
    Redesigned bookshelf manager

Build requirements changes:

    A C++11 compiler is now required
    Qt 5 or later is now required
    xml-po is no longer required

-----------------------------------------
version 1.78 at 2019-11-14 14:18:25 +0000
-----------------------------------------
  -  Release engineering for 1.78
  -  No functional changes, removed stray file from the dist. GH #37

-----------------------------------------
version 1.76 at 2019-11-10 21:56:25 +0000
-----------------------------------------
  -  Release engineering for 1.76
  -  Fix issues with patching utils/h2ph.PL on v5.8.x
  -  Whilst I was at it got it working for the v5.9.x series and converted
     patch storage to base64

-----------------------------------------
version 1.74 at 2019-11-10 19:12:13 +0000
-----------------------------------------
   - Release engineering for 1.74
   - fix #35; restore file permission
   - Revert "Fix issue where Configure was left not executable"
   - This reverts commit 8c5111233d3120fc9e5c11045755a4d96d247848.
   - Will apply skaji's solution as it is much more elegant.

-----------------------------------------
version 1.72 at 2019-11-10 17:14:02 +0000
-----------------------------------------
  -  Release engineering for 1.72
  -  Fix issue where Configure was left not executable
  -  Added test prereq Test::More as suggested by CPANTS.
  -  Signed-off-by: Chris 'BinGOs' Williams <chris@bingosnet.co.uk>

-----------------------------------------
version 1.70 at 2019-11-08 02:01:40 +0000
-----------------------------------------
  -  Release engineering for 1.70
  -  Added Base64 encoding of patches

-----------------------------------------
version 1.68 at 2019-11-07 10:11:25 +0000
-----------------------------------------
  -  Release engineering for 1.68
  -  Don't index package Errno

-----------------------------------------
version 1.66 at 2019-11-07 00:59:46 +0000
-----------------------------------------
  -  Release engineering for 1.66
  -  Fix issues with v5.7.x (h2ph.PL and Errno.pm.PL)
  -  Fix utils/h2ph.PL patching on v5.8.0
  -  Set files to be patched to 0644 if they are 0444, set back after.

  -  Issue 31: In an environment that uses the Lustre file system, it's
    been seen that any files that are set to 0444 (read only) will cause
    fatal filesystem errors when the patch is attempted. This makes using
    perlbrew to install perl on these systems impossible This change
    detects read-only files about to be patched, sets them to 0644 for
    the duration of the patching, then sets them back to 0444 so that
    they exist as expected during the actual build process.

v1.1 / 2018-09-11
==================

  * ioping: release 1.1
  * ioping.1: raw statisitics in nanoseconds
  * Merge pull request #37 from standby24x7/fix-man
  * Fix a typo in ioping.1
  * Merge pull request #36 from lewellyn/solaris
  * Correct Solaris predefined macro
  * ioping.1: add more references
  * Merge pull request #32 from kolyshkin/makefile
  * Makefile: only use vN tags for EXTRA_VERSION
  * ioping.c: set VERSION to 1.0
  * Makefile: make sure git tag == src ver
  * Makefile: make all phony targets as such
  * Makefile: move -D to CPPFLAGS
  * ioping(1): fix aio description

3.1.14.0
* Add parseFromFile to Text.Parsec.Text.Lazy and Text.Parsec.Text
  (#103, #104).
* Clarify Haddock documentation in various places (#105,#101,#102).
* Add support for base-4.13.

3.1.13.0

* Add official support for SafeHaskell.

  NOTE: This is the first version whose SafeHaskell properties have
  become an intentional part of the API contract; previous versions
  were merely accidentally safe-inferred (or not depending on various
  factors; in other words, this was a fragile property). If you rely
  on SafeHaskell to consider module imports from parsec safe, this is
  the first version of parsec which actually guarantees a well-defined
  state; you can declare this requirement by either specifying

    build-depends: parsec >= 3.1.13.0 && < 3.2

  or, starting with cabal-version:2.0, via

    build-depends: parsec ^>= 3.1.13.0

* Drop support for GHC 7.0, GHC 7.2, and GHC 7.4.1; support window
  starts with GHC 7.4.2.

3.1.12.0
* Support limited to GHC 7.0 & GHC 7.2 only
* Add MonadFail instance for ParsecT
* Add Semigroup/Monoid instances for ParsecT (#80,#82)
* Fix space leak in Applicative/Monad interface (#37)
* Add parserTrace and parserTraced combinators for debugging.

3.1.11
* Include README.md in package.

3.1.10
* Most types now have a Typeable instance. Some instances are dropped
  from older versions of GHC (sorry about that!).
* The token-parser now rejects Unicode numeric escape sequences for
  characters outside the Unicode range.
* The token-parser now loses less precision when parsing literal
  doubles.
* Documentation fixes and corrections.
* We no longer test parsec builds on GHC 7.4.

v1.1 / 2018-09-11
==================

  * ioping: release 1.1
  * ioping.1: raw statisitics in nanoseconds
  * Merge pull request #37 from standby24x7/fix-man
  * Fix a typo in ioping.1
  * Merge pull request #36 from lewellyn/solaris
  * Correct Solaris predefined macro
  * ioping.1: add more references
  * Merge pull request #32 from kolyshkin/makefile
  * Makefile: only use vN tags for EXTRA_VERSION
  * ioping.c: set VERSION to 1.0
  * Makefile: make sure git tag == src ver
  * Makefile: make all phony targets as such
  * Makefile: move -D to CPPFLAGS
  * ioping(1): fix aio description

3.1.14.0
* Add parseFromFile to Text.Parsec.Text.Lazy and Text.Parsec.Text
  (#103, #104).
* Clarify Haddock documentation in various places (#105,#101,#102).
* Add support for base-4.13.

3.1.13.0

* Add official support for SafeHaskell.

  NOTE: This is the first version whose SafeHaskell properties have
  become an intentional part of the API contract; previous versions
  were merely accidentally safe-inferred (or not depending on various
  factors; in other words, this was a fragile property). If you rely
  on SafeHaskell to consider module imports from parsec safe, this is
  the first version of parsec which actually guarantees a well-defined
  state; you can declare this requirement by either specifying

    build-depends: parsec >= 3.1.13.0 && < 3.2

  or, starting with cabal-version:2.0, via

    build-depends: parsec ^>= 3.1.13.0

* Drop support for GHC 7.0, GHC 7.2, and GHC 7.4.1; support window
  starts with GHC 7.4.2.

3.1.12.0
* Support limited to GHC 7.0 & GHC 7.2 only
* Add MonadFail instance for ParsecT
* Add Semigroup/Monoid instances for ParsecT (#80,#82)
* Fix space leak in Applicative/Monad interface (#37)
* Add parserTrace and parserTraced combinators for debugging.

3.1.11
* Include README.md in package.

3.1.10
* Most types now have a Typeable instance. Some instances are dropped
  from older versions of GHC (sorry about that!).
* The token-parser now rejects Unicode numeric escape sequences for
  characters outside the Unicode range.
* The token-parser now loses less precision when parsing literal
  doubles.
* Documentation fixes and corrections.
* We no longer test parsec builds on GHC 7.4.

Upstream NEWS:

  Add support for OGC GeoTIFF 1.1

  Expose GTIFGetPCSInfoEx(), GTIFGetProjTRFInfoEx(),
  GTIFGetGCSInfoEx(), GTIFGetDatumInfoEx(), GTIFGetEllipsoidInfoEx(),
  GTIFGetPMInfoEx(), GTIFGetUOMLengthInfoEx() and
  GTIFGetUOMAngleInfoEx() so that users can specify their own PROJ
  context

  Add GTIFKeyGetASCII(), GTIFKeyGetSHORT() and GTIFKeyGetDOUBLE() as
  safer variants of GTIFKeyGet() with type checking

  autotools build: enable build in a separate tree from source (#37)
  (fixes #28)

  Use pkg-config for libtiff detection

arpruss (8):
      support analog controllers
      optimize: move RGB conversion outside of point drawing code
      revert to original resolution
      nicer point shape
      allow scaling of vector display
      fix bug with y scale
      more flexibility in adjusting display (#37)

Update ruby-sshkey to 2.0.0.

pkgsrc change: add "USE_LANGUAGES=	# none".


2.0.0 (2019-02-11)

* Breaking Change: Drop support for Ruby 1.9
* Feature: Accept valid ed25519 keys with leading zero byte (#37)
* Feature: Support sshfp (#30)

What's Changed
 - Add NetBSD by @0323pin in #3
 - Migrate from tui-rs to ratatui by @AmmarAbouZor in #4
 - settings improvements by @AmmarAbouZor in #13
 - [Documentation] Create README Badges by @kevinmatthes in #14
 - CI Improvements by @AmmarAbouZor in #15
 - Changed: Help popup improvements by @AmmarAbouZor in #17
 - Added: Export current journal's content by @AmmarAbouZor in #18
 - Increase Version by @AmmarAbouZor in #19
 - Fixed setting backend path from CLI by @AmmarAbouZor in #22
 - Added: Release CD action by @AmmarAbouZor in #24
 - Fixed: Export journal extension by @AmmarAbouZor in #25
 - Changed: Enhance render loop by @AmmarAbouZor in #28
 - Added: CITATION.cff by @kevinmatthes in #26
 - Added: Edit current journal content in external editor by @AmmarAbouZor
   in #29
 - Added: configure CHANGELOG maintenance utilities by @kevinmatthes in #16
 - Added: Tabs and scrolling to help popup by @AmmarAbouZor in #32
 - Fixed: bugs in fragment creation by @kevinmatthes in #33
 - Added: Multi-selection for journals by @AmmarAbouZor in #34
 - Changed: bump baptiste0928/cargo-install to v2.1.0 by @kevinmatthes in #36
 - [Aeruginous] Create CHANGELOG Fragment by @github-actions in #37
 - Added: Export Import functions for multiple journals by @AmmarAbouZor in #39
 - [Aeruginous] Create CHANGELOG Fragment by @github-actions in #40
 - Fixed: Synchronizing problems with sqlite back-end by @AmmarAbouZor in #41
 - [Aeruginous] Create CHANGELOG Fragment by @github-actions in #42
 - Changed: improve GHA linting speed dramatically by @kevinmatthes in #43
 - [Aeruginous] Create CHANGELOG Fragment by @github-actions in #44
 - Addd: Option to Use Git Configured Editor as External editor by @AmmarAbouZor
   in #45
 - [Aeruginous] Create CHANGELOG Fragment by @github-actions in #46
 - [Aeruginous] Create Missing CHANGELOG Fragments by @AmmarAbouZor in #48
 - Chore: Add dependabot by @AmmarAbouZor in #50
 - [Aeruginous] Assemble CHANGELOG by @github-actions in #52

Upstream changes:
0.036 2023-05-10 17:09:48+02:00

    - Add option -dumpcode to turn of dumping coderefs in YAML::PP::Schema::Perl
    - ci updates

0.035 2022-09-30 21:16:16+02:00

    - Fix parsing alias as mapping key
    - Support emitting folded block scalars. Now any input should
      be able to output as a folded block scalar correctly. Preserving
      scalar styles will now also preserve those

0.034 2022-06-30 10:31:56+02:00

    - Fix parsing empty folded block scalars with trailing linebreaks
    - Fix error handling (remaining tokens on invalid input)
    - Support experimental v5.36 booleans
    - Allow to specify multiple boolean classes (issue #37)

0.033 2022-06-27 16:31:32+02:00

    - Fix add_mapping_resolver + on_create (tie existing data)

0.032 2022-03-08 19:02:00+01:00

    - Add missing '~' to allowed chars in tags
    - Restructure directive parsing a bit
    - Support YAML::PP::Ref in yamlpp-* utility scripts
    - Add -P to yaml-load-dump --preserve
    - Add --dump option to yamlpp-parse-emit
    - yamlpp-load-dump -D JSON::PP: don't output space before colon
    - Add export tags to YAML::PP::Common
    - Update yaml-test-suite to 2022-01-17

0.031 2021-12-25 23:43:19+01:00

    - Fix several rare test cases:
    - Support literal escaped tabs
    - Allow only one digit for block scalar indent indicator
    - Allow comments at the end of directives
    - Match word boundary after '%YAML'
    - Allow tabs and multiple spaces between directive elements
    - Forbid lines starting with tabs in block mode
    - After tabs no further indentation elements allowed

0.030 2021-11-07 21:57:28+01:00

    - preserve: Keep existing data (issue #44)
    - Forbid directive without directive end marker
    - Support explicit empty key/value pairs in flow mappings
    - Enforce EOL after end of flow context
    - Forbid multiple question marks in flow mappings

Updates
 - Moved Summary sorting key to 'X'
 - Added new key support 'X' on the Search page to cycle date types for
   searching
 - Support for verification and value stepping for all date types on the Seach
   page
 - Search page no longer auto-fills the date field
 - Fixed Search page matching partial tag, resulting in unrelated transactions
 - Transactions can now be deleted on the search page using 'D'
 - Transactions can now be edited on the search page using 'E'

Changes
 - Add NetBSD by @0323pin in #29
 - Update logo to make it round, small and transparent by @vlad-onis in #34
 - Fix db query by @TheRustyPickle in #37
 - Added searching by date, month, year by @TheRustyPickle in #38
 - Added edit and deleting function on search page directly by @TheRustyPickle
   in #39
 - Bump version by @TheRustyPickle in #40

What's Changed
 - stdout/stderr are now streamed as the subprocess is executing, rather than
   output only once the subprocess completes (#43).
 - NotFound errors during cleanup are now ignored (#42).
 - Improved error handling for malformed executables (#37).

API Changes
 - New methods Bkt::retrieve_streaming and Bkt::refresh_streaming have been
   added for library users that want to stream output, however these methods
   are subject to change and should be treated as experimental.

Upstream changes:
0.035   2023-10-03
        - PR #37 Speed up decode_jwt

0.3.2.1 — Oct 20, 2023
What's Changed

    Relax doctest boundaries. by @alaendle in #32
    GA(deps): Bump actions/checkout from 3 to 4 by @dependabot in #35
    Allow doctest-0.22 by @Vekhir in #36
    [#29] Support GHC 9.6 by @vrom911 in #33
    Support ghc-9.8 by @alaendle in #37
    Publish to hackage directly from GitHub by @alaendle in #38

New Contributors

    @Vekhir made their first contribution in co-log/co-log-core#36

Full Changelog: co-log/co-log-core@v0.3.2.0...v0.3.2.1

What's Changed
 - Update Usage by @tkna91 in #37
 - Fix #38

Upstream changes:
1.40     2023-11-04

- Rebuilt all locale data with the data from CLDR 44.0.1.


1.39     2023-05-28

- Fixed parsing of the 'el-polyton' locale code. This had the same issue as
  'be-tarask', which was fixed in 1.36. This is now fixed in such a way that
  similar `$language-$variant` codes will be parsed correctly in the
  future. Reported by @yvanzo. GH #37.

What's Changed
 - fix: line 8 for history by @thomas-mauran in #37
 - Add NetBSD by @0323pin in #39
 - docs: add contributing.md by @thomas-mauran in #40
 - Creates a much smaller final docker image by @jhauris in #41
 - feat: add "escape" event to helper menu by @charley04310 in #43
 - fix: do not allow selecting a chess piece with a not authorized move
   by @charley04310 in #45
 - Add Arch Linux install directions by @Rustmilian in #46
 - feat: home menu + credit + small fixes by @thomas-mauran in #47

Changes from changelog:

[4.16.0] 2024-01-14

 Added

- Include a check to prevent multiple entries with the same keys
  in 'bin/validate_json_data.py'
- Reuse translations from ISO 639-2 for ISO 639-5

 Changed

- Rename nb.po to nb_NO.po
- Rename mo.po to ro_MD.po
- Translation updates for ISO 3166-1
- Translation updates for ISO 3166-2
- Translation updates for ISO 3166-3
- Translation updates for ISO 639-2
- Translation updates for ISO 639-3
- Translation updates for ISO 639-5
- Translation updates for ISO 4217
- Translation updates for ISO 15924
- Reformat python files with black

 Fixed

- Fix: always use country code for parent in ISO 3166-2
- ISO 3166-2: Fix subdivision names for Finland. Fixes #37


[4.15.0] 2023-04-27

 Changed

- Translation updates for ISO 3166-1
- Translation updates for ISO 3166-3
- Translation updates for ISO 639-2


[4.14.0] 2023-04-27

 Changed

- Translation updates for ISO 3166-1
- Translation updates for ISO 3166-2
- Translation updates for ISO 3166-3
- Translation updates for ISO 639-2
- Translation updates for ISO 639-3
- Translation updates for ISO 639-5
- Translation updates for ISO 4217
- Translation updates for ISO 15924

 Fixed

* ISO 3166-2: Fix wrong Spanish translation


[4.13.0] 2023-02-28

 Added

- ISO 3166-1: Add missing common names for Laos, Iran, and Syria.
  Fixes #32

 Changed

- Translation updates for ISO 3166-1
  - Kazakh from Debian BTS. Closes: #1025423
  - Catalan from Debian BTS. Closes: #1026972
- Translation updates for ISO 3166-2
- Translation updates for ISO 3166-3
- Translation updates for ISO 639-2
- Translation updates for ISO 639-3
- Translation updates for ISO 639-5
- Translation updates for ISO 4217
- Translation updates for ISO 15924

 Fixed

- ISO 3166-3: Fix withdrawal dates of AN, CS and YU. Fixes #28


[4.12.0] 2022-11-06

 Changed

- ISO 3166-1: Update name for TR (Turkiye). Fixes #38
- Translation updates for ISO 3166-1
- Translation updates for ISO 3166-2. Closes: #1020633
- Translation updates for ISO 3166-3
- Translation updates for ISO 639-2
- Translation updates for ISO 639-3
- Translation updates for ISO 639-5
- Translation updates for ISO 4217
- Translation updates for ISO 15924

 Fixed

- ISO 3166-2: Remove comment from Dutch translation. Fixes #41

2.2.1 (2024-04-15)

What's Changed

* Document "methods" option with its type as a list of Symbols by
  @olleolleolle in #30
* Update docs reference to RaiseError middleware by @Drowze in #32
* Add Ruby 3.3 to CI matrix by @m-nakamura145 in #33
* Improve README.md about exceptions config by @mi-wada in #35
* Check for Faraday::UploadIO while rewinding by @iMacTia in #37
* Bump actions/checkout from 3 to 4 by @dependabot in #38

New Contributors

* @Drowze made their first contribution in #32
* @m-nakamura145 made their first contribution in #33
* @mi-wada made their first contribution in #35
* @dependabot made their first contribution in #38

Added support for HEREDOCs (#45)
Fixed an issue where whitespace after a line continuation causes parsing to fail (#26)
Fixed parsing a port range (#27)
Allow capital letters in user names (#35)
Added support for single-quoted strings (#37)
Fixed an issue where ADD and COPY only accepted a single parameter (#43)

0.1.32 (2024-05-15)

* Land #37, Update open_webrtc_browser to support using a user configurable
  browser

* Land #39, Upversion Github actions

* Land #40, Add support for Windows Ruby ucrt

# changes

* Codebase moved from OSDN to github.
* The shell can now open more file descriptors on Cygwin.
* Fixed the bug where the "typeset -fp" built-in prints parameter
  expansions of the form ${foo:/bar/baz} with a redundant # flag like
  ${foo:/#bar/baz}.
* Fixed the bug where the emacs-capitalize-word line-editing command
  misbehaves and possibly crashes the shell if there is no word following
  the cursor to be capitalized.
* Added the emacs-search-forward-current and emacs-search-backward-current
  line-editing commands. (by @vext01 in #37)
* [line-editing] Added the completion script for doas. (by @DanisDGK in #45)

### 1.8.10 - 15 June 2024

 * feature: new "`--output`" option to write to a file instead of standard output (pull request [#90](https://codeberg.org/a-j-wood/pv/pulls/90)) supplied by [xmort](https://codeberg.org/xmort)

### 1.8.9 - 21 April 2024

 * feature: new "`--si`" option to display and interpret size suffixes in multiples of 1000 rather than 1024 (pull request [#85](https://codeberg.org/a-j-wood/pv/pulls/85)) supplied by [kevinruddy](https://codeberg.org/kevinruddy)
 * fix: continue producing progress output when the output is blocking writes ([#34](https://codeberg.org/a-j-wood/pv/issues/34), [#86](https://codeberg.org/a-j-wood/pv/issues/86), [#87](https://codeberg.org/a-j-wood/pv/issues/87))
 * fix: honour the _TMPDIR_ / _TMP_ environment variables again, rather than hard-coding "`/tmp`", when using a terminal lock file (originally removed in 1.8.0) ([#88](https://codeberg.org/a-j-wood/pv/issues/88))
 * i18n: corrections and missing strings added to French translations (pull request [#83](https://codeberg.org/a-j-wood/pv/pulls/83)) supplied by [Thomas Bertels](https://codeberg.org/tbertels)

### 1.8.5 - 19 November 2023

 * fix: corrected percentage formatting so it doesn't jump from 2 to 3 characters wide at 100% ([#80](https://codeberg.org/a-j-wood/pv/issues/80))
 * fix: replaced "`--remote`" mechanism, using a temporary file instead of SysV IPC, so it can work reliably even when there are multiple PV instances
 * fix: corrected compilation failure when without IPC support
 * security: addressed all issues highlighted by the software auditing tools "`splint`" and "`flawfinder`" (see "`make analyse`") ([#77](https://codeberg.org/a-j-wood/pv/issues/77))
 * cleanup: compilation warnings fixed on non-IPC and MacOS systems

### 1.8.0 - 24 September 2023

#### Features

 * feature: new "`--discard`" option to discard input as if writing to */dev/null* ([#42](https://codeberg.org/a-j-wood/pv/issues/42))
 * feature: new "`--error-skip-block`" option to make "`--skip-errors`" skip whole blocks ([#37](https://codeberg.org/a-j-wood/pv/issues/37))
 * feature: use `posix_fadvise()` like `cat`(1) does, to improve efficiency ([#39](https://codeberg.org/a-j-wood/pv/issues/39))
 * feature: new "`--enable-static`" option to "`configure`" for static builds ([#75](https://codeberg.org/a-j-wood/pv/pull/75))

#### Security

 * security: with "`--pidfile`", write to a temporary file and rename it into place, to improve security
 * security: keep self-contained copies of name and format string in PV internal state for memory safety
 * security: ignore _TMP_ / _TMPDIR_ environment variables when using a terminal lock file

#### Fixes

 * fix: only report errors about missing files when starting to transfer from them, not while calculating size, and behave more like `cat`(1) by skipping them and moving on
 * fix: auto-calculate total line count with "`--line-mode`" when all inputs are regular files
 * fix: use `clock_gettime()` in ETA calculation to cope with machine suspend/resume ([#13](https://codeberg.org/a-j-wood/pv/issues/13))
 * fix: if "`--width`" or "`--height`" were provided, do not change them when the window size changes ([#36](https://codeberg.org/a-j-wood/pv/issues/36))
 * fix: when a file descriptor position in "`--watchfd`" moves backwards, show the rate using the correct prefix ([#41](https://codeberg.org/a-j-wood/pv/issues/41))
 * fix: rewrite terminal state save/restore so state is not intermittently garbled on exit when using "`--cursor`" ([#20](https://codeberg.org/a-j-wood/pv/issues/20)), ([#24](https://codeberg.org/a-j-wood/pv/issues/24))

#### Cleanups

 * cleanup: addressed many potential issues highlighted by the software auditing tools "`splint`" and "`flawfinder`" (see new target "`make analyse`")
 * cleanup: switched the build system to GNU Automake
 * cleanup: replaced the test harness with the one native to GNU Automake
 * cleanup: added a test for terminal width detection to "`make check`"
 * cleanup: added a test to "`make check`" to ensure that "`make install`" installs everything expected
 * cleanup: replaced *AC_HEADER_TIOCGWINSZ* with *AC_CHECK_HEADERS(sys/ioctl.h)* for better MacOS compatibility ([#74](https://codeberg.org/a-j-wood/pv/issues/74))
 * cleanup: with "`--sync`", call `fsync()` instead of `fdatasync()` on incapable systems ([#73](https://codeberg.org/a-j-wood/pv/issues/73))
 * cleanup: the manual is now a static file instead of needing to be built with "`configure`"

#### Dropped items

 * dropped: dropped support for "`--enable-static-nls`"
 * dropped: removed the Linux Software Map file, as the LSM project appears to be long dead
 * dropped: will no longer publish to SourceForge as it has a chequered history and is unnecessary
 * dropped: removed project from GitHub and moved to Codeberg - see "[Give Up GitHub](https://giveupgithub.org/)"

#### Other items

 * licensing change from Artistic 2.0 to GPLv3+

### 1.7.24 - 30 July 2023

 * fix: correct terminal size detection, broken in 1.7.17 by the configuration script rewrite ([#72](https://codeberg.org/a-j-wood/pv/issues/72))
 * security: removed *DEBUG* environment variable in debug mode, added "`--debug`" instead
 * cleanup: added "`make analyse`" to run "`splint`" and "`flawfinder`" on all source files
 * cleanup: corrected detection of boolean capability
 * cleanup: word wrapping of "`--help`" output is now multi-byte locale aware
 * cleanup: adjusted "`indent`" rules to line length of 120 and reformatted code

### 1.7.18 - 28 July 2023

 * fix: language file installation had been broken by the configuration script rewrite

### 1.7.17 - 27 July 2023

 * feature: new "`--sync`" option to flush cache to disk after every write (related to [#6](https://codeberg.org/a-j-wood/pv/issues/6), to improve accuracy when writing to slow disks)
 * feature: new "`--direct-io`" option to bypass cache - implements [#29 "Option to enable *O_DIRECT*"](https://codeberg.org/a-j-wood/pv/issues/29) - requested by Romain Kang, Jacek Wielemborek
 * fix: correct byte prefix size to 2 spaces in rate display, so progress display size remains constant at low transfer rates
 * cleanup: rewrote `configure.in` as per suggestions in newer "`autoconf`" manuals
 * cleanup: replaced `header.in` with one generated by "`autoheader`", moving custom logic to a separate header file "`config-aux.h`"
 * cleanup: added copyright notice to all source files as per GNU standards
 * cleanup: changed "`--version`" output to conform to GNU standards
 * cleanup: replaced backticks with `$()` in all shell scripts that did not come from elsewhere, as backticks are deprecated and harder to read
 * cleanup: improved the output formatting of "`make test`"
 * cleanup: extended the "`make test`" mechanism to allow certain tests to be skipped on platforms that cannot support them
 * cleanup: skip the "pipe" test (for *SIGPIPE*) if GNU "`head`" is not available, so that "`make test`" on stock OpenBSD 7.3 works
 * cleanup: added a lot more tests to "`make test`"
 * cleanup: replace all calls to `sprintf()` and `snprintf()` with a new wrapper function `pv_snprintf()` to improve security and compatibility
 * cleanup: replace all calls to `strcat()` with a wrapper `pv_strlcat()` to improve security and compatibility
 * cleanup: replace all `write()` calls to the terminal with a wrapper `pv_write_retry()` for consistency
 * cleanup: tidy up and fix compilation warning in "`--watchfd`" code
 * cleanup: rewrote all local shell scripts to pass analysis by [ShellCheck](https://www.shellcheck.net)

### 1.7.0 - 17 July 2023

 * dropped: support for Red Hat Enterprise Linux and its derivatives has been dropped; removed the RPM spec file, and will no longer build binaries
 * feature: the "`--size`" option now accepts "`@filename`" to use the size of another file (pull request [#57](https://codeberg.org/a-j-wood/pv/pull/57) supplied by [Dave Beckett](https://github.com/dajobe))
 * feature: the "`--watchfd`" option is now available on OS X (pull request [#60](https://codeberg.org/a-j-wood/pv/pull/60) supplied by [christoph-zededa](https://github.com/christoph-zededa))
 * feature: new "`--bits`" option to show bit count instead of byte count (adapted from pull request [#63](https://codeberg.org/a-j-wood/pv/pull/63) supplied by [Nick Black](https://nick-black.com))
 * feature: new "`--average-rate-window`" option, to set the window over which the average rate is calculated, also used for ETA (modified from pull request [#65](https://codeberg.org/a-j-wood/pv/pull/65) supplied by [lemonsqueeze](https://github.com/lemonsqueeze))
 * feature: the "`--watchfd`" option will now show relative filenames, if they are under the current directory (pull request [#66](https://codeberg.org/a-j-wood/pv/pull/66) supplied by [ikasty](https://github.com/ikasty))
 * fix: correction to `pv_in_foreground()` to behave as its comment block says it should, when not on a terminal - corrects [#19 "No output in Arch Linux initcpio after 1.6.6"](https://codeberg.org/a-j-wood/pv/issues/19), [#31 "No output written from inside zsh <() construct"](https://codeberg.org/a-j-wood/pv/issues/31), [#55 "pv Stopped Working in the Background"](https://codeberg.org/a-j-wood/pv/issues/55) (pull request [#64](https://codeberg.org/a-j-wood/pv/pull/64) supplied by [Michael Weiß](https://github.com/quitschbo))
 * fix: workaround for OS X 11 behaviour in configure script regarding stat64 at compile time (pull request [#57](https://codeberg.org/a-j-wood/pv/pull/57) supplied by [Dave Beckett](https://github.com/dajobe))
 * fix: workaround for macOS equivalence of stat to stat64 - patches from [Filippo Valsorda](https://github.com/FiloSottile) and [Demitri Muna](https://github.com/demitri), correcting [#33 "Fix compilation problems due to `stat64()` on Apple Silicon"](https://codeberg.org/a-j-wood/pv/issues/33)
 * fix: add burst rate limit to transfer, so rate limits are not broken by bursty traffic (pull request [#62](https://codeberg.org/a-j-wood/pv/pull/62) supplied by [Volodymyr Bychkovyak](https://github.com/vbychkoviak))
 * fix: corrected "`--force`" option so it will still output progress when not in the same process group as the owner of the terminal - corrects [#23 "No output with "`-f`" when run in background after 1.6.6"](https://codeberg.org/a-j-wood/pv/issues/23) and helps to correct [#31 "No output written from inside zsh <() construct"](https://codeberg.org/a-j-wood/pv/issues/31)
 * fix: corrected elapsed time display to show as D:HH:MM:SS after 1 day, like the ETA does - corrects [#16 "Show days in same format in ETA as in elapsed time"](https://codeberg.org/a-j-wood/pv/issues/16)
 * fix: corrected bug where percentages went down after 100% when in "`--numeric`" mode with a "`--size`" that was too small - corrects [#26 "Correct "`-n`" behaviour when going past 100% of "`-s`" size"](https://codeberg.org/a-j-wood/pv/issues/26)
 * i18n: recoded Polish translation file to UTF-8
 * i18n: removed inaccurate fuzzy translation matches
 * docs: moved all open issues into GitHub and updated the TODO list
 * docs: renamed README to README.md and altered it to Markdown format
 * docs: moved contributors from the README to docs/ACKNOWLEDGEMENTS.md
 * docs: moved TODO to TODO.md and altered it to Markdown format
 * docs: moved NEWS to NEWS.md, converted it to UTF-8, and altered it to Markdown format

0.4.6 (2024-07-20)

* Fix a missing link by @TO226 in #37
* Added Guix installation by @gemmaro in #40
* Add examples that work offline to the README by @kojix2 in #42
* readme: fix typo for "-o" option by @muxator in #47
* Fix typo: baplot -> barplot by @szarnyasg in #50
* docs: add nix command to installation by @thenbe in #51

Upstrean changes:
1.20 2023-12-28 Todd Rinaldo <toddr@cpan.org>
    * #32 - Skip t/pty_get_winsize.t tests on AIX
    * #27 - Fix patchlevel check for util.h

1.19 2023-12-28 Todd Rinaldo <toddr@cpan.org>
    * #37 - Remove --no-undefined from compiler test which is not compatible with all platforms.

# wk 0.9.4

- Ensure package tests pass against sf 1.0-18 (#224, #225).

# wk 0.9.3

- Ensure package compiles with `STRICT_R_HEADERS=1` (#222).

# wk 0.9.2

- Add `wk_crs()` and `wk_set_crs()` methods for `bbox` (#213)
- Fix wk_trans inconsistent meta flags handling (#217)
- Ensure package builds on arm64 for Windows (#220)

# wk 0.9.1

- Fix format strings/arguments for R-devel (#209).

# wk 0.9.0

## Breaking changes

- The common well-known binary representation of POINT EMPTY (i.e.,
  POINT (nan nan)) is now handled as POINT EMPTY allowing empty points
  to roundtrip through `wkb()` vectors (#196, #204).
- `xy(NA, NA)` is now read as a null feature instead of POINT EMPTY. This
  preserves the invariant that null features can also be identified using
  `is.na()` (#205).
- `xy(NaN, NaN)` is now read as POINT EMPTY and `is.na(xy(NaN, NaN))`
  now returns `FALSE`. This means that both EMPTY and null points can roundtrip
  through `xy()` (#205).

## Bugfixes and improvements

- `wk_meta()` now contains a new column `is_empty`, which is `TRUE`
  for any feature that contains at least one non-empty coordinate. This allows
  more efficient detection of features with zero coordinates (#197, #199).
- Updated PROJ data to use the latest pull of the database packaged with
  PROJ 9.3.0 (#201).
- The wk package now compiles once again on gcc 4.8 (#203, #206).
- Fixed `sfc_writer()` to correctly attach the `classes` attribute to
  sfc output with mixed geometry types (#195).
- Function `sfc_writer()` now has an argument `promote_multi` to write any
  input as the MULTI variant. This makes it more likely that an input vector
  will be read as a single geometry type (#198).
- The `wk_collection_filter()` now correctly increments the `part_id` when
  calling the child handler (@brownag, #194).

# wk 0.8.0

* Added `wkb_to_hex()` (@anthonynorth, #183).
* Implemented `vctrs::vec_proxy_equal()` for `wkb()` vctrs
  (@anthonynorth, #183).
* Fixed `sfc_writer()`, which had returned NULL for some inputs
  (e.g., via `wk_collection()`) (@anthonynorth, #182, #186).
* Added `wk_clockwise()` and `wk_counterclockwise()` to re-wind polygon rings
  (@anthonynorth, #188).
* New replacement-function mode for `wk_coords<-()` for in-place modification
  of coordinates (@mdsumner, #187).
* New function `wk_trans_explicit()` migrated from crs2crs (@mdsumner, #187).

# wk 0.7.3

* Fix tests for updated waldo package (#178).

# wk 0.7.2

* Fix use-after-free warnings.

# wk 0.7.1

* Fix implicit reliance on error `as.data.frame.default()`,
  which no longer occurs in r-devel (#166).

# wk 0.7.0

* Remove legacy headers that are no longer used by any downstream package
  (#146).
* `validate_wk_wkt()` now errors for an object that does not inherit from
  'wk_wkt' (#123, #146).
* Added `wk_crs_projjson()` to get a JSON representation of a CRS object.
  To make lookup possible based on shortcut-style CRS objects (e.g.,
  `"EPSG:4326"` or `4326`), added data objects `wk_proj_crs_view` and
  `wk_proj_crs_json` that contain cached versions of rendered PROJJSON
  based on the latest PROJ version (#147).
* Added a `wk_crs_proj_definition()` method for `wk_crs_inherit()` (#136,
  #147).
* Conversion to sf now uses the `sfc_writer()` for all wk classes, making
  conversions faster and fixing at least one issue with conversion of NA
  geometries to sf (#135).
* `wk_plot()` now plots `NULL`/`NA` geometries and mixed geometry types
  more reliably (#142, #143, #149).
* Exported EMPTY geometries to well-known text now include dimension
  (e.g., `POINT Z EMPTY`) (#141, #150).
* Fixed bug where `wk_polygon()` doubled some points when the input contained
  closed rings (#134, #151).
* Fixed bug where `wk_count()` exposed uninitialized values for empty input
  (#139, #153).
* The `xy_writer()` now opportunistically avoids allocating vectors for Z
  or M values unless they are actually needed (#131, #154).
* Added example WKT for all geometry types and dimensions plus helper
  `wk_example()` to access them and set various properties (#155).
* Fixes warnings when compiling with `-Wstrict-prototypes` (#157, #158).
* Removed `wk_chunk_map_feature()` in favour of using chunking strategies
  directly (#132, #159).
* Optimized `wk_coords()` for `xy()` objects (#138, #160).
* Added accessor methods for record-style vectors: `rct_xmin()`, `rct_xmax()`,
  `rct_ymin()`, `rct_ymax()`, `rct_width()`, `rct_height()`, `crc_center()`,
  `crc_x()`, `crc_y()`, `crc_r()`, `xy_x()`, `xy_y()`, `xy_z()`, and `xy_m()`
  (#144, #161).
* Added rectangle operators `rct_intersects()`, `rct_contains()`,
  and `rct_intersection()` (#161).

# wk 0.6.0

* Fixed `wk_affine_rescale()` to apply the translate and scale
  operations in the correct order (#94).
* Add `wk_handle_slice()` and `wk_chunk_map_feature()` to support
  a chunk + apply workflow when working with large vectors (#101, #107).
* C and R code was rewritten to avoid materializing ALTREP vectors
  (#103, #109).
* Added a `wk_crs_proj_definition()` generic for foreign CRS objects
  (#110, #112).
* Added `wk_crs_longlat()` helper to help promote authority-compliant
  CRS choices (#112).
* Added `wk_is_geodesic()`, `wk_set_geodesic()`, and argument `geodesic`
  in `wkt()` and `wkb()` as a flag for objects whose edges must
  be interpolated along a spherical/ellipsoidal trajectory (#112).
* Added `sf::st_geometry()` and `sf::st_sfc()` methods for wk geometry
  vectors for better integration with sf (#113, #114).
* Refactored well-known text parser to be more reusable and faster
  (#115, #104).
* Minor performance enhancement for `is.na()` and `validate_wk_wkb()`
  when called on a very long `wkb()` vector (#117).
* Fixed issue with `validate_wk_wkb()` and `validate_wk_wkt()`, which failed
  for most valid objects (#119).
* Added `wk_envelope()` and `wk_envelope_handler()` to compute feature-wise
  bounding boxes (#120, #122).
* Fixed headers and tests to pass on big endian systems (#105, #122).
* Incorporated the geodesic attribute into vctrs methods, data frame
  columns, and bbox/envelope calculation (#124, #125).
* Fix `as_xy()` for nested data frames and geodesic objects (#126, #128).
* Remove deprecated `wkb_problems()`, `wkt_problems()`, `wkb_format()`,
  and `wkt_format()` (#129).
* `wk_plot()` is now an S3 generic (#130).

# wk 0.5.0

* Fixed bugs relating to the behaviour of wk classes as
  vectors (#64, #65, #67, #70).
* `crc()` objects are now correctly exported as polygons
  with a closed loop (#66, #70).
* Added `wk_vertices()` and `wk_coords()` to extract individual
  coordinate values from geometries with optional identifying
  information. For advanced users, the `wk_vertex_filter()`
  can be used as part of a pipeline to export coordinates
  as point geometries to another handler (#69, #71).
* Added `wk_flatten()` to extract geometries from collections.
  For advanced users, the `wk_flatten_filter()` can be used as
  part of a pipeline (#75, #78).
* `options("max.print")` is now respected by all vector classes
  (#72, #74).
* Moved implementation of plot methods from wkutils to wk to
  simplify the dependency structure of both packages (#80, #76).
* Added `wk_polygon()`, `wk_linestring()`, and `wk_collection()`
  to construct polygons, lines, and collections. For advanced
  users, `wk_polygon_filter()`, `wk_linestring_filter()`, and
  `wk_collection_filter()` can be used as part of a pipeline
  (#77, #84).
* Added a C-level transform struct that can be used to simplify
  the the common pattern of transforming coordinates. These
  structs can be created by other packages; however, the
  `wk_trans_affine()` and `wk_trans_set()` transforms are
  also built using this feature. These are run using the
  new `wk_transform()` function and power the new
  `wk_set_z()`, `wk_set_m()`, `wk_drop_z()`, `wk_drop_m()`,
  functions (#87, #88, #89).

# wk 0.4.1

* Fix LTO and MacOS 3.6.2 check errors (#61).

# wk 0.4.0

* Removed `wksxp()` in favour of improved `sf::st_sfc()` support
  (#21).
* Rewrite existing readers, writers, and handlers, using
  a new C API (#13).
* Use new C API in favour of header-only approach for all
  wk functions (#19, #22).
* Use cpp11 to manage safe use of callables that may longjmp
  from C++.
* Vector classes now propagate `attr(, "crs")`, and check
  that operations that involve more than one vector have
  compatable CRS objects as determined by `wk_crs_equal()`.
* Added an R-level framework for other packages to implement
  wk readers and handlers: `wk_handle()`, `wk_translate()`,
  and `wk_writer()` (#37).
* Added a native reader and writer for `sf::st_sfc()` objects
  and implemented R-level generics for sfc, sfg, sf, and bbox
  objects (#28, #29, #38, #45).
* Implement `crc()` vector class to represent circles (#40).
* Added a 2D cartesian bounding box handler (`wk_bbox()`) (#42).
* Refactored unit tests reflecting use of the new API and
  for improved test coverage (#44, #45, #46).
* Added `wk_meta()`, `wk_vector_meta()`, and `wk_count()` to
  inspect properties of vectors (#53).
* Modified all internal handlers such that they work with vectors
  of unknown length (#54).

# wk 0.3.4

* Fixed reference to `wkutils::plot.wk_wksxp()`, which
  no longer exists.

# wk 0.3.3

* Fixed WKB import of ZM geometries that do not use EWKB.
* Added `xy()`, `xyz()`, `xym()` and `xyzm()` classes
  to efficiently store point geometries.
* Added the `rct()` vector class to efficiently store
  two-dimensional rectangles.
* Fixed the CRAN check  failure caused by a circular
  dependency with  the wkutils package.
* Added S3 methods to coerce sf objects to and from
  `wkt()`, `wkb()` and `wksxp()`.

# wk 0.3.2

* Fixed EWKB output for collections and multi-geometries
  that included SRID (#3).
* Fixed CRAN check errors related to exception handling on
  MacOS/R 3.6.2.

# wk 0.3.1

* Added a `NEWS.md` file to track changes to the package.

net/transmission-gtk: security update
net/transmission-qt: security update
net/transmission: security update

Revisions pulled up:
- net/transmission-gtk/Makefile                                 1.46
- net/transmission-gtk/PLIST                                    1.2
- net/transmission-qt/Makefile                                  1.54
- net/transmission/Makefile                                     1.27
- net/transmission/Makefile.common                              1.10
- net/transmission/PLIST                                        1.4
- net/transmission/distinfo                                     1.16
- net/transmission/patches/patch-qt_qtr.pro                     1.7

-------------------------------------------------------------------
   Module Name:	pkgsrc
   Committed By:	wiz
   Date:		Mon Jul 13 13:01:02 UTC 2020

   Modified Files:
   	pkgsrc/net/transmission: Makefile Makefile.common PLIST distinfo
   	pkgsrc/net/transmission-gtk: Makefile PLIST
   	pkgsrc/net/transmission-qt: Makefile
   	pkgsrc/net/transmission/patches: patch-qt_qtr.pro

   Log Message:
   transmission*: update to 3.00

   ### All Platforms
   - Allow the RPC server to listen on an IPv6 address ([#161](transmission/transmission#161))
   - Change `TR_CURL_SSL_VERIFY` to `TR_CURL_SSL_NO_VERIFY` and enable verification by default ([#334](transmission/transmission#334))
   - Go back to using hash as base name for resume and torrent files (those stored in configuration directory) ([#122](transmission/transmission#122))
   - Handle "fields" argument in "session-get" RPC request; if "fields" array is present in arguments, only return session fields specified; otherwise return all the fields as before
   - Limit the number of incorrect authentication attempts in embedded web server to 100 to prevent brute-force attacks ([#371](transmission/transmission#371))
   - Set idle seed limit range to 1..40320 (4 weeks tops) in all clients ([#212](transmission/transmission#212))
   - Add Peer ID for Xfplay, PicoTorrent, Free Download Manager, Folx, Baidu Netdisk torrent clients ([#256](transmission/transmission#256), [#285](transmission/transmission#285), [#355](transmission/transmission#355), [#363](transmission/transmission#363), [#386](transmission/transmission#386))
   - Announce `INT64_MAX` as size left if the value is unknown (helps with e.g. Amazon S3 trackers) ([#250](transmission/transmission#250))
   - Add `TCP_FASTOPEN` support (should result in slight speedup) ([#184](transmission/transmission#184))
   - Improve ToS handling on IPv6 connections ([#128](transmission/transmission#128), [#341](transmission/transmission#341), [#360](transmission/transmission#360), [#692](transmission/transmission#692), [#737](transmission/transmission#737))
   - Abort handshake if establishing DH shared secret fails (leads to crash) ([#27](transmission/transmission#27))
   - Don't switch trackers while announcing (leads to crash) ([#297](transmission/transmission#297))
   - Improve completion scripts execution and error handling; add support for .cmd and .bat files on Windows ([#405](transmission/transmission#405))
   - Maintain a "session ID" file (in temporary directory) to better detect whether session is local or remote; return the ID as part of "session-get" response (TRAC-5348, [#861](transmission/transmission#861))
   - Change torrent location even if no data move is needed ([#35](transmission/transmission#35))
   - Support CIDR-notated blocklists ([#230](transmission/transmission#230), [#741](transmission/transmission#741))
   - Update the resume file before running scripts ([#825](transmission/transmission#825))
   - Make multiscrape limits adaptive ([#837](transmission/transmission#837))
   - Add labels support to libtransmission and transmission-remote ([#822](transmission/transmission#822))
   - Parse `session-id` header case-insensitively ([#765](transmission/transmission#765))
   - Sanitize suspicious path components instead of rejecting them ([#62](transmission/transmission#62), [#294](transmission/transmission#294))
   - Load CA certs from system store on Windows / OpenSSL ([#446](transmission/transmission#446))
   - Add support for mbedtls (formely polarssl) and wolfssl (formely cyassl), LibreSSL ([#115](transmission/transmission#115), [#116](transmission/transmission#116), [#284](transmission/transmission#284), [#486](transmission/transmission#486), [#524](transmission/transmission#524), [#570](transmission/transmission#570))
   - Fix building against OpenSSL 1.1.0+ ([#24](transmission/transmission#24))
   - Fix quota support for uClibc-ng 1.0.18+ and DragonFly BSD ([#42](transmission/transmission#42), [#58](transmission/transmission#58), [#312](transmission/transmission#312))
   - Fix a number of memory leaks (magnet loading, session shutdown, bencoded data parsing) ([#56](transmission/transmission#56))
   - Bump miniupnpc version to 2.0.20170509 ([#347](transmission/transmission#347))
   - CMake-related improvements (Ninja generator, libappindicator, systemd, Solaris and macOS) ([#72](transmission/transmission#72), [#96](transmission/transmission#96), [#117](transmission/transmission#117), [#118](transmission/transmission#118), [#133](transmission/transmission#133), [#191](transmission/transmission#191))
   - Switch to submodules to manage (most of) third-party dependencies
   - Fail installation on Windows if UCRT is not installed

   ### Mac Client
   - Bump minimum macOS version to 10.10
   - Dark Mode support ([#644](transmission/transmission#644), [#722](transmission/transmission#722), [#757](transmission/transmission#757), [#779](transmission/transmission#779), [#788](transmission/transmission#788))
   - Remove Growl support, notification center is always used ([#387](transmission/transmission#387))
   - Fix autoupdate on High Sierra and up by bumping the Sparkle version ([#121](transmission/transmission#121), [#600](transmission/transmission#600))
   - Transition to ARC ([#336](transmission/transmission#336))
   - Use proper UTF-8 encoding (with macOS-specific normalization) when setting download/incomplete directory and completion script paths ([#11](transmission/transmission#11))
   - Fix uncaught exception when dragging multiple items between groups ([#51](transmission/transmission#51))
   - Add flat variants of status icons for message log ([#134](transmission/transmission#134))
   - Optimize image resources size ([#304](transmission/transmission#304), [#429](transmission/transmission#429))
   - Update file icon when file name changes ([#37](transmission/transmission#37))
   - Update translations

   ### GTK+ Client
   - Add queue up/down hotkeys ([#158](transmission/transmission#158))
   - Modernize the .desktop file ([#162](transmission/transmission#162))
   - Add AppData file ([#224](transmission/transmission#224))
   - Add symbolic icon variant for the Gnome top bar and when the high contrast theme is in use ([#414](transmission/transmission#414), [#449](transmission/transmission#449))
   - Update file icon when its name changes ([#37](transmission/transmission#37))
   - Switch from intltool to gettext for translations ([#584](transmission/transmission#584), [#647](transmission/transmission#647))
   - Update translations, add new translations for Portuguese (Portugal)

   ### Qt Client
   - Bump minimum Qt version to 5.2
   - Fix dropping .torrent files into main window on Windows ([#269](transmission/transmission#269))
   - Fix prepending of drive letter to various user-selected paths on Windows ([#236](transmission/transmission#236), [#307](transmission/transmission#307), [#404](transmission/transmission#404), [#437](transmission/transmission#437), [#699](transmission/transmission#699), [#723](transmission/transmission#723), [#877](transmission/transmission#877))
   - Fix sorting by progress in presence of magnet transfers ([#234](transmission/transmission#234))
   - Fix .torrent file trashing upon addition ([#262](transmission/transmission#262))
   - Add queue up/down hotkeys ([#158](transmission/transmission#158))
   - Reduce torrent properties (file tree) memory usage
   - Display tooltips in torrent properties (file tree) in case the names don't fit ([#411](transmission/transmission#411))
   - Improve UI look on hi-dpi displays (YMMV)
   - Use session ID (if available) to check if session is local or not ([#861](transmission/transmission#861))
   - Use default (instead of system) locale to be more flexible ([#130](transmission/transmission#130))
   - Modernize the .desktop file ([#162](transmission/transmission#162))
   - Update translations, add new translations for Afrikaans, Catalan, Danish, Greek, Norwegian Bokmål, Slovenian

   ### Daemon
   - Use libsystemd instead of libsystemd-daemon (TRAC-5921)
   - Harden transmission-daemon.service by disallowing privileges elevation ([#795](transmission/transmission#795))
   - Fix exit code to be zero when dumping settings ([#487](transmission/transmission#487))

   ### Web Client
   - Fix tracker error XSS in inspector (CVE-?)
   - Fix performance issues due to improper use of `setInterval()` for UI refresh (TRAC-6031)
   - Fix recognition of `https://` links in comments field ([#41](transmission/transmission#41), [#180](transmission/transmission#180))
   - Fix torrent list style in Google Chrome 59+ ([#384](transmission/transmission#384))
   - Show ETA in compact view on non-mobile devices ([#146](transmission/transmission#146))
   - Show upload file button on mobile devices ([#320](transmission/transmission#320), [#431](transmission/transmission#431), [#956](transmission/transmission#956))
   - Add keyboard hotkeys for web interface ([#351](transmission/transmission#351))
   - Disable autocompletion in torrent URL field ([#367](transmission/transmission#367))

   ### Utils
   - Prevent crash in transmission-show displaying torrents with invalid creation date ([#609](transmission/transmission#609))
   - Handle IPv6 RPC addresses in transmission-remote ([#247](transmission/transmission#247))
   - Add `--unsorted` option to transmission-show ([#767](transmission/transmission#767))
   - Widen the torrent-id column in transmission-remote for cleaner formatting ([#840](transmission/transmission#840))


   To generate a diff of this commit:
   cvs rdiff -u -r1.26 -r1.27 pkgsrc/net/transmission/Makefile
   cvs rdiff -u -r1.9 -r1.10 pkgsrc/net/transmission/Makefile.common
   cvs rdiff -u -r1.3 -r1.4 pkgsrc/net/transmission/PLIST
   cvs rdiff -u -r1.15 -r1.16 pkgsrc/net/transmission/distinfo
   cvs rdiff -u -r1.45 -r1.46 pkgsrc/net/transmission-gtk/Makefile
   cvs rdiff -u -r1.1 -r1.2 pkgsrc/net/transmission-gtk/PLIST
   cvs rdiff -u -r1.52 -r1.53 pkgsrc/net/transmission-qt/Makefile
   cvs rdiff -u -r1.6 -r1.7 pkgsrc/net/transmission/patches/patch-qt_qtr.pro
-------------------------------------------------------------------
   Module Name:    pkgsrc
   Committed By:   wiz
   Date:           Sat Jul 25 20:20:05 UTC 2020

   Modified Files:
           pkgsrc/net/transmission-qt: Makefile

   Log Message:
   transmission-qt: needs gcc 7.x (for <optional>)

   Reported and tested by spz.


   To generate a diff of this commit:
   cvs rdiff -u -r1.53 -r1.54 pkgsrc/net/transmission-qt/Makefile

# Rdpack 2.6.2

- `RStudio_reprompt` now issues a more informative error message when not called
  on a suitable file or function. Fixes issue #30, reported by @daattali.

- now the LaTeX macro `\slash` is wrapped in a condition, so that it is passed
  on for LaTeX related output but converted to `/` for other formats (such as
  html). Fixes GeoBosh/rbibutils#9, reported by @MLopez-Ibanez.

- fixed the test for the fix in Rdpack v2.6.1 (see below) to work with R-4.4.2,
  since that R-devel change was not carried on to R-4.4.2.  (Note: the error
  concerns the test only. The fix in the code of the package works for any R
  version.) Fixes issue #37, reported by @charles-plessy.


# Rdpack 2.6.1

- R-devel c86938 turned to error the warning for a non-existing key in the bib
  file. Fixed `insert_bib` (and a related test) to handle that.


# Rdpack 2.6

- fixed issues causing 'lost braces' (actually, superfluous braces) NOTEs from
  checks in R-devel occuring with some accented LaTeX characters. These NOTEs
  are not yet activated on CRAN but if/when they do, developers using Rd macros
  `\insertRef` and `\insertCite` can eliminate them by building their packages
  with Rdpack (>= 2.6) and rbibutils (>= 2.2.16).  Thanks to Sebastian Meyer for
  tracing down the issues.

- fixed a `Sweave` expression in 'man/predefined.Rd' to not emit unnecessary
  braces (see the note above).


# Rdpack 2.5

- Rd macros `insertCite` and friends were calling `\insert_citeOnly()` with
  argument `key` instead of `keys`. This was not an error since partial matching
  is ok here but not good practice. Fixes issue #28 reported by Marcel Ramos.

- changed the saved value in "tests/testthat/dummyArticle.rds" used in
  'test-bib.R' with a value obtained with R-devel r84896 n previu versins of R
  there wasasuperfluous final ' .').

- in some cases when square brackets were requested, rather than round ones,
  `\insertCiteOnly` was using closing round parenthesis.

- in some cases `\insertCiteOnly` was not handling well the last cite when it
  was followed by free text.

# bit64 4.6.0-1

## NOTICE OF PLANNED BREAKING CHANGES

1. {bit64} exports many S3 methods directly. Calling S3 methods
directly is generally bad form; we should rely on the S3 dispatch
system for this. Needing to export an S3 method is usually indicative
of some deep issue that's otherwise hard to work around.

  I plan to un-export most if not all S3 methods in future
  versions. In this release, there will be no change in behavior
  besides this notice in the NEWS. Going forward, I see two types of
  S3 exports: (1) exports that have no discoverable direct usage (that
  is, a global GitHub search, which includes the CRAN mirror, turned
  up _no_ R code calling them directly, except perhaps in `:::` form,
  which would be unaffected by un-export); and (2) exports that _are_
  observed to be called directly by some number of downstreams. With
  the former, I am more comfortable un-exporting more aggressively;
  with the latter, I will take a more gradual approach.

  Here are the S3 methods that are currently exported, for which I
  found no record of them being called directly:

  `-.integer64`, `:.default`, `:.integer64`, `!.integer64`,
  `!=.integer64`, `[.integer64`, `[[.integer64`, `[[<-.integer64`,
  `*.integer64`, `/.integer64`, `&.integer64`, `%/%.integer64`,
  `%%.integer64`, `%in%.default`, `%in%.integer64`, `^.integer64`,
  `+.integer64`, `<.integer64`, `<=.integer64`, `==.integer64`,
  `>.integer64`, `>=.integer64`, `|.integer64`, `all.equal.integer64`,
  `as.bitstring.integer64`, `as.integer64.factor`,
  `as.integer64.integer64`, `as.integer64.NULL`, `as.list.integer64`,
  `as.logical.integer64`, `cbind.integer64`, `ceiling.integer64`,
  `cummax.integer64`, `cummin.integer64`, `cumprod.integer64`,
  `cumsum.integer64`, `diff.integer64`, `duplicated.integer64`,
  `floor.integer64`, `hashdup.cache_integer64`,
  `hashfin.cache_integer64`, `hashfun.integer64`, `hashmap.integer64`,
  `hashmaptab.integer64`, `hashmapuni.integer64`,
  `hashmapupo.integer64`, `hashpos.cache_integer64`,
  `hashrev.cache_integer64`, `hashrin.cache_integer64`,
  `hashtab.cache_integer64`, `hashuni.cache_integer64`,
  `hashupo.cache_integer64`, `is.double.default`,
  `is.double.integer64`, `is.finite.integer64`,
  `is.infinite.integer64`, `is.nan.integer64`, `is.sorted.integer64`,
  `is.vector.integer64`, `keypos.integer64`, `length<-.integer64`,
  `log10.integer64`, `log2.integer64`, `match.default`,
  `match.integer64`, `mean.integer64`, `median.integer64`,
  `mergeorder.integer64`, `mergesort.integer64`,
  `mergesortorder.integer64`, `na.count.integer64`, `nties.integer64`,
  `nunique.integer64`, `nvalid.integer64`, `order.default`,
  `order.integer64`, `orderdup.integer64`, `orderfin.integer64`,
  `orderkey.integer64`, `ordernut.integer64`, `orderpos.integer64`,
  `orderqtl.integer64`, `orderrnk.integer64`, `ordertab.integer64`,
  `ordertie.integer64`, `orderuni.integer64`, `orderupo.integer64`,
  `prank.integer64`, `print.bitstring`, `prod.integer64`,
  `qtile.integer64`, `quantile.integer64`, `quickorder.integer64`,
  `quicksort.integer64`, `quicksortorder.integer64`,
  `radixorder.integer64`, `radixsort.integer64`,
  `radixsortorder.integer64`, `ramorder.integer64`,
  `ramsort.integer64`, `ramsortorder.integer64`, `range.integer64`,
  `rank.default`, `rbind.integer64`, `round.integer64`,
  `scale.integer64`, `shellorder.integer64`, `shellsort.integer64`,
  `shellsortorder.integer64`, `sign.integer64`, `signif.integer64`,
  `sort.integer64`, `sortfin.integer64`, `sortnut.integer64`,
  `sortorderdup.integer64`, `sortorderkey.integer64`,
  `sortorderpos.integer64`, `sortorderrnk.integer64`,
  `sortordertab.integer64`, `sortordertie.integer64`,
  `sortorderuni.integer64`, `sortorderupo.integer64`,
  `sortql.integer64`, `sorttab.integer64`, `sortuni.integer64`,
  `sqrt.integer64`, `summary.integer64`, `table.integer64`,
  `tiepos.integer64`, `trunc.integer64`, `unipos.integer64`

  Here are the S3 methods that are currently exported for which I _do_
  find record of them being called directly:

  `abs.integer64`, `as.character.integer64`,
  `as.data.frame.integer64`, `as.double.integer64`,
  `as.integer.integer64`, `as.integer64.bitstring`,
  `as.integer64.character`, `as.integer64.double`,
  `as.integer64.integer`, `as.integer64.logical`, `c.integer64`,
  `format.integer64`, `identical.integer64`, `is.na.integer64`,
  `lim.integer64`, `max.integer64`, `min.integer64`,
  `print.integer64`, `rank.integer64`, `seq.integer64`,
  `str.integer64`, `sum.integer64`, `unique.integer64`

  In the next release (provisionally, 4.7.0), I will add a `warning()`
  to any S3 method in the former classification, while nothing will
  change for the latter classification. I may reach out to authors
  observed to call the methods directly.

  In the subsequent release (provisionally, 4.8.0), I will un-export
  any S3 method in the former classification, and add a `warning()` to
  any S3 method in the latter classification.

  In the sub-subsequent release (provisionally, 4.9.0), I will
  un-export any S3 method in the latter classification.

  Please reach out (e.g., the GitHub log for #76) if you have any
  concerns about this plan.

  1. {bit64} lists {bit} as `Depends:`. IMO this form of dependency
  should be deprecated by R now that `Imports:` is widely available and
  well-supported for many years.

  In the next release (provisionally, 4.7.0), I will move bit to
  Imports. The practical implication is that currently,
  `library(bit64)` will make {bit} objects like `is.bit()` available
  for use without namespace-qualification. This practice makes code
  harder to read and maintain.

  Users relying on this in scripts can (1) write `library(bit)` to
  attach {bit} explicitly or (2) namespace-qualify all {bit} calls
  with `bit::`.

  Package authors relying on this can (1) add `import(bit)` to make
  the full {bit} namespace available or (2) namespace-qualify all
  {bit} calls with `bit::`; adding {bit} to `Imports:` or `Suggests:`
  will also be necessary.

  I will reach out to CRAN authors with any required
  changes. Depending on the impact size, I might make this transition
  more gradual (e.g. starting by re-exporting some or all {bit}
  functions from {bit64}, with warning, before un-exporting them in a
  subsequent release).

## NEW FEATURES

1. Implemented S3 methods for `rowSums()` and `colSums()`. Importantly
they handle `NA` values correctly, #38. Thanks @vlulla for the
request. Note that these are implemented as wrappers to `apply()`
calls, so they may not be as efficient. PRs welcome for implementing
the efficient equivalents.

  Note that by necessity, this grows the set of base exports
  overwritten to include `rowSums()` and `colSums()`, which are
  exported as S3 generics dispatching to `base::rowSums()` and
  `base::colSums()` by default.

1. Partially powering this is a new `aperm()` method for integer64
which allows `apply()` to work as intended. Using `apply()` directly
may still strip the integer64 class; that may be supported later (see
#87).

1. `is.na()` is supported for long vector input (more than `2^31`
elements), #30. Thanks @ilia-kats for the request. Long vector support
will be added on an as-needed basis as I don't have a great machine
for testing these features -- PRs welcome!

## BUG FIXES

1. `all.equal.integer64()` gets the same fix for vector `scale=` to
work as intended that `all.equal.numeric()` got in R 4.1.3, #23.

1. Made edits to `match()` to handle `is.integer64(table)` better for
older versions of R, including a new `mtfrm()` method for integer64
objects in R>=4.2.0, #85 and #111.

## NOTES

1. After creating, developing, and maintaining {bit64} for about 13
years, Jens Oehlschlägel has decided to step down as maintainer of the
package. Michael Chirico will take over in this duty. Thank you Jens
for creating such a wonderful & important part of the R ecosystem!

  I don't have any major plans for new features, and mostly hope to
  keep the package running and up to date. Contributors most welcome!
  I am also trying to freshen up the code base to make contribution
  easier.

1. The R version dependency has increased from 3.0.1 (May 2013) to
3.4.0 (April 2017). We plan to keep roughly the same R dependency as
{data.table}, i.e., as old as possibly for as long as possible, with
some bias towards gradually bringing in new R features to reduce the
maintenance overhead of a growing nest of workarounds to keep the
package "fresh" for users of the latest R versions.

  Required package {bit} already requires R 3.4.0, so the old 3.0.1
  requirement was effectively impossible anyway.

1. Default packages {methods}, {stats}, and {utils} are now
`Imports:`, not `Depends:`, dependencies. `Depends:` is an out-dated
mode of dependency in R. This will only affect the small audience of
users that run R with `R_DEFAULT_PACKAGES=NULL` (or some other subset
excluding some of these three), _and_ who are relying (perhaps
implicitly) on {bit64} being responsible for attaching those packages.

  It is my intention to move {bit} from `Depends:` to `Imports:` as
  well, but this migration will be done more gingerly -- it is more
  conceivable that this will constitute a breaking change for some use
  cases, therefore it will be done in phases. Nothing is done in this
  release, but here is your earliest warning that from the next
  release, it will be a warning to rely on {bit64} to attach {bit}
  functions for you.

1. Package documentation is now managed with {roxygen2}, #61. I tried
to retain everything in the original documentation, but the diff
required to do so was quite unmanageable (5,000+ lines), so please
alert me if anything looks amiss. Most importantly, I ensured the
NAMESPACE remains unchanged.

1. The signature of `identical.integer64()` loses `extptr.as.ref=`,
which is unavailable for R<4.2.0, but gains `...` to allow this
argument in newer versions, #37. This retains the transparency of
having all arguments named in the signature (and thus in
`?identical.integer64` as well as available for tab-completion) while
also retaining the old R version dependency R 3.3.0.

# bit64 NEWS for versions 0.8-3 through 4.5.2 are now in
  [NEWS.0](https://github.com/r-lib/bit64/blob/master/NEWS.0)

v2.0.0 (2025-02-09)

Breaking

    refactor!: rename python package serializable -> py_serializable (#155)

    The python package was renamed from serializable to py_serializable.
    Therefore, you need to adjust your imports.

    The following shows a quick way to adjust imports in the most efficient way.
    OLD imports

    import serializable
    from serializable import ViewType, XmlArraySerializationType, XmlStringSerializationType
    from serializable.helpers import BaseHelper, Iso8601Date

ADJUSTED imports

import py_serializable as serializable
from py_serializable import ViewType, XmlArraySerializationType, XmlStringSerializationType
from py_serializable.helpers import BaseHelper, Iso8601Date

    see migration path: https://py-serializable.readthedocs.io/en/refactor-rename-installable-py_serializable/migration.html

Unknown

    Delete duplicate CODEOWNERS (#156)

    we have a codeowners file in root already (b64cdde)

What's Changed

    chore(deps-dev): update mypy requirement from 1.11.2 to 1.12.0 by @dependabot in #143
    chore(deps-dev): update mypy requirement from 1.12.0 to 1.13.0 by @dependabot in #145
    chore(deps-dev): update flake8-bugbear requirement from 24.8.19 to 24.10.31 by @dependabot in #146
    chore(deps-dev): update flake8-bugbear requirement from 24.10.31 to 24.12.12 by @dependabot in #150
    chore(deps-dev): update mypy requirement from 1.13.0 to 1.14.1 by @dependabot in #154
    Delete duplicate CODEOWNERS by @jkowalleck in #156
    chore(docs): chanelog contains only relevant by @jkowalleck in #157
    chore(docs): recreate changelog by @jkowalleck in #158
    chore(deps): bump actions/upload-artifact from 3 to 4 by @dependabot in #37
    refactor!: rename python package serializable -> py_serializable by @jkowalleck in #155
    chore(deps): update sphinx requirement from <8,>=7.2.6 to >=7.2.6,<9 by @dependabot in #127

What's Changed

    refactor: Adds parallel loops to make the parsing faster by @farhaanbukhsh in #36
    fix: spinner now runs only when tasks are being executed by @ashish10677 in #37
    [Config] Add configurability to Feluda by @kageiit in #38
    Support multiple project types at once by @kageiit in #39
    Add pyproject toml support by @kageiit in #40
    Optimizing the go-parser by @farhaanbukhsh in #41

Update provided by Anthony Mallet on pkgsrc-users.

        * dJointAddPUTorques() was added to replace orphaned declaration of
          dJointAddPUTorque()
        * Fixed wrong face index being returned in convex-trimesh libCCD
          collision check routine.
        * Fixed use of potentially outdated AABBs in GIIMPACT cylinder-trimesh
          collision check routine.
        * dGeomBoxPointDepth implementation was fixed for locations outside of
          the box.
        * A fault on method call from within Joint class destructor in Python
          bindings fixed (by Tyler Limkemann)
        * A threaded job data race fixed on job release (issue #70).
        * GIMPACT math macros were changed to use standard floating point math
          rather than custom "optimized" implementations.
        * libCCD configuration description strings have been added for
          use with dGetConfiguration() and dCheckConfiguration().
        * dWorldAttachQuickStepDynamicIterationStatisticsSink public function
          was added to allow dynamic step count adjustment monitoring for
          world instances.
        * Dynamic step count adjustment was implemented for dWorldQuickStep
          with dWorldSetQuickStepDynamicIterationParameters and
          dWorldGetQuickStepDynamicIterationParameters new API functions
          to control the feature.
        * x86 targets have been changed to generate SSE2 code for calculations
          by default with possibility to explicitly configure back for FPU.
        * An incorrect optimization to Jacobian Copy building code from #1938
          that resulted in corrupt data in multi-threaded execution mode was
          fixed.
        * CMake support for project file generation has been added.
        * dxHashSpace::collide() has been changed to fault host program
          if scene gets too large and causes integer overflow.
        * Introduction of cooperative algorithms API.
          L*D*LT cooperative factorization and linear equation system
          cooperative solving have been implemented.
        * Project generation options have been changed to have built-in
          multithreaded threading implementation enabled by default.
        * dWorldStep threaded implementation has been extended to the final
          steps of constraint force applications and body position updates
          after the LCP solving. Note that body callbacks (if set) may be
          called from multiple threads if threaded execution is enabled.
        * OU atomicord32 type has been fixed to be unsigned on all supported
          platforms.
        * dGeomTriMeshDataPreprocess2() public function has been added to
          replace dGeomTriMeshDataPreprocess(). Face angles pre-computation
          for triangle meshes has been implemented.
        * dGeomTriMeshDataGetBuff and dGeomTriMeshDataSetBuff have been marked
          deprecated and their functionality implemented via
          dGeomTriMeshDataGet and dGeomTriMeshDataSet. Extra function variant
          dGeomTriMeshDataGet2() has been added to allow returning data size.
        * The implementation of OPCODE TriMesh data pre-processing
          (dGeomTriMeshDataPreprocess()) has been optimized to only contain
          a sort and a single pass over edges (used to be a sort and O(N^2)).
        * dGeomTriMeshDataPreprocess() public function has been changed to
          return a boolean status (it can fail in low memory conditions).
        * The correct handling of dJOINT_REVERSE mode for AngularMotor Joint
          implemented (issue #37).
        * A bug fixed with HashSpace calling big boxes collision twice
          (both straight and reverse geometries order) since revision #1831.
        * dJointSetHinge2Axes public function has been added and
          dJointSetHinge2Axis1/2 have been marked deprecated due to being
          unsafe.
        * ICE Container class allocation strategy fixed to avoid reserving
          excess memory with large collections.
        * dSafeNormalize3 and dSafeNormalize4 functions changed to leave the
          parameter intact instead of replacing it with the X-axis unit in case
          of fault.
        * A function to create a self-threaded threading implementation object
          has been moved back to public headers as there could be a use for it
          while running several worlds in parallel threads.
        * Hinge2 joint corected to avoid faulting asserts when the axes get
          temporarily invalid during assignments (suggested by David Mansolino)
        * An invalid memory access fixed in dxSAPSpace::BoxPruning() in case
          if there were NaN values in AABBs to be sorted.
        * Unexpected joint mode assignment (instead of comparison) fixed within
          an dUASSERT in dJointSetTransmissionAxis2() of transmission joint
        * Convex-Trimesh collider added (libccd+GIMPACT only)(by Piotr Piastucki)
        * dCreateConvex() and dGeomSetConvex() public APIs changed to expect
          their parameter arrays as const pointers
        * OPCODE mesh colliders' input coordinates have been offset to
          mesh-relative frames to decrease potential computational errors
          (suggested by luckytrashsc2@g***l.com)
        * Implemented change to return highest depth contacts subset for GIMPACT
          in cases if contacts count exceeds requested maximum (as suggested in
          the issue #36 by Piotr Piastucki)
        * Added support for using libccd from the system (if found via
          pkg-config)
        * Floating point division by zero in capsule-ray collision routine
          in case if the ray axis was parallel the cylinder and the ray started
          from within it fixed (issue #26)
        * Threading support has been extended to complete implementation
          of QuickStep
        * Added dJointSetDBallDistance
        * Built-in threading implementation compilation fixed for OSX
          (clock_gettime() is missing from the system - reported by Bram)
        * Declarations of dWorld[Get/Set]AutoDisableLinearAverageThreshold and
          dWorld[Get/Set]AutoDisableAngularAverageThreshold have been removed
          from public headers (were orphaned since rev.1052)
        * Added dODE_VERSION macro to public headers (issue #24).

## Changes in version 0.14.1

**Released on March 29th, 2025.**

* Issue #263: fix release tarball by relying on `make dist`.

* Document ATF to Kyua mappings for metadata properties.

* Support `require.diskspace` ATF metadata property.

* Support backwards compatible `unprivileged_user` metadata property for ease
  of use dealing with ATF vs Kyua.

* Fix building from source by tracking `utils/process/Kyuafile.in` and
  `engine/execenv/execenv_fwd.hpp` with automake.

## Changes in version 0.14

**Released on December 31st, 2024.**

* Replace `--with-atf` with `--enable-atf`. The latter must be specified
  to enable ATF support and the Kyua tests by proxy.

* Require newer versions of ATF (0.21) and Lutok (0.5). This is being done
  as part of a multi-phase deprecation of pre-C++11 environments.

* Vendor the ATF m4 files from the freebsd/atf repo.

* Translate `is_exclusive` metadata to its ATF counterpart.

* Issue #236: fix accidental test forkbomb in specific user environments
  with `integration` tests by avoiding infinite recursion calling kyua.

* Fix the build on Ubuntu 24.04.

- execenv support added. This FreeBSD-specific feature allows tests to be
  executed in jails.

* Issue #169: Remove deprecated `readdir_r` use.

* Fix build issue on more recent versions of MacOS.

* Fix build issue on IllumOS.

* Fix issues with PID reuse in testcases.

* Escape characters captured from stderr and stdout in HTML output.

* `integration/cmd_report_test:verbose`: fix regular expression used in
  tests which would break in certain user environments.

* Add Cirrus CI support for testing Kyua on FreeBSD.

* Remove `UTILS_UNUSED_PARAM` macro.

* Fix document rendering with newer versions of doxygen.

* Issue #152: explicitly require C++11 language features when compiling Kyua.
  Remove `std::shared_ptr` compatibility header, `utils/shared_ptr.hpp`.

* Fix `igor` and `mandoc -Tlint` reported issues with generated manpages.

* Issue #167: fix typos in kyua(1) manpage.

## Changes in version 0.13

**Released on August 26th, 2016.**

* Fixed execution of test cases as an unprivileged user, at least under
  NetBSD 7.0.  Kyua-level failures were probably a regression introduced
  in Kyua 0.12, but the underlying may have existed for much longer:
  test cases might have previously failed for mysterious reasons when
  running under an unprivileged user.

* Issue #134: Fixed metadata test broken on 32-bit platforms.

* Issue #139: Added per-test case start/end timestamps to all reports.

* Issue #156: Fixed crashes due to the invalid handling of cleanup
  routine data and triggered by the reuse of PIDs in long-running Kyua
  instances.

* Issue #159: Fixed TAP parser to ignore case while matching `TODO` and
  `SKIP` directives, and to also recognize `Skipped`.

* Fixed potential crash due to a race condition in the unprogramming of
  timers to control test deadlines.


## Changes in version 0.12

**Released on November 22nd, 2015.**

This is a huge release and marks a major milestone for Kyua as it finally
implements a long-standing feature request: the ability to execute test
cases in parallel.  This is a big deal because test cases are rarely
CPU-bound: running them in parallel yields much faster execution times for
large test suites, allowing faster iteration of changes during development.

As an example: the FreeBSD test suite as of this date contains 3285 test
cases.  With sequential execution, a full test suite run takes around 12
minutes to complete, whereas on a 4-core machine with a high level of
parallelism it takes a little over 1 minute.

Implementing parallel execution required rewriting most of Kyua's core and
partly explains explains why there has not been a new release for over a
year.  The current implementation is purely subprocess-based, which works
but has some limitations and has resulted in a core that is really complex
and difficult to understand.  Future versions will investigate the use of
threads instead for a simplified programming model and additional
parallelization possibilities.

* Issue #2: Implemented support to execute test cases in parallel when
  invoking `kyua test`.  Parallel execution is *only* enabled when the new
  `parallelism` configuration variable is set to a value greater than `1`.
  The default behavior is still to run tests sequentially because some test
  suites contain test cases with side-effects that might fail when run in
  parallel.  To resolve this, the new metadata property `is_exclusive` can
  be set to `true` on a test basis to indicate that the test must be run on
  its own.

* Known regression: Running `kyua debug` on a TAP-based test program does
  not currently report the output in real time.  The output will only be
  displayed once the test program completes.  This is a shortcoming of
  the new parallel execution engine and will be resolved.

* Removed the external C-based testers code in favor of the new built-in
  implementations.  The new approach feels significantly faster than the
  previous one.

* Fixed the handling of relative paths in the `fs.*` functions available
  in `Kyuafile`s.  All paths are now resolved relative to the location of
  the caller `Kyuafile`.  `Kyuafile.top` has been updated with these
  changes and you should update custom copies of this file with the new
  version.

* Changed temporary directory creation to always grant search
  permissions on temporary directories.  This is to prevent potential
  problems when running Kyua as root and executing test cases that require
  dropping privileges (as they may later be unable to use absolute paths
  that point inside their work directory).

* The cleanup of work directories does not longer attempt to deal with
  mount points.  If a test case mounts a file system and forgets to unmount
  it, the mount point will be left behind.  It is now the responsibility of
  the test case to clean after itself.  The reasons for this change are
  simplicity and clarity: there are many more things that a test case can
  do that have side-effects on the system and Kyua cannot protect against
  them all, so it is better to just have the test undo anything it might
  have done.

* Improved `kyua report --verbose` to properly handle environment
  variables with continuation lines in them, and fixed the integration
  tests for this command to avoid false negatives.

* Changed the configuration file format to accept the definition of
  unknown variables without declaring them local.  The syntax version
  number remains at 2.  This is to allow configuration files for newer Kyua
  versions to work on older Kyua versions, as there is no reason to forbid
  this.

* Fixed stacktrace gathering with FreeBSD's ancient version of GDB.
  GDB 6.1.1 (circa 2004) does not have the `-ex` flag so we need to
  generate a temporary GDB script and feed it to GDB with `-x` instead.

* Issue #136: Fixed the XML escaping in the JUnit output so that
  non-printable characters are properly handled when they appear in the
  process's stdout or stderr.

* Issue #141: Improved reporting of errors triggered by sqlite3.  In
  particular, all error messages are now tagged with their corresponding
  database filename and, if they are API-level errors, the name of the
  sqlite3 function that caused them.

* Issue #144: Improved documentation on the support for custom properties
  in the test metadata.

* Converted the `INSTALL`, `NEWS`, and `README` distribution documents to
  Markdown for better formatting online.


## Changes in version 0.11

**Released on October 23rd, 2014.**

* Added support to print the details of all test cases (metadata and
  their output) to `report`.  This is via a new `--verbose` flag which
  replaces the previous `--show-context`.

* Added support to specify the amount of physical disk space required
  by a test case.  This is in the form of a new `required_disk_space`
  metadata property, which can also be provided by ATF test cases as
  `require.diskspace`.

* Assimilated the contents of all the `kyua-*-tester(1)` and
  `kyua-*-interface(7)` manual pages into more relevant places.  In
  particular, added more details on test program registration and their
  metadata to `kyuafile(5)`, and added `kyua-test-isolation(7)`
  describing the isolation features of the test execution.

* Assimilated the contents of all auxiliary manual pages, including
  `kyua-build-root(7)`, `kyua-results-files(7)`, `kyua-test-filters(7)`
  and `kyua-test-isolation(7)`, into the relevant command-specific
  manual pages.  This is for easier discoverability of relevant
  information when reading how specific Kyua commands work.

* Issue #30: Plumbed through support to query configuration variables
  from ATF's test case heads.  This resolves the confusing situation
  where test cases could only do this from their body and cleanup
  routines.

* Issue #49: Extended `report` to support test case filters as
  command-line arguments.  Combined with `--verbose`, this allows
  inspecting the details of a test case failure after execution.

* Issue #55: Deprecated support for specifying `test_suite` overrides on
  a test program basis.  This idiom should not be used but support for
  it remains in place.

* Issue #72: Added caching support to the `getcwd(3)` test in configure
  so that the result can be overriden for cross-compilation purposes.

* Issue #83: Changed manual page headings to include a `kyua` prefix in
  their name.  This prevents some possible confusion when displaying,
  for example, the `kyua-test` manual page with a plain name of `test`.

* Issue #84: Started passing test-suite configuration variables to plain
  and TAP test programs via the environment.  The name of the
  environment variables set this way is prefixed by `TEST_ENV_`, so a
  configuration variable of the form
  `test_suites.some_name.allow_unsafe_ops=yes` in `kyua.conf` becomes
  `TEST_ENV_allow_unsafe_ops=YES` in the environment.

* Issues #97 and #116: Fixed the build on Illumos.

* Issue #102: Set `TMPDIR` to the test case's work directory when running
  the test case.  If the test case happens to use the `mktemp(3)` family
  of functions (due to misunderstandings on how Kyua works or due to
  the reuse of legacy test code), we don't want it to easily escape the
  automanaged work directory.

* Issue #103: Started being more liberal in the parsing of TAP test
  results by treating the number in `ok` and `not ok` lines as optional.

* Issue #105: Started using tmpfs instead of md as a temporary file
  system for tests in FreeBSD so that we do not leak `md(4)` devices.

* Issue #109: Changed the privilege dropping code to start properly
  dropping group privileges when `unprivileged_user` is set.  Also fixes
  `testers/run_test:fork_wait__unprivileged_group`.

* Issue #110: Changed `help` to display version information and clarified
  the purpose of the `about` command in its documentation.

* Issue #111: Fixed crash when defining a test program in a `Kyuafile`
  that has not yet specified the test suite name.

* Issue #114: Improved the `kyuafile(5)` manual page by clarifying the
  restrictions of the `include()` directive and by adding abundant
  examples.


## Changes in version 0.10

**Experimental version released on August 14th, 2014.**

* Merged `kyua-cli` and `kyua-testers` into a single `kyua` package.

* Dropped the `kyua-atf-compat` package.

* Issue #100: Do not try to drop privileges to `unprivileged_user` when we
  are already running as an unprivileged user.  Doing so is not possible
  and thus causes spurious test failures when the current user is not
  root and the current user and `unprivileged_user` do not match.

* Issue #79: Mention `kyua.conf(5)` in the *See also* section of `kyua(1)`.

* Issue #75: Change the `rewrite__expected_signal__bad_arg` test in
  `testers/atf_result_test` to use a different signal value.  This is to
  prevent triggering a core dump that made the test fail in some platforms.


## Changes in kyua-cli version 0.9

**Experimental version released on August 8th, 2014.**

Major changes:

The internal architecture of Kyua to record the results of test suite
runs has completely changed in this release.  Kyua no longer stores all
the different test suite run results as different "actions" within the
single `store.db` database.  Instead, Kyua now generates a separate
results file inside `~/.kyua/store/` for every test suite run.

Due to the complexity involved in the migration process and the little
need for it, this is probably going to be the only release where the
`db-migrate` command is able to convert an old `store.db` file to the
new scheme.

Changes in more detail:

* Added the `report-junit` command to generate JUnit XML result files.
  The output has been verified to work within Jenkins.

* Switched to results files specific to their corresponding test suite
  run.  The unified `store.db` file is now gone: `kyua test` creates a
  new results file for every invocation under `~/.kyua/store/` and the
  `kyua report*` commands are able to locate the latest file for a
  corresponding test suite automatically.

* The `db-migrate` command takes an old `store.db` file and generates
  one results file for every previously-recorded action, later deleting
  the `store.db` file.

* The `--action` flag has been removed from all commands that accepted
  it.  This has been superseded by the tests results files.

* The `--store` flag that many commands took has been renamed to
  `--results-file` in line with the semantical changes.

* The `db-exec` command no longer creates an empty database when none
  is found.  This command is now intended to run only over existing
  files.


## Changes in kyua-testers version 0.3

**Experimental version released on August 8th, 2014.**

* Made the testers set a "sanitized" value for the `HOME` environment
  variable where, for example, consecutive and trailing slashes have
  been cleared.  Mac OS X has a tendency to append a trailing slash to
  the value of `TMPDIR`, which can cause third-party tests to fail if
  they compare `${HOME}` with `$(pwd)`.

* Issues #85, #86, #90 and #92: Made the TAP parser more complete: mark
  test cases reported as `TODO` or `SKIP` as passed; handle skip plans;
  ignore lines that look like `ok` and `not ok` but aren't results; and
  handle test programs that report a pass but exit with a non-zero code.


## Changes in kyua-cli version 0.8

**Experimental version released on December 7th, 2013.**

* Added support for Lutok 0.4.

* Issue #24: Plug the bootstrap tests back into the test suite.  Fixes
  in `kyua-testers` 0.2 to isolate test cases into their own sessions
  should allow these to run fine.

* Issue #74: Changed the `kyuafile(5)` parser to automatically discover
  existing tester interfaces.  The various `*_test_program()` functions
  will now exist (or not) based on tester availability, which simplifies
  the addition of new testers or the selective installation of them.


## Changes in kyua-testers version 0.2

**Experimental version released on December 7th, 2013.**

* Issue #74: Added the `kyua-tap-tester`, a new backend to interact with
  test programs that comply with the Test Anything Protocol.

* Issue #69: Cope with the lack of `AM_PROG_AR` in `configure.ac`, which
  first appeared in Automake 1.11.2.  Fixes a problem in Ubuntu 10.04
  LTS, which appears stuck in 1.11.1.

* Issue #24: Improve test case isolation by confining the tests to their
  own session instead of just to their own process group.


## Changes in kyua-cli version 0.7

**Experimental version released on October 18th, 2013.**

* Made failures from testers more resilent.  If a tester fails, the
  corresponding test case will be marked as broken instead of causing
  kyua to exit.

* Added the `--results-filter` option to the `report-html` command and
  set its default value to skip passed results from HTML reports.  This
  is to keep these reports more succint and to avoid generating tons of
  detail files that will be, in general, useless.

* Switched to use Lutok 0.3 to gain compatibility with Lua 5.2.

* Issue #69: Cope with the lack of `AM_PROG_AR` in `configure.ac`, which
  first appeared in Automake 1.11.2.  Fixes a problem in Ubuntu 10.04
  LTS, which appears stuck in 1.11.1.


## Changes in kyua-cli version 0.6

**Experimental version released on February 22nd, 2013.**

* Issue #36: Changed `kyua help` to not fail when the configuration file
  is bogus.  Help should always work.

* Issue #37: Simplified the `syntax()` calls in configuration and
  `Kyuafile` files to only specify the requested version instead of also
  the format name.  The format name is implied by the file being loaded, so
  there is no use in the caller having to specify it.  The version number
  of these file formats has been bumped to 2.

* Issue #39: Added per-test-case metadata values to the HTML reports.

* Issue #40: Rewrote the documentation as manual pages and removed the
  previous GNU Info document.

* Issue #47: Started using the independent testers in the `kyua-testers`
  package to run the test cases.  Kyua does not implement the logic to
  invoke test cases any more, which provides for better modularity,
  extensibility and robustness.

* Issue #57: Added support to specify arbitrary metadata properties for
  test programs right from the `Kyuafile`.  This is to make plain test
  programs more versatile, by allowing them to specify any of the
  requirements (allowed architectures, required files, etc.) supported
  by Kyua.

* Reduced automatic screen line wrapping of messages to the `help`
  command and the output of tables by `db-exec`.  Wrapping any other
  messages (specially anything going to stderr) was very annoying
  because it prevented natural copy/pasting of text.

* Increased the granularity of the error codes returned by `kyua(1)` to
  denote different error conditions.  This avoids the overload of `1` to
  indicate both "expected" errors from specific subcommands and
  unexpected errors caused by the internals of the code.  The manual now
  correctly explain how the exit codes behave on a command basis.

* Optimized the database schema to make report generation almost
  instantaneous.

* Bumped the database schema to 2.  The database now records the
  metadata of both test programs and test cases generically, without
  knowledge of their interface.

* Added the `db-migrate` command to provide a mechanism to upgrade a
  database with an old schema to the current schema.

* Removed the GDB build-time configuration variable.  This is now part
  of the `kyua-testers` package.

* Issue #31: Rewrote the `Kyuafile` parsing code in C++, which results in
  a much simpler implementation.  As a side-effect, this gets rid of the
  external Lua files required by `kyua`, which in turn make the tool
  self-contained.

* Added caching of various configure test results (particularly in those
  tests that need to execute a test program) so that cross-compilers can
  predefine the results of the tests without having to run the
  executables.


## Changes in kyua-testers version 0.1

**Experimental version released on February 19th, 2013.**

This is the first public release of the `kyua-testers` package.

The goal of this first release is to adopt all the test case execution
code of `kyua-cli` 0.5 and ship it as a collection of independent tester
binaries.  The `kyua-cli` package will rely on these binaries to run the
tests, which provides better modularity and simplicity to the
architecture of Kyua.

The code in this package is all C as opposed to the current C++ codebase
of `kyua-cli`, which means that the overall build times of Kyua are now
reduced.


## Changes in kyua-cli version 0.5

**Experimental version released on July 10th, 2012.**

* Issue #15: Added automatic stacktrace gathering of crashing test cases.
  This relies on GDB and is a best-effort operation.

* Issue #32: Added the `--build-root` option to the debug, list and test
  commands.  This allows executing test programs from a different
  directory than where the `Kyuafile` scripts live.  See the *Build roots*
  section in the manual for more details.

* Issue #33: Removed the `kyuaify.sh` script.  This has been renamed to
  atf2kyua and moved to the `kyua-atf-compat` module, where it ships as a
  first-class utility (with a manual page and tests).

* Issue #34: Changed the HTML reports to include the stdout and stderr of
  every test case.

* Fixed the build when using a "build directory" and a clean source tree
  from the repository.


## Changes in kyua-cli version 0.4

**Experimental version released on June 6th, 2012.**

* Added the `report-html` command to generate HTML reports of the
  execution of any recorded action.

* Changed the `--output` flag of the `report` command to only take a
  path to the target file, not its format.  Different formats are better
  supported by implementing different subcommands, as the options they
  may receive will vary from format to format.

* Added a `--with-atf` flag to the configure script to control whether
  the ATF tests get built or not.  May be useful for packaging systems
  that do not have ATF in them yet.  Disabling ATF also cuts down the
  build time of Kyua significantly, but with the obvious drawbacks.

* Grouped `kyua` subcommands by topic both in the output of `help` and
  in the documentation.  In general, the user needs to be aware of
  commands that rely on a current project and those commands that rely
  purely on the database to generate reports.

* Made `help` print the descriptions of options and commands properly
  tabulated.

* Changed most informational messages to automatically wrap on screen
  boundaries.

* Rewrote the configuration file parsing module for extensibility.  This
  will allow future versions of Kyua to provide additional user-facing
  options in the configuration file.

  No syntax changes have been made, so existing configuration files
  (version 1) will continue to be parsed without problems.  There is one
  little exception though: all variables under the top-level
  `test_suites` tree must be declared as strings.

  Similarly, the `-v` and `--variable` flags to the command line must
  now carry a `test_suites.` prefix when referencing any variables under
  such tree.


## Changes in kyua-cli version 0.3

**Experimental version released on February 24th, 2012.**

* Made the `test` command record the results of the executed test
  cases into a SQLite database.  As a side effect, `test` now supports a
  `--store` option to indicate where the database lives.

* Added the `report` command to generate plain-text reports of the
  test results stored in the database.  The interface of this command is
  certainly subject to change at this point.

* Added the `db-exec` command to directly interact with the store
  database.

* Issue #28: Added support for the `require.memory` test case property
  introduced in ATF 0.15.

* Renamed the user-specific configuration file from `~/.kyuarc` to
  `~/.kyua/kyua.conf` for consistency with other files stored in the
  `~/.kyua/` subdirectory.

* Switched to use Lutok instead of our own wrappers over the Lua C
  library.  Lutok is just what used to be our own utils::lua module, but
  is now distributed separately.

* Removed the `Atffile`s from the source tree.  Kyua is stable enough
  to generate trustworthy reports, and we do not want to give the
  impression that atf-run / atf-report are still supported.

* Enabled logging to stderr for our own test programs.  This makes it
  slightly easier to debug problems in our own code when we get a
  failing test.


## Changes in kyua-cli version 0.2

**Experimental version released on August 24th, 2011.**

The biggest change in this release is the ability for Kyua to run test
programs implemented using different frameworks.  What this means is
that, now, a Kyua test suite can include not only ATF-based test
programs, but also "legacy" (aka plain) test programs that do not use
any framework.  I.e. if you have tests that are simple programs that
exit with 0 on success and 1 on failure, you can plug them in into a
Kyua test suite.

Other than this, there have been several user-visible changes.  The most
important are the addition of the new `config` and `debug` subcommands
to the `kyua` binary.  The former can be used to inspect the runtime
configuration of Kyua after parsing, and the latter is useful to
interact with failing tests cases in order to get more data about the
failure itself.

Without further ado, here comes the itemized list of changes:

* Generalized the run-time engine to support executing test programs
  that implement different interfaces.  Test programs that use the ATF
  libraries are just a special case of this.  (Issue #18.)

* Added support to the engine to run `plain` test programs: i.e. test
  programs that do not use any framework and report their pass/fail
  status as an exit code.  This is to simplify the integration of legacy
  test programs into a test suite, and also to demonstrate that the
  run-time engine is generic enough to support different test
  interfaces.  (Issue #18.)

* Added the `debug` subcommand.  This command allows end users to tweak
  the execution of a specific test case and to poke into the behavior of
  its execution.  At the moment, all this command allows is to view the
  stdout and stderr of the command in real time (which the `test`
  command currently completely hides).

* Added the `config` subcommand.  This command allows the end user to
  inspect the current configuration variables after evaluation, without
  having to read through configuration files.  (Issue #11.)

* Removed the `test_suites_var` function from configuration files.  This
  was used to set the value of test-suite-sepecific variables, but it
  was ugly-looking.  It is now possible to use the more natural syntax
  `test_suites.<test-suite-name>.<variable> = <value>`.  (Issue #11.)

* Added a mechanism to disable the loading of configuration files
  altogether.  Needed for testing purposes and for scriptability.
  Available by passing the `--config=none` flag.

* Enabled detection of unused parameters and variables in the code and
  fixed all warnings.  (Issue #23.)

* Changed the behavior of "developer mode".  Compiler warnings are now
  enabled unconditionally regardless of whether we are in developer mode
  or not; developer mode is now only used to perform strict warning
  checks and to enable assertions.  Additionally, developer mode is now
  only automatically enabled when building from the repository, not for
  formal releases.  (Issue #22.)

* Fixed many build and portability problems to Debian sid with GCC 4.6.3
  and Ubuntu 10.04.1 LTS.  (Issues #20, #21, #26.)


## Changes in kyua-cli version 0.1

**Experimental version released on June 23rd, 2011.**

This is the first public release of the `kyua-cli` package.

The scope of this release is to provide functional replacement for the
`atf-run` utility included in the atf package.  At this point, `kyua`
can reliably run the NetBSD 5.99.53 test suite delivering the same
results as `atf-run`.

The reporting facilities of this release are quite limited.  There is
no replacement for `atf-report` yet, and there is no easy way of
debugging failing test programs other than running them by hand.  These
features will mark future milestones and therefore be part of other
releases.

Be aware that this release has suffered very limited field testing.
The test suite for `kyua-cli` is quite comprehensive, but some bugs may
be left in any place.

1.5.2 (2025-04-08)

* Fixed GH-37: gnupg_decrypt() returns false when decrypting an encrypted
  empty string
* Fixed GH-46: gnupg_decrypt() segfaults when password callback user ID hint
  is not supplied
* Fixed 1.5.0 regressition - the deletekey allow_secret made optional again

* Use cmake to build.

Changelog:
2022-10-03, LibOFX 0.10.9:

- Fix library name on Windows (#88)
- Fix several more memory issues (#90)

2022-09-27, LibOFX 0.10.8:

        - Fix null pointer dereference bugs (#87)
        - Initial support for exporting Config.cmake with targets (#81)
        - Fix version and tools description in vcpkg.json
        - Add cpack rules for "make source_package"
        - Fix installation path of libofx.h (#83)
        - Rename some variables that shadowed others to clarify different meanings #75 (#80)

2022-09-08, LibOFX 0.10.7:

        - autotools: fix LIBOFX_MAJOR_VERSION and friends in libofx.h (#76)
        - CMake: miscellaneous fixes (#73)

2022-09-04, LibOFX 0.10.6:

        - Update FindOpenSP; also allow to forcefully ENABLE SP_MULTI_BYTE (#71)
        - Add support for CMake build system (#63)
        - Minor code cleanup in CharStringtostring function and its header (#65)
        - Ignore SGML parser character error because the char is accepted fine (#60) (#64)
        - Fix find_dtd() when OFX_DTD_PATH env var is used (#66)
        - Add ./configure option to disable CLI tools
        - Only link ofx2qif against C++ STD lib
        - Win32 code fixes for MSVC compilation
        - Don't deconst iconv input buffer under Windows (#51)

2022-04-19, LibOFX 0.10.5:
        - Fix missing include for ptrdiff_t on Homebrew (#57)

2022-04-18, LibOFX 0.10.4:

        - #56: Fix parallel builds by fixing the man-page build
        - #54: Remove all "using namespace std" directives
        - #53: Fix some minor memory leaks
        - Revert #44 (fix "typos" in source code) because it was wrong

2021-09-29, LibOFX 0.10.3:

        - #45: fix gmt offset seconds
        - #44: fix various typos in source code
        - fix win32 build failure

2021-04-23, LibOFX 0.10.2:

        - #41: Improved imported date stability, see gnucash bug
        797848 and gnucash bug 636340.
        - #40: Respect --libdir for opensp. Don't override docdir.

2021-01-25, LibOFX 0.10.1:

        - Issue #37 fixed: Correct casting of iconv input argument
        - Issue #30 fixed: Let ofxdump also return an error value on error
        - Code cleanup towards normal C++

2021-01-03, LibOFX 0.10.0:

	- Issue #34 fixed: Remove unimplemented function from libofx.h header
	- Issue #30 fixed: Return error value if file parsing is unsuccessful in libofx_proc_file
	- Issue #29 fixed: Use given parameter for actual file type in libofx_proc_file

	- Large contribution adding investment / security handling in OFX files, by jeffjl74.
	- ABI-breaking change, hence MINOR version incremented (due to MAJOR still at zero),
	  but libofx.h API should only have additions
	- Details:
        - jeffjl74 Enhanced handling of investments in OFX files (support not added to OFC)
        - increased OFX_SECNAME_LENGTH to match the OFX spec (ABI-breaking change, hence MINOR version incremented)
        - OfxSecurityData now includes:
            - an enum for the type of the security (stock, bond, fund, option)
            - the optional <SECINFO> fields
            - the mandatory <DEBTINFO> and <OPTINFO> fields
            - the optional <DEBTINFO> and <OPTINFO> fields
        - added <INVBAL> parsing for cash balances in investment accounts
            - usefulness depends upon how the broker uses these fields
                - Vanguard fund account puts the market value in there instead of the cash balance
                - other tested brokers use it appropriately, though the date of the balance is sometimes inconsistent
                  usually due to unsettled trades, i.e. the "as of" date will say "today" but the cash
                  balance will actually be from a couple of days ago with the difference being unsettled trades.
        - <STMTTRN> fields under an <INVBANKTRAN> are now parsed into an OfxInvestmentTransactionContainer
            - This changes previous behaviour. LibOFX formerly provided an OfxBankTransactionContainer.
              Now it sets data.invtransactiontype_valid true with data.invtransactiontype = OFX_INVBANKTRAN.
              The end result is that the transaction callback now looks like an investment transaction
              (which it is) rather than a banking transaction (which it is not).
        - added the fields from section 13.9.2.4.2 of OFX spec 2.1.1 to OfxTransactionData
            - provides better support for bonds, options, and 401(k)
        - added <INVPOS> support to provide balances for securities
            - responds to sourceforge feature request #7
            - adds new callback for investment positions
                - adds new OfxPositionData struct
                - adds new ofx_set_position_cb function
        - added <CURRENCY>, <ORIGCURRENCY>, <CURRATE> and <CURSYM> parsing and fields to transactions, securities, and positions
        - added a new account type OfxAccountData::OFX_401K
            - if set, will add <INC401K>Y</INC401K> and <INC401KBAL>Y</INC401KBAL> in the investment statement request
                - this is currently untested
            - added parsing of transactions for 401k in the response (tested only via ofxdump on spec examples)
        - added a fix for sourceforge bug #46 account callback on <TRANSFER>
            - <TRANSFER> no longer results in redundant/irrelevant account and statement callbacks
        - modified ofxdump to support the above changes
        - added investment account examples from OFX 2.1.1 spec to "ofx_sample_files"
            - fixed some time offsets in the OFX spec examples
                - section 13.13: EST is GMT -5
                - section 16.5.3.2: August is not PST or GMT -8. Changed to -7 PDT
                - section 16.5.4.2: August is not PST or GMT -8. Changed to -7 PDT
            - updated existing samples to fix the time formats (added seconds to the time format)
        - could not get openSP to parse ofx201.dtd
            - for elements that actually still provide their data,
              ofxdump generates lots of parse errors on an OFX 2.x file.
              Data handling for these elements in ofx_sgml.cpp is a little unorthodox.

Upstream changes:
0.9735 2025-03-27
- better connectedness docs (#36 #37) - thanks @gwselke
0.9734 2025-03-01
- add connected_subgraphs (#35) - thanks @merkys
0.9733 2025-01-12
- added max_cliques (#33,#34) - thanks @choroba
- restore 0.9716 behaviour of random_graph (#32) - thanks @kester-habermann for report

* What's Changed:
INCR transfer bug fixes by @ebiggers in #16
Use XDG_CACHE_HOME for xsel.log by @valeth in #15
Using markdown syntax by @gildasio in #9
Plug memory leak in handle_targets in #18
Fix segfault when stdin is empty by @mptre in #17
Fix #19 segfault when --append to empty selection by @MaskRay in #20
Do not modify HOME environment variable. by @e7appew in #21
Perform fstat on stdin and stdout only if required. by @e7appew in #22
Debian patches by @hyperair in #25
Avoid passing NULL to vsnprintf() by @mptre in #27
Avoid extra char copy in strncpy by @ony in #32
Set timer value to 0 to stop timer, don't use a nullptr timer by @mckellyln in #31
Remove interfering error message by @emendelson in #37
Option: trim trailing newline from output by @aaaaaaaalex in #39
In README file: updated link to ICCCM rant to one that works. by @andrep in #40
Fix MULTIPLE conversion requests by @CyberShadow in #45
Added option to add window name by @esturafd in #41
Set WM_NAME and WM_CLASS window properties by @uosis in #35
Modernize by @SoapGentoo in #50

* Remove developer-merged patch from pkgsrc

1.2.2 (2025-07-26)

What's Changed

Bug Fixes

* Fix issue where reviews cannot be displayed for files with non-ASCII
  characters in filename by @TohruOkamoto in #37

New Contributors

* @TohruOkamoto made their first contribution in #37