Comments
toshio
Works and fixes https://bugzilla.redhat.com/show_bug.cgi?id=1627963 for my Kensington Wireless Expert Mouse
Found an issue with the hawkey update. Seems that it depends on new features in the libsolv update but the dependencies aren't strict enough to pull it in. So if you install f24 and then update just hawkey the needed libsolv update is not pulled in. Output of running this in an F24 container that shows the issue: https://gist.github.com/abadger/94ef27df1039fe7cf1d0d82ea14b060a
Updating libsolv prior to updating hawkey (in that Dockerfile, hawkey is updated as a dep of python2-dnf) prevents the issue from happening.
Those rpmlint errors look pretty major. I'm revoking until I can figure out why alternatives is messing up so badly.
Oops, someone discovered this morning that the 0.13.1 release breaks python-sphinx: https://bugzilla.redhat.com/show_bug.cgi?id=1378071#c25 I'll update sphinx from 1.4.x to 1.5.x to fix that.
Since this is now using environment modules rather than alternatives, switching between packages can now be done without root permissions. Use the module swap command to switch between the two packages. For instance::
Switch to the python2 version
$ module swap python-sphinx/python2-sphinx
Switch back to the python3 version
$ module swap python-sphinx/python3-sphinx
Confirm 3.0.1.1-1.fc25 fixes the dependency issue. Was able to install and use this on FC25.
Python3 subpackage was broken by this update. It removed the line in the spec file that removed the execute bit on the files in the examples directory. I'm building a new update for f24 and rawhide to restore that line.
Note: This package is going to sit in testing for quite a while as this is a .0 release and upstream will be making new releases to fix bugs and polish the release. Very likely, this specific version will not make it out of the updates-testing repository.
This update has been unpushed
This update has been unpushed
Tested on RHEL-6.1 by running the python-kitchen unittests. Checked with the RHEL python-nose package both installed and uninstalled.
This update has been unpushed
Thanks for reporting. I'll get it blocked and removed from the repository. Miscommunication on my part lead me to branch it without having PyQt4 available in EPEL-5.
This update has been submitted for stable.
This update has been submitted for stable.
This update has been submitted for stable.
This update has been submitted for stable.
This update has been submitted for testing.
This update has been submitted for testing.
The rubygems subpackage built from this appears to break something important. Both vagrant and irb begin to fail once this version's rubygems package is installed:
$ dnf upgrade rubygems-3.2.33-152.fc35
$ irb
Ignoring json-2.3.0 because its extensions are not built. Try: gem pristine json --version 2.3.0 /usr/share/rubygems/rubygems/specification.rb:1406:in
rescue in block in activate_dependencies': Could not find 'reline' (>= 0.1.5) among 70 total gem(s) (Gem::MissingSpecError) Checked in 'GEM_PATH=/home/badger/.gem/ruby:/usr/share/gems:/usr/local/share/gems' at: /usr/share/gems/specifications/irb-1.3.5.gemspec, executegem envfor more information from /usr/share/rubygems/rubygems/specification.rb:1403:inblock in activate_dependencies' from /usr/share/rubygems/rubygems/specification.rb:1392:ineach' from /usr/share/rubygems/rubygems/specification.rb:1392:inactivate_dependencies' from /usr/share/rubygems/rubygems/specification.rb:1374:inactivate' from /usr/share/rubygems/rubygems.rb:299:inblock in activate_bin_path' from /usr/share/rubygems/rubygems.rb:298:insynchronize' from /usr/share/rubygems/rubygems.rb:298:inactivate_bin_path' from /usr/bin/irb:23:in<main>' /usr/share/rubygems/rubygems/dependency.rb:311:into_specs': Could not find 'reline' (>= 0.1.5) among 70 total gem(s) (Gem::MissingSpecError) Checked in 'GEM_PATH=/home/badger/.gem/ruby:/usr/share/gems:/usr/local/share/gems' , executegem envfor more information from /usr/share/rubygems/rubygems/specification.rb:1404:inblock in activate_dependencies' from /usr/share/rubygems/rubygems/specification.rb:1392:ineach' from /usr/share/rubygems/rubygems/specification.rb:1392:inactivate_dependencies' from /usr/share/rubygems/rubygems/specification.rb:1374:inactivate' from /usr/share/rubygems/rubygems.rb:299:inblock in activate_bin_path' from /usr/share/rubygems/rubygems.rb:298:insynchronize' from /usr/share/rubygems/rubygems.rb:298:inactivate_bin_path' from /usr/bin/irb:23:in<main>'Downgrading just the rubygems subpackage to rubygems-3.2.22-151.fc35 appears to fix the issue.
At first glance, the symptoms look like this: https://github.com/rubygems/rubygems/issues/5156 but since you reported that and a fix was merged upstream last year, this might be a red herring.