Forums : Technical Issue Help
Dear Open Hub Users,
We’re excited to announce that we will be moving the Open Hub Forum to
https://community.blackduck.com/s/black-duck-open-hub.
Beginning immediately, users can head over,
register,
get technical help and discuss issue pertinent to the Open Hub. Registered users can also subscribe to Open Hub announcements here.
On May 1, 2020, we will be freezing https://www.openhub.net/forums and users will not be able to create new discussions. If you have any questions and concerns, please email us at
info@openhub.net
bioconductor erroneously marked as abandoned
Hello,
The bioconductor project is marked as abandoned but in fact is going stronger than ever. Can you fix this?
The svn url is
https://hedgehog.fhcrc.org/bioconductor/trunk/madman/Rpacks/
The login is readonly/readonly.
Thanks.
Dan / Bioconductor team
Dan,
The problem appears to be an insistence on some cog along the way that every commit has a commit message... There are a few in the early revs that appear to have no message. There are admin tools to fix this retroactively. Let me know if you can deal with any of this or I can look deeper and see if the requirement is legit or a bug.
Thanks!
Hi,
Thanks for looking into this.
Yes, there is a requirement that all commits have commit messages at least 10 characters long.
Is it a requirement of Ohloh that every commit have a message?
I would just as soon not try and second-guess developers from years ago by changing their commit messages, even if they were empty (and replacing them with some generic string such as 'automatically added commit message').
If Ohloh is requiring that every commit have a message, then I can tell you from experience you are going to run into this problem a lot, and not just in this project. It seems to make more sense to me to see if something can change on the Ohloh side, or just to make it clear that non-empty commit messages are a requirement.
In any case, please let me know what you decide to do.
Thanks!
Dan
Dan,
The way I interpret it for now, I think it is a requirement of the tools we use rather than a requirement ohloh has set. I will escalate this up the chain and see if it has been seen before... I haven't seen this particular error before and I suspect it's one of those phase-of-the-moon errors that only happen infrequently. I'll report back here when I have news.
Thanks!