guix_mirror_bot pushed a change to branch kde-team
in repository guix.
discard 849c0d0f10 gnu: sweeper: Update to 25.08.2.
discard f823d9cb64 gnu: ktimer: Update to 25.08.2.
discard 30125d22ef gnu: kmouth: Update to 25.08.2.
discard 19f044cc5b gnu: kmousetool: Update to 25.08.2.
discard 98c7d5c05d gnu: kmag: Update to 25.08.2.
discard 400664b6ff gnu: kontrast: Update to 25.08.2.
discard 2f579fc860 gnu: kongress: Update to 25.08.2.
discard 8f3d6b79ba gnu: kfind: Update to 25.08.2.
discard 60f5817863 gnu: keysmith: Update to 25.08.2.
new 9201770a8f gnu: keysmith: Update to 25.08.2.
new 59d9bdd77e gnu: kfind: Update to 25.08.2.
new 23401ce4e0 gnu: kongress: Update to 25.08.2.
new c28c78e1ee gnu: kontrast: Update to 25.08.2.
new b499d8b655 gnu: kmag: Update to 25.08.2.
new 51197e2e8e gnu: kmousetool: Update to 25.08.2.
new 9a2540dbf3 gnu: kmouth: Update to 25.08.2.
new 6567fcbcef gnu: ktimer: Update to 25.08.2.
new 5bf664eaa0 gnu: sweeper: Update to 25.08.2.
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 (849c0d0f10)
\
N -- N -- N refs/heads/kde-team (5bf664eaa0)
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/kde-utils.scm | 1 +
1 file changed, 1 insertion(+)
