-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When a responce from the developer/maintaner is expected #7
Comments
Sadly, I can't provide any estimates. I had even talked him by phone two years ago, but still no progress. |
If its been 2 years ago then he is likely not going to do anything. Which means you could either ask him if the main project should move here, or declare an official fork. |
Is it possible to ask you to push him or mhddfs maintainers in mainline distros? I also believe that this changes should be adopted by upstream ASAP, but don't have enough time for doing politics. The essence of this repo is in the following commits: 403e52f: nailed the first and most pesky segfault that I have found while running mhddfs in production What I also have to say is that I'm using this one in production for two years, and there were no 'Transport endpoint not connected' issue since I have done all of these changes. Best Regards, Valentin |
I spoke to a debian developer, what you can do at least for debian/ubuntu is to propose a "non-maintainer upload" or nmu. There are several guides to do that, initially you need to open a bug. |
If you get stuck during the bug opening you can also ask @kaplanlior for advice |
Its written several times in the readme, thought it might be a good idea to document its progress
The text was updated successfully, but these errors were encountered: