Bash completion works again.

Review request bouncycastle1.58 compat package: Anyone that can do a review?

There are two solutions to this.

  1. Update bouncycastle as proposed in the update, but also add a bouncycastle1.46 compat package package that provides /usr/share/java/bcprov-1.46,jar that provides the old version.

  2. Leave the bouncycastle package at the old 1.46 version and add the update as a councycastle1.56 compat package with versioned jars.

Option 1 gives a cleaner state going forward, but option 2 is more backward compatible since it does not change the meaning of the unversioned /usr/share/java/bcprov,jar.

Do you have any preferences?

The StandardSymbolsPS.otf font introduced in this update has broken charmaps. Since fontconfig prefers the .otf version over the .t1 version this is a regression that breaks applications.

See for details.

I am aware of the missing dependency. I filed a request in bugzilla to the maintainer - @bowlofeggs - for an EPEL 7 build a week ago: - but I haven't had any reply yet.

All architectures are pushed at the same time. It is not possible to request an update of only some of the architectures.

This issue should not exist anymore. All libraries used by "root-config --libs" are listed as requires in the root-core package. This has been the case since version 6.06.08-1 (September 2016). Are you for some reason installing old packages that are no longer available in EPEL? The current version in EPEL stable is 6.10.04-1 and in EPEL testing root-6.10.06-1. Which version are you installing?

$ root-config --libs
-L/usr/lib64/root -lCore -lImt -lRIO -lNet -lHist -lGraf -lGraf3d -lGpad -lTree -lTreePlayer -lRint -lPostscript -lMatrix -lPhysics -lMathCore -lThread -lMultiProc -pthread -lm -ldl -rdynamic

$ rpm -q --requires root-core | grep ^root
root-cling(x86-64) = 6.10.06-1.fc26
root-fonts = 6.10.06-1.fc26
root-graf(x86-64) = 6.10.06-1.fc26
root-graf-asimage(x86-64) = 6.10.06-1.fc26
root-graf-gpad(x86-64) = 6.10.06-1.fc26
root-graf-postscript(x86-64) = 6.10.06-1.fc26
root-graf3d(x86-64) = 6.10.06-1.fc26
root-hist(x86-64) = 6.10.06-1.fc26
root-icons = 6.10.06-1.fc26
root-io(x86-64) = 6.10.06-1.fc26
root-mathcore(x86-64) = 6.10.06-1.fc26
root-matrix(x86-64) = 6.10.06-1.fc26
root-multiproc(x86-64) = 6.10.06-1.fc26
root-net(x86-64) = 6.10.06-1.fc26
root-physics(x86-64) = 6.10.06-1.fc26
root-tree(x86-64) = 6.10.06-1.fc26
root-tree-player(x86-64) = 6.10.06-1.fc26

Issues with EPEL packages shoulf be reported in Redhat's bugzilla at When reporting new bugs choose the product "Fedora EPEL" for packages in the EPEL repository, the choose "root" as the component when reporting issues with the root package.

Hi Alejandro.

Thank you for your feedback and for investigating the issue and suggesting a solution. I have made a scratch build that implements your fix. Could you confirm that it restores functionality for you.


Hi Alejandro.

Thank you for your feedback and for investigating the issue and suggesting a solution. I have made a scratch build that implements your fix. Could you confirm that it restores functionality for you.


Bug 1467347 is fixed. Thanks for the quick fix!

BZ#1467347 /usr/bin/python3 /usr/share/java-utils/ pom_remove_parent causes traceback in F24

Hi Steve. Could you push this so that the broken deps warnings will stop:

nordugrid-arc has broken dependencies in the rawhide tree:
On x86_64:
       nordugrid-arc-arex-5.3.0-1.fc26.x86_64 requires python2-stomppy

This fixes the misspelled Provides/Obsoletes.

BZ#1435744 Misspelled Provides/Obsoletes

Minor typo - the summary for the python2 subpackage says python3:

$ dnf search stomppy
============================= N/S Matched: stomppy =============================
python2-stomppy.noarch : Python stomp client for messaging for python3
python3-stomppy.noarch : Python stomp client for messaging for python3

This update changes the name of the binary package, and hence breaks dependencies in other packages that declare a dependency on it. There is an attempt at a provides for the old name, but unfortunately it is misspelled so it is not useful for backward compatibility with the old name (see rhbz #1435744). In order to fix the broken dependency in my package I adapted it to require the new name of the binary package, which stopped the complaints about the broken deps in F27. Now after the freeze is lifted for F26 my update for F26 was pushed to stable too, but now this update is not pushed yet and the new name is not available in F26 so now I got notifications of broken dependencies in F26.


WaylandEnable=false in /etc/gdm/custom.conf works again.

The originally reported problem (that was fixed) reappeared again:

Thank you for the report. I forwarded it upstream and a fix was committed to upstream's git. I have applied the fix as an additional patch in xrootd-4.6.0-7.

Resolves broken upgrade path for iptables.