From: "Collin J. Doering" via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 68237@debbugs.gnu.org, Kjetil Haugen <Kjetil.Haugen@amd.com>
Subject: bug#68237: Cuirass 1.2.0-1.bdc1f9f local builds never occur
Date: Mon, 15 Jan 2024 17:31:04 -0500 [thread overview]
Message-ID: <87a5p6448d.fsf@rekahsoft.ca> (raw)
In-Reply-To: <87r0ijj5ou.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 987 bytes --]
Excellent! Confirmed latest version 1.2.0-2.7bcd3d0 solves the issue. Also, fwiw I was not on a foreign distro.
Also, thanks for noting that cuirass also is a channel, so in the future I could simply use it directly for upstream changes.
Best wishes!
On 15 Jan 2024 at 10:40, Ludovic Courtès <ludo@gnu.org> wrote:
> Hi,
>
> Ludovic Courtès <ludovic.courtes@inria.fr> skribis:
>
>> Cuirass commits 10a5117936bb51c54a362172b6e53ef5150ab909 and
>> b8ee2486ce877e42a3f910610d3efa8274e2603f appear to fix issues when
>> building in local build mode that most likely explain what you were
>> observing.
>
> If you run ‘guix pull’ now, you’ll get version 1.2.0-2.7bcd3d0 of the
> ‘cuirass’ package, which includes the fixes above.
>
> I’m tentatively closing this issue but please do let me know if you
> notice any problems.
>
> Thanks,
> Ludo’.
--
Collin J. Doering
http://rekahsoft.ca
http://blog.rekahsoft.ca
http://git.rekahsoft.ca
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 515 bytes --]
prev parent reply other threads:[~2024-01-15 22:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 2:39 bug#68237: Cuirass 1.2.0-1.bdc1f9f local builds never occur Collin J. Doering via Bug reports for GNU Guix
2024-01-08 16:44 ` Haugen, Kjetil via Bug reports for GNU Guix
2024-01-09 17:42 ` Ludovic Courtès
2024-01-15 9:40 ` Ludovic Courtès
2024-01-15 18:49 ` Haugen, Kjetil via Bug reports for GNU Guix
2024-01-15 22:31 ` Collin J. Doering via Bug reports for GNU Guix [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=87a5p6448d.fsf@rekahsoft.ca \
--to=bug-guix@gnu.org \
--cc=68237@debbugs.gnu.org \
--cc=Kjetil.Haugen@amd.com \
--cc=collin@rekahsoft.ca \
--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).