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

SETUP.md repo sed substitution is failing #92

Closed
dhimmel opened this issue Nov 13, 2017 · 6 comments
Closed

SETUP.md repo sed substitution is failing #92

dhimmel opened this issue Nov 13, 2017 · 6 comments

Comments

@dhimmel
Copy link
Member

dhimmel commented Nov 13, 2017

At the OpenCon do-a-thon, we've had 2 users experience potentially faulty substitutions. Rather than rebranding their README to USER/REPO, their README.md is rebranded to USER/USER. Possibly introduced in #84?

The two examples are https://github.com/zambujo/manubot/commit/10397d6a05235c3517ac981b9b3c67920c226b9a are broadwym/manu1@64954e5.

Interestingly one user did not have the issue: https://github.com/schliebs/open_manuscript/commit/77da6c844ac061061c03b93721e7eade90fabd99, making me wonder whether its user error or not.

SETUP.md currently uses:

sed "s/greenelab/$OWNER/g" README.md > tmp && mv -f tmp README.md
sed "s/manubot-rootstock/$REPO/g" README.md > tmp && mv -f tmp README.md

@vsmalladi any ideas what could be happening?

@agitter
Copy link
Member

agitter commented Nov 13, 2017

@dhimmel (or @zambujo and @broadwym) what operating system was used on the failed setup?

@vsmalladi
Copy link
Collaborator

@dhimmel that is weird, not sure why it would fail since we didn't change the syntax.

@dhimmel
Copy link
Member Author

dhimmel commented Nov 13, 2017

what operating system was used on the failed setup?

@zambujo was on Linux (had issue), @broadwym was on Windows (had issue), and @schliebs was on Windows (no issue).

not sure why it would fail since we didn't change the syntax

Yeah me too. Therefore I thought user error is most likely. Although I'm surprised that two people had the same issue. Also @zambujo thought that he didn't make an error.

@vsmalladi
Copy link
Collaborator

I can try a full test on Mac and see if anything inadvertently changed.

@vsmalladi
Copy link
Collaborator

@dhimmel I tested this weekend and everything worked fine setting up.

@dhimmel
Copy link
Member Author

dhimmel commented Nov 27, 2017

I tested this weekend and everything worked fine setting up.

Cool, I'll close this issue and we'll assume there was user error rather than faulty commands.

One thing I noticed is that the demo users would often retype commands rather than copy and paste, which could be the source of some errors.

@dhimmel dhimmel closed this as completed Nov 27, 2017
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

3 participants