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
use rhn-channel for libyml-devel #3194
Conversation
@cg2v this looks good, could you test with: rvm get branch /feature/gh_3191_rhel_yaml_support |
Does not seem to have worked RHEL6, RHN: Skipping installation of 'libffi-devel', in case you depend on FFI reinstall your ruby after following this instructions: /home/cg2v/.rvm/scripts/functions/requirements/redhat: line 203: requirements_rvm_pkg_configure: command not found Skipping installation of 'libffi-devel', in case you depend on FFI reinstall your ruby after following this instructions: Installing requirements for redhat. (the missing functions were why I was looking at github issues in the first place...) If I add the missing source to scripts/functions/requirements/redhat and set autolibs to read-fail, I get the "expected" |
re-enabling autolibs, and removing the redhat logic from commits 28908c4 and 4538416 gets farther. It fails to run rhn-channel -l, because rhn-channel is in /usr/sbin and must be run as root. It then tries to run rhn-channel -a -c with an empty channel (presumably because it did not detect the base channel). Something also swallows the 'Username:' prompt from rhn-channel -a Installing requirements for redhat. Password: |
Adding the __rvm_sudos still fails, and I can't figure out why. Here's update_system.log |
can you check if there is libffi-devel is also available in the optional repository? |
try with new: rvm get branch /feature/gh_3191_rhel_yaml_support |
looks good (both with and without rhel-x86_64-server-optional-6 already subscribed). something is still swallowing the username prompt when rhn-channel -a is run on rhel6, I have to know to type the username when the progress dots stop. (on rhel7 the username prompt does appear.) [cg2v@yawata-crossing ~]$ rvm requirements Skipping installation of 'libffi-devel', in case you depend on FFI reinstall your ruby after following this instructions: Installing requirements for redhat. |
now it should be better, is there a chance you could test it also on Centos as the behavior changed for it too. |
It no longer seems to run rhn-channel: Checking requirements for redhat. |
oh, this is confusing, please run this: rvm get branch /feature/gh_3191_rhel_yaml_support
rvm --trace requirements 2>&1 | tee big.log and gist |
https://gist.github.com/5468e902fb09c17859fa FYI, centos 6 worked fine |
…itories installation on centos
…g reporsitories installation on centos" This reverts commit 00f5cb5.
…initialization to it
did you had epel already installed in the centos box? - epel and libyaml-devel has to be removed to trigger installation of it again also pushed more updates |
The centos machine was a new minimal install (so minimal that I had to install which and tar before rvm would install). At least on this system, libyaml-devel is the centos 6 base repo. (I am using lxc for the centos, since I didn't want to put alot of effort into the install, and lxc doesn't support 7 yet) |
how about the other changes, did they improve things? |
yes, workflow is good there, still have the missing username problem. $ rvm requirements |
and this should do it, merged to master, you can test it with: rvm get head |
Works with master, and the prompting seems fixed too. There are some outstanding issues:
|
please open a new issue for the prompt, for RHSM please post instructions to #3207 |
Ruby supports embeded libyaml since 2.0.0, no need to require superflous and buggy instructions to add it. This can pose security risk for not updated libyaml - but it should be Ruby's responsibility to inform users about it! Fixes #2998 Update #3194 Deprecate/fix #3191 Deprecate/fix #3207 Partially fixes #3304
Ruby supports embedded libyaml since 2.0.0, no need to require superfluous and buggy instructions to add it. This can pose security risk for not updated libyaml - but it should be Ruby's responsibility to inform users about it! Fixes #2998 Update #3194 Deprecate/fix #3191 Deprecate/fix #3207 Partially fixes #3304
based on info from #3191
WIP