Error in installation documentation #7797
Comments
|
Additionally starman is installed in |
Thanks for the report! I've fixed the 1.11 documentation online and checked - and changed where necessary - all versions of the document back to 1.7 (when the move of conf/ to doc/conf/ was first released). |
Can you point me a bit more specifically where to look? I can't find it in the 1.11 installation document (the one I just changed with respect the By the way, where Starman can be found depends on whether it's installed from CPAN or by the system package manager. In the latter case, you will find it in |
|
I was following the installation instructions from the website, so I guess
CPAN installed starman
…On Sun, 10 Dec 2023, 20:55 Erik Huelsmann, ***@***.***> wrote:
Additionally *starman* is installed in /usr/local/bin contrary to the
systemd doco, which has it in /usr/bin
Can you point me a bit more specifically where to look? I can't find it in
the 1.11 installation document (the one I just changed with respect the
doc/conf/ path).
By the way, where Starman can be found depends on whether it's installed
from CPAN or by the system package manager. In the latter case, you will
find it in /usr/bin; from what I understood from your installation
procedure, you've installed from CPAN, so yours is in /usr/local/bin
indeed. I think this clarification should be added to the documentation.
I'll do it when you point me where to look :-).
—
Reply to this email directly, view it on GitHub
<#7797 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AMS2F7WONW7FBQVESOWH36TYIWBKDAVCNFSM6AAAAABAOCQ7WCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBYHEYTINBZHA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Thanks for your quick reply! Regarding this conversation:
I meant to ask "can you point me a bit more specifically to the point in the docs where it says that starman is in |
|
I don't know that it does mention it in the doco. When starman failed to
start I did "whereis starman" and found it in /usr/local/bin. The systemd
script explicitly calls /usr/bin/starman. As /usr/local/bin is usually in
$PATH it may be more appropriate to modify the systemd script to exclude
the explicit path and just call "starman" instead.
…On Tue, 12 Dec 2023 at 06:51, Erik Huelsmann ***@***.***> wrote:
Thanks for your quick reply! Regarding this conversation:
Additionally *starman* is installed in /usr/local/bin contrary to the
systemd doco, which has it in /usr/bin
Can you point me a bit more specifically where to look? I can't find it in
the 1.11 installation document (the one I just changed with respect the
doc/conf/ path).
I meant to ask "can you point me a bit more specifically to the point in
the docs where it says that starman is in /usr/bin?" because I'm having
trouble finding the point in the docs where it does. I suspect I'm looking
in the wrong place though...
—
Reply to this email directly, view it on GitHub
<#7797 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AMS2F7Q6XZASUS5VTUFWDWLYI5P3PAVCNFSM6AAAAABAOCQ7WCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJQG43TSNZXHE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
Howard.
--
When you want a computer system that works, just choose Linux;
When you want a computer system that works, just, choose Microsoft.
|
|
I don't think the systemd commands are executed with a PATH sein. (Not sure though). Anybody using starman from their package repository (the majority?) will have it in /use/bin. Our Debian package also uses this file with minimal changes. I prefer to keep things simple for packages. Those installing by themselves without using Docker I expect they know what they are doing. That leaves all actions in this issue addressed. Closing. |
|
The problem for me is that Docker is only available for AMD64 architecture,
not the armhf of the Raspberry Pi. The Raspberry Pi is a low cost option
for small business accounting - AU$170 for the Pi400 kit and AU$110 for a
21" screen - nothing else required 😀
…On Sun, 17 Dec 2023, 19:25 Erik Huelsmann, ***@***.***> wrote:
I don't think the systemd commands are executed with a PATH sein. (Not
sure though). Anybody using starman from their package repository (the
majority?) will have it in /use/bin. Our Debian package also uses this file
with minimal changes. I prefer to keep things simple for packages. Those
installing by themselves without using Docker I expect they know what they
are doing.
That leaves all actions in this issue addressed. Closing.
—
Reply to this email directly, view it on GitHub
<#7797 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AMS2F7RNV3KWAWRVLADO6DDYJ2T6LAVCNFSM6AAAAABAOCQ7WCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJZGA3TCMZYGY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Version
Version 1.11.4
What browsers are you seeing the problem on?
This problem isn't browser related
What happened?
In the link https://ledgersmb.org/content/installing-ledgersmb-111, when dealing with setting up systemd, there is the line
sed -e "s#WORKING_DIR#$PWD#" conf/systemd/ledgersmb_starman.service \ | sudo tee /etc/systemd/system/ledgersmb-starman.serviceExecuting this produces the error
sed: can't read conf/systemd/ledgersmb_starman.service: No such file or directoryWhat should have happened?
The
conf/directory is nowdoc/conf/On line documentation needs correction
The text was updated successfully, but these errors were encountered: