guix_mirror_bot pushed a change to branch python-team
in repository guix.
discard 3a5b6b846a gnu: python-anaconda-cli-base: Use python-pytest-8.
discard 030327c1da gnu: proton-vpn-cli: Update to 0.1.5.
discard c9d0a306d1 gnu: pass-git-helper: Fix build.
discard 83153662f7 gnu: pairadise: Disable missing tests.
discard f16a41d257 gnu: liquidctl: Fix build.
discard c82e7b9264 gnu: libmemcached: Fix build.
discard 2ec4a92bcb gnu: fenics: Fix tests.
discard f21f4b8b18 gnu: httpie: Skip 2 tests.
discard bdf4180d12 gnu: gourmet: Fix build.
new e9613b5602 gnu: gourmet: Fix build.
new 57202ed044 gnu: httpie: Skip 2 tests.
new 455c9ea3b0 gnu: fenics: Fix tests.
new a6bc69af5c gnu: libmemcached: Fix build.
new b5f47f7e94 gnu: liquidctl: Fix build.
new 6d5ac947d0 gnu: pairadise: Disable missing tests.
new 427a736a42 gnu: pass-git-helper: Fix build.
new b079b26d40 gnu: proton-vpn-cli: Update to 0.1.5.
new 8d20adadbe gnu: python-anaconda-cli-base: Use python-pytest-8.
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 (3a5b6b846a)
\
N -- N -- N refs/heads/python-team (8d20adadbe)
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/nutrition.scm | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
