-
Notifications
You must be signed in to change notification settings - Fork 5
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
README contains dead or stale links to vdr-developer.de #2
Comments
A mirror of the now defunct projects.vdr-developer.org has been set up at GitLab, including for this project https://gitlab.com/vdr-projects/vdr-plugin-rpihddevice. It is still at the above mentioned 1.0.4 version. |
@dr-m IMHO the "original" vdr-projects - which tries to group, co-maintain or maintain vdr plugins and related stuff is https://github.com/vdr-projects (134 repositories), is the successor of projects.vdr-developer.org. https://gitlab.com/vdr-projects is a single-person project with 9 repositories. |
@madmartin Thank you for the clarification. https://github.com/vdr-projects currently links to https://vdr-projects.github.io/ which in turn links to this repository and not https://github.com/vdr-projects/vdr-plugin-rpihddevice (which has diverged from this one). I hope that this situation can be clarified soon. |
It looks like GitHub thought that #6 would fix this issue, only because in my initial comment I mentioned that one of the included bug fixes was fixed differently in a commit:
|
As far as I can tell, the @madmartin I think that the fork https://github.com/vdr-projects/vdr-plugin-rpihddevice needs to be deleted, or rebased with this repository. |
I have no access to this, I can only open an issue in that repo. |
@dr-m please see vdr-projects#1 |
Can someone provide a new pull request to fix the links in this repos README file? |
I can do that. |
I was thoroughly confused by the following comment in the
README
file:That URL does work, but it has not been updated since 4744541. Furthermore:
Anything at http://projects.vdr-developer.org seems to currently return an internal error. I think that it did work some days or weeks ago.
The text was updated successfully, but these errors were encountered: