unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Vagrant Cascadian <vagrant@debian.org>
To: "Ludovic Courtès" <ludo@gnu.org>, guix-devel <guix-devel@gnu.org>
Subject: Re: Automatically testing package updates
Date: Mon, 02 Dec 2024 16:32:42 -0800	[thread overview]
Message-ID: <874j3lppw5.fsf@contorta> (raw)
In-Reply-To: <87iks2urmd.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1157 bytes --]

On 2024-12-02, Ludovic Courtès wrote:
> 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.

Yay!

> Some examples:
>
>   • guile-ssh fails to build with the latest libssh:
>     <https://ci.guix.gnu.org/build/6753990/log>.

This can be fixed by updating to guile-ssh 0.18.0:

  https://issues.guix.gnu.org/74659

Which also works with libssh 0.10.x in guix master.

Running "guix build --dependents guile-ssh" on it now.

First thing I notice is it is trying to build all of rust, which does
not always get a lot of testing on aarch64-linux... so might end up
being a long chain of builds that fail...

Might be nice to have options to exclude specific dependents from the
builds to perform? With guix refresh --list-dependents, it was a bit
difficult, but you could actually manually exclude things from the
output and then only the builds you wanted to try. Maybe something like:

  guix build --dependents PACKAGE --exclude-dependents OTHERPACKAGE


live well,
  vagrant

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

      parent reply	other threads:[~2024-12-03  0:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-02 13:44 Automatically testing package updates Ludovic Courtès
2024-12-02 14:50 ` Simon Tournier
2024-12-02 19:14 ` Simon Tournier
2024-12-02 19:16   ` Simon Tournier
2024-12-03  0:32 ` Vagrant Cascadian [this message]

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=874j3lppw5.fsf@contorta \
    --to=vagrant@debian.org \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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).