-
-
Save bendermIBM/252e4c14c7ff2ccf350c3b5a7c0f5139 to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# Foreman Status 07-30-2019 | |
Currently am trying to rebuild the foreman spec to use a correct version of puppet that will be compatible with Linux on Z. | |
Running into an issue where there are conflicting package requirements. Foreman requires (only a snippet) | |
``` | |
rubygem(activerecord-session_store) >= 1.1.0 is needed by foreman-1.22.0-1.fc30.noarch | |
rubygem(activerecord-session_store) < 2 is needed by foreman-1.22.0-1.fc30.noarch | |
rubygem(apipie-rails) >= 0.5.2 is needed by foreman-1.22.0-1.fc30.noarch | |
rubygem(apipie-rails) < 0.6.0 is needed by foreman-1.22.0-1.fc30.noarch | |
``` | |
`activerecord-session_store` requires `rubygem-rack >= 2.0.0` and `apipie-rails` requires a package called `sprockets-rails`. | |
``` | |
yum install rubygem-apipie-rails | |
Fedora Modular 30 - s390x 11 kB/s | 4.2 kB 00:00 | |
Fedora Modular 30 - s390x - Updates 23 kB/s | 4.1 kB 00:00 | |
Local Repo 3.0 MB/s | 3.0 kB 00:00 | |
Error: | |
Problem: package rubygem-rails-5.2.1-1.fc30.noarch requires rubygem(sprockets-rails) >= 2.0.0, but none of the providers can be installed | |
- package rubygem-apipie-rails-0.5.14-1.fc30.noarch requires rubygem(rails) >= 4.1, but none of the providers can be installed | |
- package rubygem-sprockets-rails-3.2.0-3.fc30.noarch requires rubygem(sprockets) >= 3.0.0, but none of the providers can be installed | |
- conflicting requests | |
- nothing provides (rubygem(rack) >= 1.0 with rubygem(rack) < 2) needed by rubygem-sprockets-3.0.0-1.fc30.noarch | |
(try to add '--skip-broken' to skip uninstallable packages) | |
``` | |
`sprockets-rails` here as we can see requires `rubygem-rack >= 1.0` so at this point we have a build conflict requiring the same package but with a MAJOR version difference. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment