geography/py-gnssutils: Update to 1.2.6
Upstream NEWS:
### RELEASE 1.2.6
1. Add `msgfilter` argument to GNSSReader - will only parse GNSS messages where msgid is in msgfilter. msgid is string type for NMEA, otherwise integer.
1. Enhance `parsing` argument to GNSSReader - permissible values:
- `PARSE_NONE` (0) - No message parsing, raw output only
- `PARSE_FULL` (1) - Full parsing of all message attributes (the default)
- `PARSE_META` (2) - Parse only basic metadata from messages (protocol, identity and length). Outputs a new generic `GNSSMessage` object. Approximately 100x faster than full parsing, but individual data attributes will no longer be available.
DEPRECATION NOTICE:
1. Since u-blox discontinued their Thingstream PointPerfect L-Band and MQTT encrypted SPARTN services in October 2025, the [SPARTN Configuration Panel](https://github.com/semuconsulting/PyGPSClient/blob/master/SPARTN.md) panel and 'gnssmqttclient' module are redundant. These facilities and their associated package dependencies (including 'paho-mqtt') will be removed in the next version of pygnssutils (provisionally 1.2.7). The NTRIP Client facility will continue to support unencrypted SPARTN NTRIP streams.
security/vaultwarden -- Update to v1.37.0
XXX Pull-up candidate
From upstream's changelog:
Note
This update is required for support with clients with version
2026.7.0+, please update before reporting any issues with them.
Security Fixes
This release contains security fixes for the following advisories. We
strongly advice to update as soon as possible.
SSRF via the icon endpoint [GHSA-hw4g-2v3f-74x5]
[GHSA-vh5m-fc9v-m84g] (Medium, 5.8 / 6.3)
Cross-Organization Cipher Access [GHSA-xwf8-pjh7-h589] (Medium, 5.9)
[47 lines not shown]
resterm: Update to 0.48.1
This release improves diagnostics, settings validation, workflow execution and WebSocket reliability.
Fixed
* on-failure=continue now applies to failed @if and @switch branches. Cancellation still stops the workflow immediately.
* continued workflow failures still correctly mark the overall run as unsuccessful.
* fixed cancellation, handover, and background watcher cleanup for interactive WebSocket sessions.
* workflow blocks placed after mocks are preserved when documents are rendered.
* directive highlighting now correctly handles quoted, escaped, structured, comparison, and Unicode values.
wvkbd: update to 0.20
This release implements automatic focus-based visibility toggling,
thanks to Christian Duerr. Start wvkbd with the --auto parameter to
opt-in for this feature (it is not the default yet). It also implements
the ability to define different text colours for pressed and swiped keys
(thanks to Pachulke and to Christoph Butz for fixes).
There are also new flags that are using for users of wvkbd in privacy
sensitive use cases (e.g. for as a lock screens): --no-popup, --no-highlight,
--supress-feedback.
[Christoph Butz]
Added flags to suppress key-press feedback
Fixed issue on deskintl layout with text_press and text_swipe scheme colors
[Christian Duerr]
Fix CLI option alignment
[10 lines not shown]
It has been observed in the wild that some individual instances of
ISP10[24]0 controllers don't seem to like getting a 64-bit DMA address
from our driver (at least, there seems to be some sort of incorrect
handling vis a vis the RQSTYPE_A64 message in isp_intr()).
Upon inspection, it was noted that in isp_pci_dmasetup(), the decision
to use RQSTYPE_T3RQS vs RQSTYPE_T2RQS was conditional on sizeof(bus_addr_t)
being larger than sizeof(uint32_t).
However, this isn't the correct predicate; instead, the choice should
be dependent on what the largest value that bus_addr_t will have. As
it happans, the PCI layer makes a distinction between 32-bit and 64-bit
DMA windows, and isp_pci's use of the regular "pa->pa_dmat" would ensure
that the DMA address always fits within 32-bits. Therefore, there was
never a reason to use RQSTYPE_T3RQS, regardless of the size of bus_addr_t.
As such, we tweak the code to depend explicitly on a new isp_use_dma64
flag, which is initialized by the bus front-end according to the DMA
window selection that's been made.
[4 lines not shown]
rust197: complete the transition to the "new fix" for the memchr crate.
Apply the vector.rs patch consistently also to the 2.7.4 memchr crate,
so that we do not get checksum conflicts for files in newer crates
which are un-changed from 2.7.4 with the older set of patches.
Should complete the fix of https://github.com/rust-lang/rust/issues/159919.
Support for the 21142/21143 internal NWay block is structured like a
PHY driver, but it was overlooked when the ifmedia/mii layer gained a
locking protocol. Update it to avoid a recursive mutex acquisition
that can occur if the autonegotiation completes (very) quickly.
PR kern/60494
