all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Oleg Pykhalov <go.wigust@gmail.com>
To: Tanguy LE CARROUR <tanguy@bioneland.org>
Cc: Help Guix <help-guix@gnu.org>,  Nils Landt <nils@landt.email>
Subject: Re: "Command not found" when using `home-mcron-service`
Date: Mon, 15 Jan 2024 18:25:27 +0300	[thread overview]
Message-ID: <87h6jeehzs.fsf@gmail.com> (raw)
In-Reply-To: <170532260816.14803.15496485777094283367@bioneland.org> (Tanguy LE CARROUR's message of "Mon, 15 Jan 2024 13:43:28 +0100")

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

Tanguy LE CARROUR <tanguy@bioneland.org> writes:

> If I'm correct, setting the PATH environment variable in the mcron job
> should fix it.
>
> You mean inside the `#~(job …)`? Sorry, but… how would you do that? 😅
> And this means that I would have to do it for every single job? 🤔
> Sounds suboptimal to me.



> Quoting Tanguy LE CARROUR (2024-01-15 13:30:35)
>> Quoting Nils Landt (2024-01-15 13:03:06)
>> > > Tanguy LE CARROUR <tanguy@bioneland.org> hat am 15.01.2024 10:38 CET
>> > > geschrieben:
>> > > […]
>> > > `mbsync` is in my profile, but Mcron cannot find it.
>> > > Do I have to declare all the required packages… somehow?! 🤔
>> > 
>> > That sounds like it's related to this issue I reported:
>> > https://issues.guix.gnu.org/65471
>> 
>> It looks like, indeed!
>
> Actually, there's a "small" difference: I'm not using Debian, but… Guix
> System! 🤔

The Home service matches Guix System in this case, so currently
specification of a full path to a binary is required.

It's possible to do in several ways:

1) Use full path to the binary with ungexp, e.g.

preferred and cleaner:

    #$(file-append notmuch "/bin/notmuch")

or:
    (string-append #$notmuch "/bin/notmuch")

Hint: make sure notmuch is defined, e.g. at the top of a file:

    (use-modules (gnu packages mail))


2) Symlink resolving in a Guix profile, e.g.:

    "/home/user123/.guix-profile/bin/notmuch"

or

    (readlink "/home/user123/.guix-profile/bin/notmuch")


I would recommend for 1) because of reproducibility and easier to track
in future, especially if you have a lot of self managed services.


Oleg.

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

  reply	other threads:[~2024-01-15 15:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-15  9:38 "Command not found" when using `home-mcron-service` Tanguy LE CARROUR
2024-01-15 12:03 ` Nils Landt
2024-01-15 12:30   ` Tanguy LE CARROUR
2024-01-15 12:43     ` Tanguy LE CARROUR
2024-01-15 15:25       ` Oleg Pykhalov [this message]
2024-01-15 16:17         ` Tanguy LE CARROUR
2024-01-15 17:13           ` Oleg Pykhalov
2024-01-16  7:22             ` Tanguy LE CARROUR
2024-01-15 18:11     ` Nils Landt
2024-01-16  7:10       ` Tanguy LE CARROUR

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=87h6jeehzs.fsf@gmail.com \
    --to=go.wigust@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=nils@landt.email \
    --cc=tanguy@bioneland.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.