guix_mirror_bot pushed a change to branch astro-update
in repository guix.
discard 6edfe1e4fe gnu: python-holodeck: Limit parallel tests to 8 threads.
discard aa67a739e2 gnu: Add spot-nik.
discard 96898ac2ad gnu: Add python-euclidlike.
discard 03baa5e9bf gnu: Add python-astronify.
discard 23c69f87e6 gnu: Add python-pyo.
discard 6c7dd95b86 gnu: python-sunkit-image: Update to 0.7.0.
discard 156e85be08 gnu: splash: Update to 3.12.0.
new b8f112768a gnu: python-sunkit-image: Update to 0.7.0.
new 3080c68508 gnu: python-romancal: Update to 0.22.0-0.cbdb56a.
new 598bc27d77 gnu: splash: Update to 3.12.0.
new f38be04a38 gnu: python-holodeck: Limit parallel tests to 8 threads.
new bc4d981181 gnu: python-pyhalo: Skip one more test.
new 36652f05f6 gnu: Add python-pyo.
new d2f3b4f765 gnu: Add python-astronify.
new 6b707e3889 gnu: Add python-euclidlike.
new 862ad83bed gnu: Add spot-nik.
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 (6edfe1e4fe)
\
N -- N -- N refs/heads/astro-update (862ad83bed)
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 9 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 | 38 ++++++++++++++++++++++++++++----------
1 file changed, 28 insertions(+), 10 deletions(-)
