From: Gary Johnson <lambdatronic@disroot.org>
To: Remco <me@rwv.io>
Cc: help-guix@gnu.org
Subject: Re: What happened to gfortran-toolchain?
Date: Mon, 10 Jan 2022 11:14:31 -0500 [thread overview]
Message-ID: <87czkzin3i.fsf@disroot.org> (raw)
In-Reply-To: <87h7agzrnv.fsf@rwv.io>
Hi Remco,
Yes. That appears to have fixed the problem. I pulled and was then
able to once again reinstall gfortran-toolchain.
Cheers,
Gary
Remco <me@rwv.io> writes:
>> Could this hidden-package form be the culprit here? Was hiding gfortran
>> an intentional change to Guix System, or was this an accident? If the
>> former, what is the current recommended approach for Fortran programming
>> on Guix?
>
> Just came across this commit which was made about an hour before your
> message:
>
> https://git.savannah.gnu.org/cgit/guix.git/commit/?id=af1b5de6d8a54439ef3f7e1f5fe9a8e7d109972d
>
> Does that fix the problem for you?
>
> Cheers,
> Remco
--
GPG Key ID: 7BC158ED
Use `gpg --search-keys lambdatronic' to find me
Protect yourself from surveillance: https://emailselfdefense.fsf.org
=======================================================================
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
Why is HTML email a security nightmare? See https://useplaintext.email/
Please avoid sending me MS-Office attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
prev parent reply other threads:[~2022-01-10 16:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-06 16:39 What happened to gfortran-toolchain? Gary Johnson
2022-01-06 17:43 ` Remco
2022-01-10 16:14 ` Gary Johnson [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=87czkzin3i.fsf@disroot.org \
--to=lambdatronic@disroot.org \
--cc=help-guix@gnu.org \
--cc=me@rwv.io \
/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.
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).