From: Gottfried <gottfried@posteo.de>
To: Csepp <raingloom@riseup.net>
Cc: help-guix@gnu.org
Subject: Re: guix weather
Date: Mon, 22 May 2023 14:21:06 +0000 [thread overview]
Message-ID: <e9c28c71-2e60-5bb1-ffe4-054b898ca10a@posteo.de> (raw)
In-Reply-To: <87r0r9st6n.fsf@riseup.net>
[-- Attachment #1.1.1: Type: text/plain, Size: 1336 bytes --]
Hi,
thanks very much.
this worked:
gfp@Tuxedo ~$ guix weather -m /home/gfp/Projekte/Lilypond/lilypond.scm
so it is a valid manifest
Kind regards
Gottfried
Am 21.05.23 um 15:31 schrieb Csepp:
>
> Gottfried <gottfried@posteo.de> writes:
>
>> [[PGP Signed Part:Undecided]]
>> Hi,
>>
>> what is the command for checking my manifest "lilypond.scm" with guix
>> weather?
>>
>> guix weather -m lilypond.scm
>> does not work
>>
>> guix weather -m lilypond.scm=/home/gpf/Projekte/Lilypond
>> does not work either
>>
>> my "lilypond.scm" file is in: /home/gpf/Projekte/Lilypond/
>>
>>
>> Kind regards
>>
>> Gottfried
>>
>> [2. OpenPGP public key --- application/pgp-keys; OpenPGP_0x61FAF349C9FB7F94.asc]...
>>
>> [[End of PGP Signed Part]]
>
> If it's a valid manifest, then guix weather -m /path/to/the/manifest.scm
> If that doesn't work, then either you are using the wrong path or it's
> not a valid manifest file.
>
>
> If it can't find the file using a relative path (ie.: one that does not
> start with a slash) then you should use an absolute path, like so:
> /home/gpf/Projekte/Lilypond/lilypond.scm
>
> This:
> lilypond.scm=/home/gpf/Projekte/Lilypond
> is definitely not going to work. Guix uses that syntax for package
> transformations, not files.
--
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3191 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
prev parent reply other threads:[~2023-05-22 14:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-21 11:56 guix weather Gottfried
2023-05-21 13:31 ` Csepp
2023-05-22 14:21 ` Gottfried [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e9c28c71-2e60-5bb1-ffe4-054b898ca10a@posteo.de \
--to=gottfried@posteo.de \
--cc=help-guix@gnu.org \
--cc=raingloom@riseup.net \
/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.