Failed dependencies

General issues about GOWrite...
Anything not bug, specific new feature or need for support to this forum.

Moderator: lpaatero

Post Reply
johny
Posts: 14
Joined: Fri Apr 29, 2016 9:07 pm

Failed dependencies

Post by johny » Thu Jun 14, 2018 8:57 pm

I am trying to install 3.0.14 onto mac os x.
johyn@bonjour:~/Downloads$ rpm -i gowrite-3.0.14-1.noarch.rpm
error: Failed dependencies:
/bin/bash is needed by gowrite-3.0.14-1.noarch
/bin/sh is needed by gowrite-3.0.14-1.noarch

But I have bash and sh in the shell:
johny@bonjour:~/Downloads$ which bash
/bin/bash
johny@bonjour:~/Downloads$ which sh
/bin/sh

What is causing this problem?

johny
Posts: 14
Joined: Fri Apr 29, 2016 9:07 pm

Re: Failed dependencies

Post by johny » Fri Jun 15, 2018 12:04 am

Found a solution here:
https://unix.stackexchange.com/question ... m-on-a-mac

Basically, just extract files from the rpm package and put it in my local home directory, then run it from there.

By the way, it looks like the script 'gowrite' works well, while 'gowrite2' doesnt:
johny@bonjour:~/gowrite2$ ./gowrite2
starting GO Write 2...
mknod: illegal option -- m
usage: mknod [-F format] name [b | c] major minor
mknod [-F format] name [b | c] major unit subunit
mknod name [b | c] number
mknod name w
johny@bonjour:~/gowrite2$

lpaatero
Go liiton hallitus
Posts: 461
Joined: Fri May 21, 2004 12:20 pm
Location: Finland

Re: Failed dependencies

Post by lpaatero » Sun Jun 17, 2018 2:36 pm

Thanks for pointing out the mknod issue. I will replace it with mkfifo in next release. mkfifo should also work in mac.

The "other platform" ZIP installation file can be used to do the same, unzipping it gives all needed to run.

regards
Lauri

Blankerson
Posts: 1
Joined: Wed Jul 04, 2018 11:25 am

Re: Failed dependencies

Post by Blankerson » Wed Jul 11, 2018 1:05 pm

Hi Lauri, when's the next release due? I was going to go back to GOWrite, but if it's soon I think I'll wait for it. Better to do that then worry about issues like this, right?

lpaatero
Go liiton hallitus
Posts: 461
Joined: Fri May 21, 2004 12:20 pm
Location: Finland

Re: Failed dependencies

Post by lpaatero » Mon Jul 16, 2018 8:43 am

I do not have any other changes ready, so it could take a while until I create next update.

The correction I made is simple:
replace the line with mknod command in gowrite2 script file with

Code: Select all

mkfifo -m 700 ~/.gowrite/cmd
mkfifo command should be available in almost everywhere

regards
Lauri

johny
Posts: 14
Joined: Fri Apr 29, 2016 9:07 pm

Re: Failed dependencies

Post by johny » Fri Mar 01, 2019 6:19 pm

mkfifo works, Lauri. But it looks the change hasn't been made to the script gowrite2 in the latest 3.0.17 version. As far as I know, mkfifo is more portable and standardized than mknod, so it should be the preferred one.

By the way, Lauri, each time the script gowrite2 is invoked, there will be a pipe named "p" created in the current directory, like:

Code: Select all

prwx------   1 johny  bonjour     0 Mar  1 11:22 p
Looks to me that this pipe is redundant (or typo), because ~/.gowrite/cmd is already created in the first place.

This is the change I would suggest for the script gowrite2:

Code: Select all

johny@bonjour:~/gowrite2$ diff gowrite2.org gowrite2
40c40
<   mknod -m 700 ~/.gowrite/cmd p
---
>   mkfifo -m 700 ~/.gowrite/cmd
Thanks,
johny

lpaatero
Go liiton hallitus
Posts: 461
Joined: Fri May 21, 2004 12:20 pm
Location: Finland

Re: Failed dependencies

Post by lpaatero » Fri Mar 01, 2019 10:14 pm

Thanks for reporting.

My repo has correct script, so it seems build script has failed somehow, and taken something crap :(

Created version 3.0.18 for ZIP and RPM. Can you check if everything is right now?
It looks fine on my machine.

regards
Lauri

johny
Posts: 14
Joined: Fri Apr 29, 2016 9:07 pm

Re: Failed dependencies

Post by johny » Sat Mar 02, 2019 6:19 pm

Hi Lauri,

I've downloaded and tried the zip format of 3.0.18, and it looks pretty good. No problem found so far. Thanks for checking and updating.

Have a nice weekend!
johny

Post Reply