all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: 48926@debbugs.gnu.org
Cc: guix-sysadmin@gnu.org
Subject: bug#48926: Cuirass is not building Mutt
Date: Tue, 8 Jun 2021 15:09:32 -0400	[thread overview]
Message-ID: <YL/AbAMtXG3UpMVW@jasmine.lan> (raw)

Recently I noticed that I'm not getting substitutes for Mutt.

Looking at the ci.guix.gnu.org web interface, it seems that we stopped
building Mutt about a month ago:

https://ci.guix.gnu.org/search?query=spec%3Amaster+mutt-2.0.7+system%3Ax86_64-linux

And `guix weather` confirms that we seem to have stopped building it:

------
$ guix describe          
Generation 174	Jun 08 2021 14:59:25	(current)
  guix 74c7055
    repository URL: https://git.savannah.gnu.org/git/guix.git
    commit: 74c70553394e32f7b6d5fa56da3bf3b18623c70f
$ guix weather mutt      
computing 1 package derivations for x86_64-linux...
looking for 1 store items on https://ci.guix.gnu.org...
https://ci.guix.gnu.org
  0.0% substitutes available (0 out of 1)
  unknown substitute sizes
  0.0 MiB on disk (uncompressed)

  0.0% (0 out of 1) of the missing items are queued
  at least 1,000 queued builds
      x86_64-linux: 906 (90.6%)
      aarch64-linux: 9 (.9%)
      i686-linux: 85 (8.5%)
  build rate: .00 builds per hour
      x86_64-linux: 0.00 builds per hour
      i686-linux: 0.00 builds per hour
      aarch64-linux: 0.00 builds per hour
------

I wonder what is going on?




             reply	other threads:[~2021-06-08 19:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-08 19:09 Leo Famulari [this message]
2021-06-09  9:35 ` bug#48926: Cuirass is not building Mutt Mathieu Othacehe
2021-06-18  9:37   ` Ludovic Courtès
2021-06-18  9:48     ` Mathieu Othacehe
2021-06-18  9:49       ` Mathieu Othacehe
2021-06-28 13:11       ` Ludovic Courtès
2021-12-19 17:04         ` Mathieu Othacehe

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YL/AbAMtXG3UpMVW@jasmine.lan \
    --to=leo@famulari.name \
    --cc=48926@debbugs.gnu.org \
    --cc=guix-sysadmin@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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.