Hide Forgot
Description of problem: Current httparty requires specific version of rubygem-crack (0.1.8). This gem was recently upgraded to version 0.3.1. This breaks the dependency chain and fails to build packages that depend on rubygem-httparty, like BoxGrinder. Version-Release number of selected component (if applicable): rubygem-httparty-0.7.4-1.fc16.noarch
This also affects Fedora 16 *stable* repository as rubygem-httparty was submitted also for F16 update. --> Processing Dependency: rubygem(crack) = 0.1.8 for package: rubygem-httparty-0.7.4-1.fc16.noarch ---> Package rubygem-crack.noarch 0:0.3.1-1.fc16 will be an update ---> Package spice-glib.x86_64 0:0.7.39-1.fc16 will be updated ---> Package spice-glib.x86_64 0:0.8-1.fc16 will be an update ---> Package spice-gtk.x86_64 0:0.7.39-1.fc16 will be updated ---> Package spice-gtk.x86_64 0:0.8-1.fc16 will be an update ---> Package spice-gtk-python.x86_64 0:0.7.39-1.fc16 will be updated ---> Package spice-gtk-python.x86_64 0:0.8-1.fc16 will be an update ---> Package spice-gtk3.x86_64 0:0.7.39-1.fc16 will be updated ---> Package spice-gtk3.x86_64 0:0.8-1.fc16 will be an update ---> Package spice-server.x86_64 0:0.10.0-1.fc16 will be updated ---> Package spice-server.x86_64 0:0.10.1-1.fc16 will be an update ---> Package telepathy-butterfly.noarch 0:0.5.15-3.fc16 will be updated ---> Package telepathy-butterfly.noarch 0:0.5.15-4.fc16 will be an update ---> Package usbredir.x86_64 0:0.3.1-1.fc16 will be updated ---> Package usbredir.x86_64 0:0.3.3-1.fc16 will be an update --> Finished Dependency Resolution Error: Package: rubygem-httparty-0.7.4-1.fc16.noarch (@fedora) Requires: rubygem(crack) = 0.1.8 Removing: rubygem-crack-0.1.8-1.fc15.noarch (@fedora) rubygem(crack) = 0.1.8 Updated By: rubygem-crack-0.3.1-1.fc16.noarch (updates) rubygem(crack) = 0.3.1 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest
It seems moving to a new httparty isn't an option right now, as it brings in new dependencies not yet in Fedora. I'll try to rebuild httparty with a the restriction on crack a little bit looser. If it doesn't work for your applications, please let me know.
Ok, after playing with the test set of httparty, it won't pass unless crack is exactly at 0.1.8, and even then, it had one failure on my Fedora 16 system. I'd like to move to a newer httpary (0.8.1) and that doesn't even use rubygem-crack. It needs multi_json and multi_xml. In looking at the boxgrinder-* gems on rubygems.org, I don't see anything that needs httparty. Which gem is it?
I have no idea how I missed the bad karma before I pushed, so I am extremely sorry for that. The best solution might be to downgrade crack in F16 and add an EPOCH, which is not great, but might be the shortest path to fixing the issue.
(In reply to comment #3) > Ok, after playing with the test set of httparty, it won't pass unless crack is > exactly at 0.1.8, and even then, it had one failure on my Fedora 16 system. > > I'd like to move to a newer httpary (0.8.1) and that doesn't even use > rubygem-crack. It needs multi_json and multi_xml. > > In looking at the boxgrinder-* gems on rubygems.org, I don't see anything that > needs httparty. Which gem is it? Michael, BoxGrinder doesn't require httparty directly, it is a indirect requirement via aws-sdk gem. Please note the httparty version requirement of aws-sdk itself: http://rubygems.org/gems/aws-sdk
(In reply to comment #4) > I have no idea how I missed the bad karma before I pushed, so I am extremely > sorry for that. The best solution might be to downgrade crack in F16 and add > an EPOCH, which is not great, but might be the shortest path to fixing the > issue. The karma was added after you pushed the package to stable - that's why. You missed the failing AutoQA test though. We're talking here about every Fedora version: F15, F16 and Rawhide. The push broke every release. --Marek
I'm adding an EPOCH and rebuilding for F15, F16 and Rawhide. I'd like to switch to an httparty that doesn't require crack in rawhide and that work has started.
rubygem-crack-0.1.8-4.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/rubygem-crack-0.1.8-4.fc15
rubygem-crack-0.1.8-4.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/rubygem-crack-0.1.8-4.fc16
Package rubygem-crack-0.1.8-4.fc15: * should fix your issue, * was pushed to the Fedora 15 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing rubygem-crack-0.1.8-4.fc15' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-1395/rubygem-crack-0.1.8-4.fc15 then log in and leave karma (feedback).
rubygem-crack-0.1.8-4.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
rubygem-crack-0.1.8-4.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.