The package has not been updated since 2018 and has been running into
removals on python311.
Fortunately getfullargspec is a drop-in replacement for getargspec, so a
simple substitution restore life support for now.
This patch will fail to apply when a new version comes out, and thus
will force us to remove it, where the `sed` command in `postPatch` may
become abandoned, and not fail the build due to it not doing anything.
This fixes the build for keyutils on Python 3.11 and higher.
It appears this package is affected by changes that were made to CPython
that were causing code generated by certain earlier versions of Cython
to fail.
This update simply re-generates the relevant code with the up-to-date
Cython 0.29.x series during the pre-build phase, allowing the build to
succeed.
Fixes#263482.
Fixes#263506.
Co-authored-by: Robert Schütz <github@dotlambda.de>
Co-authored-by: Martin Weinelt <mweinelt@users.noreply.github.com>
Release announcement:
https://github.com/psb1558/Junicode-font/releases/tag/v2.200
From it:
Junicode 2.200 features miscellaneous fixes and additions, and it also
inaugurates a long-term program of adding glyphs for the benefit of
the Ansund HTR (Handwritten Text Recognition) project, which is
developing tools for the automated reading of medieval manuscripts. Of
the additions made so far, the ones likely to be of greatest interest
to users are two series of medieval capitals, available via features
ss11[1] and ss11[2]. The first series consists of rustic capitals,
often used for text in late ancient and early medieval times and for
rubrics (headings) in the central Middle Ages. The second consists of
Lombardic capitals, used in the central and later Middle Ages for what
are now called drop caps. These capitals are designed to harmonize
with Junicode to the greatest degree possible while remaining faithful
to the medieval sources.
Release announcement:
https://github.com/psb1558/Junicode-font/releases/tag/v2.100
From it:
Version 2.100 features a thorough reworking of the font's number
system. The default numbers are now oldstyle (or "lowercase")
proportional, and the metrics, kerning, and often the outlines of the
number glyphs have been refined, along with those of glyphs typically
associated with numbers (e.g. currency symbols). An alternate, more
modern style of some oldstyle numbers has been supplied and made
available via Stylistic Set 9 (ss09).
Release announcement:
https://github.com/psb1558/Junicode-font/releases/tag/v2.004
From it:
This release includes (mainly in the italic face) revisions of metrics
and kerning of numbers and of kerning around parentheses and
brackets. It also fixes some spacing problems (in the roman face) with
capitals in parentheses (U+1F110-U+1F129) and a few problems with
disordered or wrong components.
Release announcement:
https://github.com/psb1558/Junicode-font/releases/tag/v2.003
From it:
This is mostly a bug-fix version. It (1) fixes several non-functioning
tag sequences; (2) fixes an incompatibility with InDesign that caused
OpenType features to misbehave in that program; (3) improved several
outlines and adjusted badly positioned anchors.
Release announcement:
https://github.com/psb1558/Junicode-font/releases/tag/v2.002
From it:
Version 2.002 adds U+0243 B with stroke (with small cap and petite cap
variants) and variants of U+014A Eng (with small cap and petite cap
variants). It also adds many anchors and refines and corrects many
outlines (especially in roman).
Release announcement:
https://github.com/psb1558/Junicode-font/releases/tag/v2.001
This is a breaking change, at least in font file naming (Junicode.ttf
is now Junicode-Regular.ttf). In general, 2.0 adds a lot more font
variants and opentype and web font versions of the font.
Seeing as backward compatibility is broken anyway, I opted to break it
a bit more and change custom install path (`junicode-ttf`) to
seemingly more conventional `truetype`; new .otf and .woff2 variants
are then naturally placed in corresponding directories. This
does *not* affect the `fonts.packages` NixOS option, which rearranges
font files anyway, but brings a degree of consistency with other
fonts.
Both the file renaming and the directory structure change break
satysfi, however, so I adjusted its builder accordingly, copying over
only those font variants that were also present in 1.0 series.
