Skip to content

OS Detection and specs work on non-centos and future CentOS versions#184

Closed
chrisumbel wants to merge 0 commit into
cloudfoundry:masterfrom
chrisumbel:master
Closed

OS Detection and specs work on non-centos and future CentOS versions#184
chrisumbel wants to merge 0 commit into
cloudfoundry:masterfrom
chrisumbel:master

Conversation

@chrisumbel
Copy link
Copy Markdown

Non-Centos RH OSes (i.e. Fedora which is used on Jenkins) were similarly unable to test because they got trapped out in repository_index.rb. OS detection specs even on CentOS 6 would fail when doing tests for the non-RH OSes.

OS detection on CentOS 7 would fail completely due to format changes for /etc/redhat-release.

OS detection would like have detected incorrectly on >9 as only a single digit was matched by regex.

Integration tests (spec/bin/*) still fail on non-Centos 6, RHEL-based OSes, but all other tests pass now.

Related to #183

@cfdreddbot
Copy link
Copy Markdown

Hey chrisumbel!

Thanks for submitting this pull request!

All pull request authors must have a Contributor License Agreement (CLA) on-file with us. Please sign the appropriate CLA (individual or corporate).

When sending signed CLA please provide your github username in case of individual CLA or the list of github usernames that can make pull requests on behalf of your organization.

If you are confident that you're covered under a Corporate CLA, please make sure you've publicized your membership in the appropriate Github Org, per these instructions.

@chrisumbel chrisumbel closed this May 5, 2015
@nebhale
Copy link
Copy Markdown
Contributor

nebhale commented May 5, 2015

@chrisumbel Did you intend to close this issue? Contribution looks good other than the rubocop failures.

@chrisumbel
Copy link
Copy Markdown
Author

oh, I was going to address those and re-submit.

@nebhale
Copy link
Copy Markdown
Contributor

nebhale commented May 5, 2015

Just force push a commit to the same branch and it adds it to this PR directly. You don't need a separate PR for an update like that.

@cfdreddbot
Copy link
Copy Markdown

Hey chrisumbel!

Thanks for submitting this pull request!

All pull request authors must have a Contributor License Agreement (CLA) on-file with us. Please sign the appropriate CLA (individual or corporate).

When sending signed CLA please provide your github username in case of individual CLA or the list of github usernames that can make pull requests on behalf of your organization.

If you are confident that you're covered under a Corporate CLA, please make sure you've publicized your membership in the appropriate Github Org, per these instructions.

@nebhale nebhale reopened this May 5, 2015
@chrisumbel
Copy link
Copy Markdown
Author

Sounds good. I'll address it shortly.

@chrisumbel
Copy link
Copy Markdown
Author

Addressed!

212 files inspected, no offenses detected

@nebhale
Copy link
Copy Markdown
Contributor

nebhale commented May 5, 2015

@chrisumbel Can you please squash down the two commits into a single one and update the branch one last time?

@chrisumbel
Copy link
Copy Markdown
Author

Squashed. Think I did that right.

@nebhale
Copy link
Copy Markdown
Contributor

nebhale commented May 5, 2015

Sadly, no :) If you check out the "Commits" tab you'll see that you've now got 4 commits. Roughly, you're looking for:

$ git rebase --interactive origin/master
$ git push chrisumbel master -f

(assuming that origin is https://github.com/cloudfoundry/java-buildpack.git, and chrisumbel is https://github.com/chrisumbel/java-buildpack.git)

@chrisumbel chrisumbel closed this May 5, 2015
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

Successfully merging this pull request may close these issues.

3 participants