guix_mirror_bot pushed a change to branch astro-update
in repository guix.
discard 453883d6ec gnu: python-astropy: Update to 8.0.1.
discard 8aa3fe96ce gnu: python-astropy-7: Update to 7.2.2.
discard 5d5e22fe89 gnu: specification-astropy-data: Update to 0.0.0-3.7db2a3f.
discard c7b7751d07 gnu: python-astropy-iers-data: Update to 0.2026.7.6.1.1.20.
add e156a6c620 gnu: emacs-elfeed: Update to 4.1.0.
add 894df36f58 gnu: emacs-hel: Update to 0.12.0.
add 4abf34c2db gnu: Add emacs-hel-leader.
new 7b7fdba9a0 gnu: python-astropy-iers-data: Update to 0.2026.7.6.1.1.20.
new bae51e9814 gnu: specification-astropy-data: Update to 0.0.0-3.7db2a3f.
new 449aba3bcf gnu: python-astropy-7: Update to 7.2.2.
new 748a22bd73 gnu: python-astropy: Update to 8.0.1.
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 (453883d6ec)
\
N -- N -- N refs/heads/astro-update (748a22bd73)
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 4 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 | 45 +++++++++++++++++++++++++++++++++++++--------
1 file changed, 37 insertions(+), 8 deletions(-)
