guix_mirror_bot pushed a change to branch gnuzilla-updates
in repository guix.
discard ad4bba28de gnu: Remove rust-cbindgen-0.24 and rust-cbindgen-0.23.
discard bfcd8ad5f7 gnu: icecat: Update to 140.2.0 [security fixes].
discard 6266938424 gnu: nss: Cleanup stale comments.
discard 3d820eaf4f gnu: libical: Update to 3.0.20.
discard d2d3e50ea5 gnu: mozjs: Update to 140.2.0.
discard a50d32be63 gnu: harfbuzz: Update to 11.4.4.
discard a9dc35bcab gnu: icu4c: Update to 77.1.
new 4ca52d6a97 gnu: icedove: Fix localization.
new 5e3298a8d6 gnu: icu4c: Update to 77.1.
new 6a745e7739 gnu: harfbuzz: Update to 11.4.4.
new 4ed3968444 gnu: mozjs: Update to 140.2.0.
new d973dd31f1 gnu: libical: Update to 3.0.20.
new 9a16f49798 gnu: nss: Remove stale comments.
new ee076eb8df gnu: icecat: Update to 140.2.0 [security fixes].
new 7116ca3e80 gnu: Remove rust-cbindgen-0.24 and rust-cbindgen-0.23.
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 (ad4bba28de)
\
N -- N -- N refs/heads/gnuzilla-updates (7116ca3e80)
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 8 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/gnuzilla.scm | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
