guix_mirror_bot pushed a change to branch crypto-team
in repository guix.
omit facca8542a gnu: openldap: Update to 2.6.10.
omit 6b1adb0ba3 gnu: openldap: Refresh input.
omit 447c75a98a gnu: pcsc-lite: Update to 2.4.1
add d7c9d011d7 gnu: fish: Update to 4.3.3.
add d9197db628 gnu: fish: Add localization support.
add 7a544d6882 gnu: sshuttle: Update to 1.3.2.
add 732717b316 gnu: meshlab: Update to 2025.07.
add 48b9e7ea5a gnu: emacs-dape: Update to 0.26.0.
new a6c250efef gnu: pcsc-lite: Update to 2.4.1
new eab5e7786a gnu: openldap: Refresh input.
new 8e24203a5e gnu: openldap: Update to 2.6.10.
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (facca8542a)
\
N -- N -- N refs/heads/crypto-team (8e24203a5e)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 3 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
gnu/packages/emacs-xyz.scm | 4 +-
gnu/packages/engineering.scm | 62 +++++---
.../corrosion-honor-CARGO_BUILD_TARGET.patch | 23 ++-
gnu/packages/rust-crates.scm | 172 ++++++++++++++-------
gnu/packages/shells.scm | 48 +++---
gnu/packages/vpn.scm | 6 +-
6 files changed, 196 insertions(+), 119 deletions(-)
