guix_mirror_bot pushed a change to branch astro-update
in repository guix.
discard 748a22bd73 gnu: python-astropy: Update to 8.0.1.
discard 449aba3bcf gnu: python-astropy-7: Update to 7.2.2.
discard bae51e9814 gnu: specification-astropy-data: Update to 0.0.0-3.7db2a3f.
discard 7b7fdba9a0 gnu: python-astropy-iers-data: Update to 0.2026.7.6.1.1.20.
add f181089f1c gnu: python-astropy-7: Use python-astropy-iers-data.
add aa641a7175 gnu: python-astropy-iers-data-next: Update to
0.2026.7.6.1.1.20.
new 5ddad1af62 gnu: python-astropy-iers-data: Update to 0.2026.7.6.1.1.20.
new 69056ae4f5 gnu: specification-astropy-data: Update to 0.0.0-3.7db2a3f.
new f43d253a35 gnu: python-astropy-7: Update to 7.2.2.
new aac23f9707 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 (748a22bd73)
\
N -- N -- N refs/heads/astro-update (aac23f9707)
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/astronomy.scm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
