py-music21: update to 9.5.0
Music21 v9.5 is a small bug-fix release that fixes a few hard to find bugs, takes advantage of updated dependencies, and adds a bit more typing in various places.
Fixes Introducing Tiny Incompatibilities
These incompatibilities have been removed from music21 in order to get correct typing. They were never documented nor promised to work, hence considering it okay with Semantic versioning.
interval.getWrittenLowerNote works on notes and pitches but both objects must be a Note or must be a Pitch. (This restriction guarantees that the type of object being returned as the lower one will not vary based on attributes, and lets these functions be properly typed). By @mscuthbert in #1749 (started in 1747 by mistake) -- same is true for the parallel methods getWrittenHigherNote, getAbsoluteHigherNote, and getAbsoluteLowerNote. Now your IDE/mypy etc. should know the type of object being returned by these poorly-named functions!
Removed the "ability" to do this: p = pitch.Pitch(pitch.Pitch('D')) to get a D. Never was documented before: Pitches now cannot take other pitch objects as arguments; this ability was just used in the pre-typed past where we were mixing strings and Pitch objects interchangeably and was only used in music21 in one place (reduceChords.py). The newly created Pitch objects lost a lot of information about harmonics, accidental display, etc. so this was a good catch. Contributed by first-time contributor @float3 in #1746
What's Changed
Fixed links to generated documentation by @jacobtylerwalls in #1741
Take advantage of Astroid 1015 bug being fixed by @mscuthbert in #1745 -- many overloaded functions in music21 were very verbose with code that did not actually run in order to pass mypy with Astroid bug no. 1015 (a tough bug!). Major contributions to fixing the bug were given by @jacobtylerwalls. Also better docs about why music21 has its own StrEnum package. Also 'highestTime' will forever be equivalent to OffsetSpecial.AT_END -- if you know about this, it's great. Most will not care.
Added some typing to graph modules by @mscuthbert in PR1745 above.
Updated typing on tablature and intervals by @mscuthbert in #1747
Code of Conduct Clarify by @mscuthbert in #1748
Update interval Typing overloads by @mscuthbert in #1749
Fix a case where octave transposing instruments like piccolo or double bass imported from MusicXML could have incorrect octave information and bad enharmonic transposition (C#s becoming Dbs) fixed by @gregchapman-dev in #1752 (this is unrelated to a question recently here and in StackOverflow about the difference between transposing by P8 and by 12 semitones (thanks to @vanderstel for answering).)
Bug fix: corpora (including the built in core corpus) which were indexed using Python 3.13 could not be read on other systems (like Mac to Linux); a pathlib.Path was being stored in the corpus accidentally. Fixed by @mscuthbert in #1754
(www/cgicc) Updated 3.2.19 to 3.2.20
(upstream)
- Date of release is Oct 22 2023
- No update on ChangeLog, NEWS (as of 3.2.17)
- autoconf used 2.69 to 2.71
- 65 files updated
(/tmp/x)% diff -urN cgicc-3.2.* | grep '^\++' |wc
65 325 4764
- too many changes on removing back tick char: `foo' -> 'foo'
- doxygen.conf has only version number diff
stumpwm: add version 24.11
StumpWM is a window manager written entirely in Common Lisp. It
attempts to be highly customizable while relying entirely on the
keyboard for input. You will not find buttons, icons, title bars,
tool bars, or any of the other conventional GUI widgets. StumpWM
attempts to be customizable yet visually minimal. There are no
window decorations, no icons, and no buttons. It does have various
hooks to attach your personal customizations, and variables to
tweak.
bochs: Enable e1000 ethernet support.
This is basically required for networking on any halfway
modern OS.
verified to build on netbsd and linux via drecklypkg
msmtp: update to 1.8.28. Changes:
- Build with libgsasl by default again (if found).
- Detect SMTPUTF8 server capability and use it if available.
- Add IDN support to --configure (build with libidn2 to enable this).
- Add special value 'none' to logfile_time_format to suppress time output.
- Add a testing infrastructure ('make check')
- Many improvements in the msmtpq script
- Many improvements to the vim scripts
- Add support for SCRAM-SHA-256-PLUS and SCRAM-SHA-1-PLUS authentication, and
prefer SCRAM methods over the PLAIN method because of their superior
properties.
- With --read-envelope-from, a Resent-From header is now used if it is present
and appears before any From header
- Added a new configuration command 'from_full_name' to set a full name for the
From header (like -F on the command line)
- Fixed the allow_from_override command
Packaging adjusted to more closely resemble mpop. Build-tested on NetBSD
and macOS.
mpop: update to 1.4.21. Changes:
- Build with libgsasl by default again (if found).
- Add IDN support to --configure (build with libidn2 to enable this).
- Add support for SCRAM-SHA-256-PLUS and SCRAM-SHA-1-PLUS
authentication, and prefer SCRAM methods over the PLAIN method because
of their superior properties.
Packaging adjusted to more closely resemble msmtp. Build-tested on
NetBSD and macOS.
postgresql: updated to 17.4, 16.8, 15.12, 14.17, 13.20
PostgreSQL 17.4, 16.8, 15.12, 14.17, and 13.20
The issues listed below affect PostgreSQL 17. Some of these issues may also
affect other supported versions of PostgreSQL.
Improve behavior of quoting functions in libpq. The fix for CVE-2025-1094
caused the quoting functions to not honor their string length parameters and,
in some cases, cause crashes. This problem could be noticeable from a
PostgreSQL client library, based on how it is integrated with libpq.
Fix small memory leak in pg_createsubscriber.
gsasl: update to 2.2.1. Changes:
* Noteworthy changes in release 2.2.1 (2024-01-02) [stable]
** Base64 encoding/decoding now rejects non-conforming data.
** SCRAM server: Add support for GSASL_SCRAM_SALTED_PASSWORD.
If the server knows GSASL_SCRAM_SALTED_PASSWORD with matching
GSASL_SCRAM_ITER and GSASL_SCRAM_SALT values, it can avoid having to
compute the expensive PBKDF2 operation. The SCRAM client already
supports this mode. It is recommended for servers to store
GSASL_SCRAM_SERVERKEY and GSASL_SCRAM_STOREDKEY values in a database,
but sometimes storing GSASL_SCRAM_SALTED_PASSWORD, GSASL_SCRAM_ITER
and GSASL_SCRAM_SALT has other advantages.
** gsasl: Added --scram-salted-password=STRING for test purposes.
Based on idea from Manvendra Bhangui <mbhangui at gmail.com> in
<https://lists.gnu.org/archive/html/help-gsasl/2022-11/msg00000.html>.
[89 lines not shown]
nodejs: updated to 23.8.0
Version 23.8.0 (Current)
Notable Changes
Support for using system CA certificates store on macOS and Windows
Introduction of the URL Pattern API
Support for the zstd compression algorithm
Node.js thread names
Timezone data has been updated to 2025a
sqlite: allow returning ArrayBufferViews from user-defined functions