Update to 0.62
Upstream changes:
0.62 - 2025-01-13, H.Merijn Brand
* doc should not be part of test
0.61 - 2025-01-13, H.Merijn Brand
* Replace "use vars" with "our" (James Raspass: PR #9)
* Specify recommended versions based on known CVE's
* Update doc for groff-1.24
* It's 2024
* Tested with perl-5.40.0
* It's 2025
* Add SECURITY.md
tex-pst-barcode{,-doc}: update to 0.20
- updated documentation
- Common text rendering code was factored out of the linear and matrix renderers
into its own resource.
- The ITF-14 encoder's text positioning was fixed.
- The Code 128 encoder's raw mode was fixed.
- The linear and matrix renderers were enhanced to accept top and bottom for the
textyalign option.
- The linear and matrix renderers were enhanced with a textdirection option.
- The linear and matrix renderer were enhanced with support for extratextsubspace,
extratextsplit and extratextlinegaps options corresponding to the alttext
equivalents.
- The linear and matrix renderers were enhanced with alttextsubspace that allows
given characters to be substituted for spaces.
- The linear and matrix renderers were enhanced with alttextsplit and
alttextlinegaps options that may be used to render multi-line blocks of text.
- The GS1 AI linter was realigned with the latest release of the GS1 Syntax
Dictionary.
[14 lines not shown]
tex-incgraph{,-doc}: update to 1.4.0
### Added
- `incgraph.doc.bib` for references (moved from documentation source)
- `\incmultipages`: specialized macro to include multiple pages from
a PDF file
### Changed
- .tds.zip removed from CTAN upload to comply to CTAN rules
- TDS structure flattend on GitHub repository
- `README.md` adapted to these changes
- `CHANGES.md` renamed to `CHANGELOG.md` following
https://keepachangelog.com/en/1.1.0/
- `incgraph-doc.sty` renamed to `incgraph.doc.sty`
- References updated
- Required LaTeX version bumped to 2025-06-01
- Implemenation of `\igrGetLastPage` changed.
It wraps an L3 layer function now.
- `\igrLastPage` is locally assigned now.
[6 lines not shown]
tex-circuitikz{,-doc}: update to 1.8.5
1.8.4
- Add a new set of filter blocks, add options for inner block drawings
- Add the option to *not* draw the wiper in rotary switches
- Add an option to change the aspect of `msrstub`
- Add the singeneric (sine generic bipole) component
- Fix a problem with dc symbol dashes
- Fix the position of the left/right up/down anchors for node-type blocks
- Minor fixes in the manual
- Make the value of `bipoles/length` usable by `\ctikzvalof`
- Add a key to customise the number of lines of the `gridnode` inner drawing
1.8.5
- Add "automatic advanced voltages/currents/flows" (by Romano),
marked as experimental for now.
- Add an `ideal filter` option for plot-type filters,
to draw ideal (square) filter shapes.
vfs_attach: reject file system with non-unique fstype
while currently our fstype values are still unique, given the poor
hash function used by makefstype [1], it isn't too unlikely for a future
or out-of-tree file system to have a conflicting value. it's safer
to reject it explicitly. note that, we can't lightly change the hash
function because it's exposed as a part of nfs file handles.
[1] for example, makefstype("qa") == makefstype("uq") == 0x1a5.
the current list of fstype values used by the in-tree file systems:
0000064b zfs
000006a6 udf
0000070b nfs
0000072b lfs
0000073b mfs
0000076b hfs
0000078b ffs
[28 lines not shown]
tex-chemfig{,-doc}: update to 1.71
1.7
1. To draw a horizontal reaction a new environment is provided: \hreac...\endhreac
2. The strut of the previous atom is no longer added to the argument of \printatom
The key 'use atom strut', when set to true, reverts to the previous behavior
3. When 'use atom strut' is 'false', each atom is typeset in a TeX box only once,
whereas previously it was sometimes 5 times or more
1.71
* bugfix: too many incorrect bond connections with the new definition of
\CF_ifzerodim. Back to the previous definition (macro \CF_ifzerodim used
only if the key "use atom strut" is true).
* bugfix: optional argument \chemfig or \chemname taken into account in hreac
environment.
* bugfix:in hreac environment, the argument of \^{<dim>} or \>{<dim> }is no
longer evaluated at 0pt if in ex or em.
* the macro \name{<name>} has on optionnal argument [<dim>]
* warning if non empty optional arguments of \schemestart are used
* the key "name sep" is now set to 1.5ex by default and is the value used
if the optional argument of \chemname is empty.
tex-latexdiff{,-doc}: update to 1.4.0
add directive pairs %BEGIN DIF(ADD|DEL), %END DIF(ADD|DEL)
that causes blocks to be marked up as a whole
add directive pair %BEGIN DIFNOMARKUP, %END DIFNOMARKUP that
can suppress markup locally
add option for letter-level markup for single substituted words,
controlled by configuration variable MAXCHANGESLETTER, which limits
this behaviour to a small number of changes.
By default this is set to 1 - other sensible settings are 0 and 2.
lint: in case of lossy floating point conversions, print exact value
When running lint on sparc64 with target sparc64, some tests print
warnings in cases where they shouldn't. To track down their cause,
print the exact floating point value in the message, in hexadecimal.
As the snprintf(3) manual page says, there are multiple equivalent
representations, so just match them using the placeholder "....." in the
"expect" comments. In this particular case, the message is missing
completely, so the output of the failed test will reveal the actual
value.
The affected test cases are:
* msg_380.c:38, converting -9223372036854775809.0 to 'long long'
* msg_380.c:39, converting -9223372036854775808.0 to 'long long'
* msg_381.c:38, converting -9223372036854775809.0 to 'long long'
* msg_381.c:39, converting -9223372036854775808.0 to 'long long'
Add a new land_mine test case
This new test case is intended to attempt to find buried
shell expansion code bugs, that don't often affect normal
scripts, (including most of the normal ATF tests) but can
cause problems with very odd ones.
It would have detected the bug introduced last Monday which
blew up the gettext libtool usage (because of clearly unintentional
libtool script code), which was fixed on Thursday.
It also would have detected a similar one, which was never
detected in the wild, which was installed in 2019, and also
fixed on Thursday.
Whether it can detect other similar problems in other cases is
unknown - probably not, until they are understood... More sub-tests
here for more bizarre cases might help, or might not.
[6 lines not shown]
