Skip to content
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

Meta: Warn users about creating forks of outdated software #163

Open
josephbisch opened this issue Jan 7, 2018 · 2 comments
Open

Meta: Warn users about creating forks of outdated software #163

josephbisch opened this issue Jan 7, 2018 · 2 comments

Comments

@josephbisch
Copy link
Collaborator

There seems to have been a lot of recent issues posted by people that are creating forks using some guide that seems to instruct them to create a fork of an old version of Litecoin or something.

They end up with a fork containing Gitian descriptors such as this descriptor, which uses Ubuntu Lucid which has been eol since 2013. They end up running into compilation issues and the issues they post in the issue tracker here often lack important information such as which coin they are trying to build. Even when they are successful in building, the use of Ubuntu Lucid in 2018 is questionable, to put it lightly.

So should we put a warning at the top of the README about following outdated guides and using old versions of distros for the builds? Should we use a template for issues so that people are prompted to link to the descriptor they are trying to use if they have an issue concerning a specific project that uses Gitian? Should we do both?

@devrandom
Copy link
Owner

An issue template is likely a good idea. I'm slightly worried that we are providing tech support outside of the scope of this project, but maybe it's OK if we have the bandwidth and it's not too much of a burden.

@josephbisch
Copy link
Collaborator Author

Yeah, I'm also worried about providing tech support outside of Gitian itself. I'm going to stop dealing with issues that are obviously caused by the particular descriptor rather than Gitian itself, because there has been an increase in the number of such issues and the projects are obviously not reading the documentation here and using current examples to model their Gitian usage after.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants