Description of problem: I want to update rubygem-rest-client from 1.8.0 to 2.0.0. Because the 2.0.0 supports mime-types latest version 3.1, that is likely to be needed by Rails 5.0.0. I prepared the patch to update to 2.0.0. I am going to upload it here soon. I also like you guys to update "Monitoring on", monitor the upstream version up. https://admin.fedoraproject.org/pkgdb/package/rpms/rubygem-rest-client/
Created attachment 1179912 [details] Update to 2.0.0 Could you check my patch? # Dependency for rawhide. $ dnf repoquery --disablerepo=* --enablerepo=rawhide --whatrequires 'rubygem(rest-client)' rubygem-apipie-bindings-0:0.0.15-2.fc24.noarch rpm spec: ok gem spec: ok https://rubygems.org/gems/apipie-bindings/versions/0.0.15 rubygem-deltacloud-client-0:1.1.2-7.fc24.noarch rpm spec: ok gem spec: ok https://rubygems.org/gems/deltacloud-client/versions/1.1.2 rubygem-dynect_rest-0:0.4.3-6.fc20.noarch rpm spec: ok gem spec: ok https://rubygems.org/gems/dynect_rest/versions/0.4.3 rubygem-foreman_api-0:0.1.11-4.fc24.noarch rpm spec: ok gem spec: ok https://rubygems.org/gems/foreman_api/versions/0.1.11 rubygem-heroku-0:3.41.3-2.fc24.noarch rpm spec: ok gem spec: ok https://rubygems.org/gems/heroku/versions/3.41.3 rubygem-morph-cli-0:0.2.2-4.fc24.noarch rpm spec: ok gem spec: ok https://rubygems.org/gems/morph-cli/versions/0.2.2 rubygem-rbovirt-0:0.0.35-3.fc24.noarch rpm spec: ok gem spec: ok https://rubygems.org/gems/rbovirt/versions/0.0.35 vagrant-0:1.8.1-2.fc25.noarch rpm spec: ng asking. https://bugzilla.redhat.com/show_bug.cgi?id=1356650 $ dnf repoquery --disablerepo=* --enablerepo=rawhide --whatrequires 'rubygem-rest-client' rubygem-rest-client-doc-0:1.8.0-2.fc24.noarch ok $ dnf repoquery --disablerepo=* --enablerepo=rawhide --arch src --whatrequires 'rubygem(rest-client)' no target $ dnf repoquery --disablerepo=* --enablerepo=rawhide --arch src --whatrequires 'rubygem-rest-client' no target
(In reply to Jun Aruga from comment #0) > I also like you guys to update "Monitoring on", monitor the upstream version > up. > https://admin.fedoraproject.org/pkgdb/package/rpms/rubygem-rest-client/ The monitoring is enabled ... not sure why Anitya did not reported the updated version into BZ ...
(In reply to Vít Ondruch from comment #2) > (In reply to Jun Aruga from comment #0) > > I also like you guys to update "Monitoring on", monitor the upstream version > > up. > > https://admin.fedoraproject.org/pkgdb/package/rpms/rubygem-rest-client/ > > The monitoring is enabled ... not sure why Anitya did not reported the > updated version into BZ ... Okay, I got it. Humm.
(In reply to Vít Ondruch from comment #2) > (In reply to Jun Aruga from comment #0) > > I also like you guys to update "Monitoring on", monitor the upstream version > > up. > > https://admin.fedoraproject.org/pkgdb/package/rpms/rubygem-rest-client/ > > The monitoring is enabled ... not sure why Anitya did not reported the > updated version into BZ ... Vit I could see "Monitoring: No monitoring" from the URL. Is this the reason, isn't it? https://admin.fedoraproject.org/pkgdb/package/rpms/rubygem-rest-client/
(In reply to Jun Aruga from comment #4) That is actually combo of 3 options: 1. No monitoring 2. Bugs & builds 3. Bugs only where the middle is marked by arrow, i.e. it is active.
(In reply to Vít Ondruch from comment #5) > That is actually combo of 3 options: s/combo/radio button/
(In reply to Vít Ondruch from comment #5) > (In reply to Jun Aruga from comment #4) > That is actually combo of 3 options: > > 1. No monitoring > 2. Bugs & builds > 3. Bugs only > > where the middle is marked by arrow, i.e. it is active. Ah I got it.
Hi, could you check my patch? (In reply to Jun Aruga from comment #1) > Created attachment 1179912 [details] > Update to 2.0.0
Thank you. I applied the patch in Rawhide.