OpenSuSE has issued an advisory on March 30: http://lists.opensuse.org/opensuse-updates/2015-03/msg00092.html The issue is fixed upstream in 1.7. Mageia 4 and Mageia 5 are affected. Reproducible: Steps to Reproduce:
CC: (none) => fundawangWhiteboard: (none) => MGA5TOO, MGA4TOO
ruby-bundler is required by pcs as a BuildRequires. ruby-bundler is required by ruby-jeweler which is required by stompserver as a BuildRequires. If we can't maintain this package, we should remove it as well as ruby-jeweler, pcs, and stompserver. I've CC'd ennael (pcs maintainer) and solbu (stompserver maintainer) so they can help with this package if they would like to.
CC: (none) => cooker, ennael1
Things using bundler as a BuildRequires worry me...
As I was worried: http://pkgsubmit.mageia.org/autobuild/cauldron/x86_64/core/2015-04-28/pcs-0.9.123-4.mga5.src.rpm/build.0.20150428213808.log + make -O -j8 get_gems bundle package Fetching gem metadata from https://rubygems.org/.......... Resolving dependencies... Installing backports (3.4.0) Installing monkey-lib (0.5.4) Installing multi_json (1.8.4) Using rack (1.5.2) Installing rack-protection (1.5.2) Using rack-test (0.6.2) Installing rpam-ruby19 (1.2.1) Using tilt (1.4.1) Installing sinatra (1.4.4) Installing sinatra-contrib (1.4.2) Installing sinatra-sugar (0.5.1) Using bundler (1.3.5) Your bundle is complete! Use `bundle show [gemname]` to see where a bundled gem is installed. Updating files in vendor/cache * backports-3.4.0.gem * monkey-lib-0.5.4.gem * multi_json-1.8.4.gem * rack-1.5.2.gem * rack-protection-1.5.2.gem * rack-test-0.6.2.gem * rpam-ruby19-1.2.1.gem * tilt-1.4.1.gem * sinatra-1.4.4.gem * sinatra-contrib-1.4.2.gem * sinatra-sugar-0.5.1.gem
OK at least they don't end up in the built package.
Yes it would be very bad if this was being used to bundle things during builds. I don't know if Anne and Johnny still want to keep pcs and stompserver, but if they don't, are ruby-bundler and ruby-jeweler needed for any reason?
Dropped from Cauldron for now.
Version: Cauldron => 4Whiteboard: MGA5TOO, MGA4TOO => (none)
With only a couple of weeks remaining in Mageia 4's lifetime, we don't have time to fix this and test it. This package has been dropped and no longer exists in Mageia as of Mageia 5. Closing this as OLD.
Status: NEW => RESOLVEDResolution: (none) => OLD
Thomas, if you are building this for infra_5, this issue still needs to be addressed.
CC: (none) => tmb