https://bugzilla.redhat.com/show_bug.cgi?id=1443076 --- Comment #39 from jiri vanek <jvanek@xxxxxxxxxx> --- (In reply to Severin Gehwolf from comment #35) > (In reply to jiri vanek from comment #34) > > > - Some config files are not in conf: It's likely an upstream issue > > > as I see them in lib for an upstream build too. Please report a bug. > > > $ rpm -Vv java-9-openjdk-headless | grep ' c ' | grep lib/security > > > ......... c > > > /usr/lib/jvm/java-9-openjdk-9.0.0.178-1.fc26.x86_64/lib/security/blacklisted. > > > certs > > > ......... c > > > /usr/lib/jvm/java-9-openjdk-9.0.0.178-1.fc26.x86_64/lib/security/default. > > > policy > > > > > > > If the file is not in expected location, jdk will not find it > > I can move them to conf and link to original location, but as /etc is still > > in play, then I would rather not touch it. > > If you insists, I will move them, and link them. > > My point was that we should ask *upstream* whether or not this is > intentional. It's one of the odd balls. Everything else is in conf upstream > already. Thus, we should file a bug/ask upstream whether or not this should > be in conf upstream. That's all that's to do here. Thank you! explained: http://mail.openjdk.java.net/pipermail/build-dev/2017-August/019589.html > > > Config files in etc. I really wont to move them. However it will not be an > > easy task from point of view of multiple installs and copy-jdk-configs. > > I would like to not block this review on it. I have already started to work > > on c-j-c to support this, but there is still some longer way to go. > > OK. This should be fine. I'm glad to hear this will be worked on. > Suport for linked resources added: https://pagure.io/copy_jdk_configs/commits/master Now it will need hours and hours of testing. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx