Comments

36 Comments

As you said, this is expected behavior. IOW there are independent versions of the packages you have mentioned with higher NVR then the subpackages of the same name provided by Ruby.

@robatino Thx for the bugreport. However, the 117 -> 118 update happens only if you have enabled updates-testing. Since this update obsoletes the -117 update, it should not happen to anybody anymore, unless they installed -117 by the bad luck.

@mattf or maybe s/Why you take/How you get/

@mattf Why you take the packages from Bodhi when they should be available in updates-testing repository? Anyway, simply don't take rubygem-json and rubygem-rdoc from Koji, since we have independent packages for rubygem-json and rubygem-rdoc of higher versions, which you appears to have installed already.

Actually I was wrong, it is not public :( sorry for the noise.

@gpotts the comment in BZ should be accessible now.

This is from the bug:

The rubygem-rkerberos folks (Satellite) have been aware this was going to happen for several releases now. The rationale for dropping it in general is that we can't actually provide the guarantees that keeping the version locked means. In particular, with this change, we introduce a new admin plugin and there's a good chance that will leak into the kadm5 interface (which is not stable, nor do we guarantee it as such).

BTW the older versions of the package are still available in Koji:

https://koji.fedoraproject.org/koji/packageinfo?packageID=17179

@gpotts: Sorry for breaking CentOS 7.4, but unfortunately, there is no way around it :/ See https://bugzilla.redhat.com/show_bug.cgi?id=1462982#c6 for more information.

@roca: I can't reproduce. Also, the change should not really be related. Do you mind oper BZ tickets with more details?

Thx for the ticket. Just FTR, please be aware that even if the conclusion is to retire rubygem-rmagick, it can be retired just in F28+, not in the stable branches, where this update landed as well.

Upstream is one thing and the package in Fedora is the other thing. I am pretty sure that Fedora package maintainer is active. Breaking others packages in stable Fedora is not justifiable.

This breaks rubygem-rmagick. The update should be coordinated with its maintainer.

This is going to break rubygem-rmagick, since it has hardcoded version dependency. The ABI check reports ABI breakage, so I would be careful about this update

This is going to break rubygem-rmagick, since it has hardcoded version dependency. The ABI check reports ABI breakage, so I would be careful about this update

Ok, one month in updates-testing and two positive responses. I pushed this into stable.

So lets see how this will work ... I did precisely 0 testing, so it is up to you guys. Autokarma is disabled ...

Can somebody test this scratch build of rubygem-fog-libvirt prior I commit it?

https://koji.fedoraproject.org/koji/taskinfo?taskID=18520272

This [1] was the real source of issues as far as I remember. I'll bump the fog-libvirt dependency to the latest ruby-libvirt and add this to this update, but I hope you guys will test it, because I don't have an energy to spend on testing this.

[1] https://github.com/vagrant-libvirt/vagrant-libvirt/issues/568#issuecomment-193448091