From: Andreas Enge <andreas@enge.fr>
To: Superfly Johnson <superfly.johnson@yahoo.com>
Cc: guix-devel@gnu.org
Subject: Re: Fetchmail's fetchmail conf does not work on Gentoo
Date: Fri, 20 Sep 2024 09:09:26 +0200 [thread overview]
Message-ID: <Zu0fpg-Xa9dFtL1P@jurong> (raw)
In-Reply-To: <6070efd9-c41b-4d8c-93c9-84dae99a1af2@yahoo.com>
Hello,
Am Thu, Sep 19, 2024 at 08:20:56PM -0400 schrieb Superfly Johnson:
> Hi again Guix-Devel mailing list. I'm currently trying to configure a
> fetchmail daemon on my gentoo laptop to get mails. Unfortunately,
> fetchmailconf will not execute properly. It will always return line 2: exec:
> :: not found.
>
> I have looked at the file it is trying to execute. The entire script is
>
> #!/gnu/store/3jhfhxdf6v5ms10x5zmnl166dh3yhbr1-bash-minimal-5.1.16/bin/sh
> exec : /fetchmailconf.py "$@"
>
> It seems to me like the path to fetchmailconf needs to be corrected.
I have had a quick look, but definitely more needs to be done.
fetchmailconf.py is part of the source code, but it is not installed.
I tried to execute it, using "python3" instead of "python";
then it complains about
Traceback (most recent call last):
File "/tmp/fetchmail-6.4.37/fetchmailconf.py", line 14, in <module>
from past.builtins import execfile
ModuleNotFoundError: No module named 'past'
Apparently, and logically, this requires the python-future package.
So maybe this should become a propagated input?
I will stop here and let people who actually know Python intervene :)
Andreas
next prev parent reply other threads:[~2024-09-20 7:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6070efd9-c41b-4d8c-93c9-84dae99a1af2.ref@yahoo.com>
2024-09-20 0:20 ` Fetchmail's fetchmail conf does not work on Gentoo Superfly Johnson
2024-09-20 7:09 ` Andreas Enge [this message]
2024-09-20 9:44 ` Tobias Geerinckx-Rice
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=Zu0fpg-Xa9dFtL1P@jurong \
--to=andreas@enge.fr \
--cc=guix-devel@gnu.org \
--cc=superfly.johnson@yahoo.com \
/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.