From: "Ludovic Courtès" <ludo@gnu.org>
To: guix-devel <guix-devel@gnu.org>
Subject: Automatically testing package updates
Date: Mon, 02 Dec 2024 14:44:10 +0100 [thread overview]
Message-ID: <87iks2urmd.fsf@gnu.org> (raw)
Hello Guix!
A new patch series that has just landed¹ adds a ‘--dependents’ flag (and
also ‘--development’) to ‘guix build’, which makes it easier to build
dependents when modifying a package.
It also adds ‘etc/upgrade-manifest.scm’, a manifest that grabs and
returns the latest upstream version of a few security-critical packages.
More precisely, it returns two things:
1. Individual package updates. Update each of libgcrypt, libgit2,
etc. independently and return the updated packages together with
their direct dependents.
2. Joint package updates. Update all these packages at once and
return their dependents at distance two.
The result can be seen here (x86_64-linux only):
https://ci.guix.gnu.org/jobset/security-updates
You can go to the dashboard:
https://ci.guix.gnu.org/eval/latest/dashboard?spec=security-updates
… and type, for example, “latest-libgpg-error” (to view the libgpg-error
update and its dependents) or “full-upgrade” (to view all the dependents
of that set of packages).
Some examples:
• guile-ssh fails to build with the latest libssh:
<https://ci.guix.gnu.org/build/6753990/log>.
• libgcrypt cannot be upgraded without libgpg-error:
<https://ci.guix.gnu.org/build/6754153/log>.
• libgcrypt 1.11.0 builds fine when upgraded jointly with its
dependents: <https://ci.guix.gnu.org/build/6754305/details>
• gnutls 3.8.8 has one test failure:
<https://ci.guix.gnu.org/build/6753571/log>.
• curl 8.11.0 has one test failure:
<https://ci.guix.gnu.org/build/6753884/log>.
This manifest is just an example. We could come up with manifests
targeting package collections like CRAN packages, astronomy packages,
and so on.
Feedback welcome!
Ludo’.
¹ https://issues.guix.gnu.org/74542
next reply other threads:[~2024-12-02 14:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 13:44 Ludovic Courtès [this message]
2024-12-02 14:50 ` Automatically testing package updates Simon Tournier
2024-12-02 19:14 ` Simon Tournier
2024-12-02 19:16 ` Simon Tournier
2024-12-05 7:20 ` Efraim Flashner
2024-12-05 8:06 ` Hilton Chain
2024-12-05 9:23 ` Ricardo Wurmus
2024-12-05 13:29 ` Suhail Singh
2024-12-05 15:31 ` Ricardo Wurmus
2024-12-05 16:10 ` Suhail Singh
2024-12-05 19:07 ` Attila Lendvai
2024-12-05 19:55 ` Ricardo Wurmus
2024-12-06 5:09 ` Suhail Singh
2024-12-14 23:46 ` Ludovic Courtès
2024-12-06 4:53 ` Suhail Singh
2024-12-05 19:58 ` Ricardo Wurmus
2024-12-03 0:32 ` Vagrant Cascadian
2024-12-14 23:47 ` Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2024-12-03 14:01 Sharlatan Hellseher
2024-12-14 23:51 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87iks2urmd.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).