-
Notifications
You must be signed in to change notification settings - Fork 982
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Is this repo still alive ? #663
Comments
Yes, For that matter i had to clone the repository and to make local changes to fix things. Over all it would be nice to know what to expect |
A statement from the maintainers would be nice @BertrandGouny |
hi @nesc58 and @nix-power i use this image and when I run the container inside it i write below command to act as a nfs client but I continuously get this error apt update showmount -e 10.0.0.84 !!!!!!!!!!!!!PLEASE HELP!!!!!!!!!!!!!! |
|
@BertrandGouny any comments? |
I did something like that as well, @nix-power . Forked the repo, modified it, and so on. That docker image does not look much as the original anymore :-) Still, having a baseline to work against would be nice, hence the OP. |
Hello, The update will be a big change. That's why i'm note taking the time to review or merge anything for now. I hope you will understand. Also if a fork is actively maintained i can add a link on the readme to that repository. Let me know. Thanks |
I appreciate your reply, @BertrandGouny , and thank you for it. About the fork, I will see what I can do to push it back publicly. Most of the changes have been pushed in my internal gitea server, and are so customized to my internal LAN that to re-publish the fork will need a lot of work. As in your case, much of what I do here is on my own time. Let me know if you need help, btw. Bonne fin de soirée ! --J.F.Gratton |
thanks @BertrandGouny for the update! |
It is clear that this project is not going to be maintained, so it would be better to abandon it for another one. |
I notice that both master and develop branches are 2yrs+ old.
I'm assuming that this project is dead on its tracks ? Not to mention the 300+ issues opened ?
Just sent an email to the maintainers about that. Not that I'm optimistic about a reply.
The text was updated successfully, but these errors were encountered: