Description of problem: This is what I saw on today's update: ... Cleanup : 1:java-1.7.0-openjdk-devel-1.7.0.25-2.3.10.10.fc19.x86_64 207/254 /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25-2.3.10.10.fc19.x86_64/bin/javac has not been configured as an alternative for javac /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25-2.3.10.10.fc19.x86_64 has not been configured as an alternative for java_sdk_openjdk /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25-2.3.10.10.fc19.x86_64 has not been configured as an alternative for java_sdk_1.7.0 Cleanup : 1:java-1.7.0-openjdk-1.7.0.25-2.3.10.10.fc19.x86_64 208/254 /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25-2.3.10.10.fc19.x86_64/jre/bin/java has not been configured as an alternative for java /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25-2.3.10.10.fc19.x86_64/jre has not been configured as an alternative for jre_openjdk /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25-2.3.10.10.fc19.x86_64/jre has not been configured as an alternative for jre_1.7.0 ... Cleanup : 1:java-1.7.0-openjdk-javadoc-1.7.0.25-2.3.10.10.fc19.noarch 231/254 /usr/share/javadoc/java-1.7.0-openjdk-1.7.0.25-2.3.10.10.fc19/api has not been configured as an alternative for javadocdir ... Version-Release number of selected component (if applicable): java-1.7.0-openjdk-1.7.0.25-2.3.12.3.fc19.x86_64 before java-1.7.0-openjdk-1:1.7.0.25-2.3.12.3.fc19.x86_64 after
It's a warning that's safe to ignore. It was a mistake in the old package (1.7.0.25-2.3.10.10.fc19) that has been fixed in the new one. Please reopen the bug if you see any unexpected side-effects.
Today, updating from 1:java-1.7.0-openjdk-devel-1.7.0.25-2.3.12.4.fc19.i686 1:java-1.7.0-openjdk-1.7.0.25-2.3.12.4.fc19.i686 to 1:java-1.7.0-openjdk-devel-1.7.0.60-2.4.2.0.fc19.i686 1:java-1.7.0-openjdk-1.7.0.60-2.4.2.0.fc19.i686 gives me again Cleanup : 1:java-1.7.0-openjdk-devel-1.7.0.25-2.3.12.4.fc19.i686 20/30 /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25-2.3.12.4.fc19.i386/bin/javac has not been configured as an alternative for javac /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25-2.3.12.4.fc19.i386 has not been configured as an alternative for java_sdk_openjdk /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25-2.3.12.4.fc19.i386 has not been configured as an alternative for java_sdk_1.7.0 ... Cleanup : 1:java-1.7.0-openjdk-1.7.0.25-2.3.12.4.fc19.i686 27/30 /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25-2.3.12.4.fc19.i386/jre/bin/java has not been configured as an alternative for java /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25-2.3.12.4.fc19.i386/jre has not been configured as an alternative for jre_openjdk /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25-2.3.12.4.fc19.i386/jre has not been configured as an alternative for jre_1.7.0 This seems to indicate that it has not been fixed.
Yes, I've seen it for the last F19 java update as well. Running transaction Updating : 1:java-1.7.0-openjdk-1.7.0.60-2.4.2.0.fc19.x86_64 1/4 Updating : 1:java-1.7.0-openjdk-devel-1.7.0.60-2.4.2.0.fc19.x86_64 2/4 Cleanup : 1:java-1.7.0-openjdk-devel-1.7.0.25-2.3.12.4.fc19.x86_64 3/4 /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25-2.3.12.4.fc19.x86_64/bin/javac has not been configured as an alternative for javac /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25-2.3.12.4.fc19.x86_64 has not been configured as an alternative for java_sdk_openjdk /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25-2.3.12.4.fc19.x86_64 has not been configured as an alternative for java_sdk_1.7.0 Cleanup : 1:java-1.7.0-openjdk-1.7.0.25-2.3.12.4.fc19.x86_64 4/4 /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25-2.3.12.4.fc19.x86_64/jre/bin/java has not been configured as an alternative for java /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25-2.3.12.4.fc19.x86_64/jre has not been configured as an alternative for jre_openjdk /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25-2.3.12.4.fc19.x86_64/jre has not been configured as an alternative for jre_1.7.0 Verifying : 1:java-1.7.0-openjdk-1.7.0.60-2.4.2.0.fc19.x86_64 1/4 Verifying : 1:java-1.7.0-openjdk-devel-1.7.0.60-2.4.2.0.fc19.x86_64 2/4 Verifying : 1:java-1.7.0-openjdk-devel-1.7.0.25-2.3.12.4.fc19.x86_64 3/4 Verifying : 1:java-1.7.0-openjdk-1.7.0.25-2.3.12.4.fc19.x86_64 4/4
Me three!
I just got this message on update too, but I don't see any other bad side-effects.
Hmmm, I just noticed the following CLUE. I'm on 64-bit (x86_64) but the update only came out for 32-bit (i386). I suspect that is part of the problem. Here is what I see in my repo: /fedora/updates/19/i386/drpms/java-1.7.0-openjdk-1.7.0.25-2.3.12.4.fc19_1.7.0.60-2.4.2.0.fc19.i686.drpm /fedora/updates/testing/19/SRPMS/java-1.7.0-openjdk-1.7.0.25-2.3.12.3.fc19.src.rpm /fedora/updates/testing/19/i386/java-1.7.0-openjdk-1.7.0.25-2.3.12.3.fc19.i686.rpm /fedora/updates/testing/19/i386/drpms/java-1.7.0-openjdk-1.7.0.25-2.3.10.3.fc19_1.7.0.25-2.3.12.3.fc19.i686.drpm /fedora/updates/testing/19/x86_64/java-1.7.0-openjdk-1.7.0.25-2.3.12.3.fc19.x86_64.rpm /fedora/updates/testing/19/x86_64/drpms/java-1.7.0-openjdk-1.7.0.25-2.3.10.3.fc19_1.7.0.25-2.3.12.3.fc19.x86_64.drpm Charlie B
Hmmm, weirder still. I just updated my local clone of the repos and now the 64-bit version of ... 2.3.12.4... is there in /fedora/updates/19. java-1.7.0-openjdk-1.7.0.25-2.3.12.4.fc19_1.7.0.60-2.4.2.0.fc19.x86_64.drpm Looking at my download logs there seems to have been some churn in the repos. I must have had a stale copy. Oh well.
See http://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Scriptlet_Ordering for the order in which scriptlets run. Here is what happens: 1. The new java-1.7.0-openjdk-devel package is installed. 2. %post of the *new* package runs. That script removes all of the configured alternatives of the *old* package. Look for the two instances of this comment: # Remove old alternatives 3. The old java-1.7.0-openjdk-devel package is removed. 4. The %postun script of the *old* package runs. That script removes all of the configured alternatives of the old package. But that has already been done in step 2, so it issues its "What you talking about, Willis?" complaint that is the subject of this bug. The warning is harmless, but it is also unnecessary. Don't remove alternatives in both places. Pick one.
What is a workaround for these error messages? I've been seeing them on openjdk updates for a while now.
I an can silent them. But it will just hide underlying issue. The underlying issue will disappear with eol of f18, in which the change of alternatives handling was introduced. In f21 the backward compatibility script will be removed, and the messages disappear. As omair told - those messages are harmless and mostly means that your openjdk have survived the alternatives change. If you really feel that those messages should be hidden, please reopen and I will reconsider. To Jerry James Unluckily its not true. Update of f18 to f19/f20 is supported. And so until eol of f18, the removing script must be kept.
(In reply to jiri vanek from comment #10) > I an can silent them. But it will just hide underlying issue. > The underlying issue will disappear with eol of f18, in which the change of > alternatives handling was introduced. But I'm running Fedora 19.
I'm confused. I did a clean install of Fedora-19 and ran into these issues. Are you (Jiri - comment #10) saying the error messages will go away now (F-19), or rather that they will persist until Fedora-21?
(In reply to Charles Butterfield from comment #12) > I'm confused. I did a clean install of Fedora-19 and ran into these issues. > Are you (Jiri - comment #10) saying the error messages will go away now > (F-19), or rather that they will persist until Fedora-21? Unluckily the second. Unless there will be strong pressure I have intention to keep them in till eol of f18.
(In reply to jiri vanek from comment #13) > Unluckily the second. Unless there will be strong pressure I have intention > to keep them in till eol of f18. To clarify, Fedora 18 should go EOL (end of life) in January 2014. That's not that far away ;)
It appears that this bug has successfully been ported to f20. Cleanup : 1:java-1.7.0-openjdk-headless-1.7.0.60-2.4.4.0.fc20.x86_ 12/20 /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.4.0.fc20.x86_64/jre/bin/java has not been configured as an alternative for java /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.4.0.fc20.x86_64/jre has not been configured as an alternative for jre_openjdk /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.4.0.fc20.x86_64/jre has not been configured as an alternative for jre_1.7.0 /usr/lib/jvm/jre-1.7.0-openjdk-1.7.0.60-2.4.4.0.fc20.x86_64 has not been configured as an alternative for jre_1.7.0_openjdk Cleanup : 1:java-1.7.0-openjdk-1.7.0.60-2.4.4.0.fc20.x86_64 13/20 Shall I file a new bz for f20 or can this bz be retargeted?
I had the same issues this evening updating a fresh F20 install. /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.4.0.fc20.x86_64/bin/javac has not been configured as an alternative for javac /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.4.0.fc20.x86_64 has not been configured as an alternative for java_sdk_openjdk /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.4.0.fc20.x86_64 has not been configured as an alternative for java_sdk_1.7.0 /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.4.0.fc20.x86_64/jre/bin/java has not been configured as an alternative for java /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.4.0.fc20.x86_64/jre has not been configured as an alternative for jre_openjdk /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.4.0.fc20.x86_64/jre has not been configured as an alternative for jre_1.7.0 /usr/lib/jvm/jre-1.7.0-openjdk-1.7.0.60-2.4.4.0.fc20.x86_64 has not been configured as an alternative for jre_1.7.0_openjdk
I created BZ 1057411 for this on F20 x86_64.
Here's the Fedora 20 bug: https://bugzilla.redhat.com/show_bug.cgi?id=1056264 This should be re-opened and fixed along with 1056264. It appears to be the same problem.
Just updated tonight with F20 and same issue. RPM Scriptlet: /usr/share/javadoc/java-1.7.0-openjdk-1.7.0.65-2.5.1.2.fc19/api has not been configured as an alternative for javadocdir 23:49:41 : RPM Scriptlet: /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.65-2.5.1.2.fc19.x86_64/bin/javac has not been configured as an alternative for javac 23:49:41 : YUM: /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.65-2.5.1.2.fc19.x86_64 has not been configured as an alternative for java_sdk_openjdk 23:49:41 : YUM: /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.65-2.5.1.2.fc19.x86_64 has not been configured as an alternative for java_sdk_1.7.0 23:49:43 : RPM Scriptlet: /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.65-2.5.1.2.fc19.x86_64/jre/bin/java has not been configured as an alternative for java 23:49:43 : YUM: /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.65-2.5.1.2.fc19.x86_64/jre has not been configured as an alternative for jre_openjdk 23:49:43 : YUM: /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.65-2.5.1.2.fc19.x86_64/jre has not been configured as an alternative for jre_1.7.0 23:49:43 : YUM: /usr/lib/jvm/jre-1.7.0-openjdk-1.7.0.65-2.5.1.2.fc19.x86_64 has not been configured as an alternative for jre_1.7.0_openjdk
I just realized that this was my F19 machine, not the F20 one. Sorry but it is still occurring.