Blackdown-jdk-1.4.2.02 is not updating the $PATH and $ROOTPATH environment when being upgraded from Blackdown-jdk-1.4.2.01. I've found that out during 'emerge --update world'. Sys-libs/db failed to emerge because it could not find javac executable. After looking in the $PATH I've seen that blackdown-jdk was still version 1.4.2.01 instead of 1.4.2.02, which was the new one 'emerge --update world' had already emerged. After changing, manually, the $PATH and $ROOTPATH, 'emerge --update world' was able to continue. Reproducible: Always Steps to Reproduce: 1. emerge "=dev-java/blackdown-jdk-1.4.2.01-r2" 2. emerge blackdown-jdk (so it will upgrade from 1.4.2.01-r2 to 1.4.2.02) 3. Check the $PATH and $ROOTPATH (/etc/profile.env) Actual Results: The $PATH and $ROOTPATH was not updated. It keeps showing /opt/blackdown-jdk-1.4.2.01/bin and /opt/blackdown-jdk-1.4.2.01/jre/bin instead of the new one. Expected Results: The $PATH and $ROOTPATH should have been updated to include /opt/blackdown-jdk-1.4.2.02/bin and /opt/blackdown-jdk-1.4.2.02/jre/bin instead keep on using /opt/blackdown-1.4.2.01/bin and /opt/blackdown-jdk-1.4.2.01/jre/bin
> Blackdown-jdk-1.4.2.02 is not updating the $PATH and $ROOTPATH environment when > being upgraded from Blackdown-jdk-1.4.2.01. > I've found that out during 'emerge --update world'. Sys-libs/db failed to emerge > because it could not find javac executable. After looking in the $PATH I've seen > that blackdown-jdk was still version 1.4.2.01 instead of 1.4.2.02, which was the > new one 'emerge --update world' had already emerged. After changing, manually, > the $PATH and $ROOTPATH, 'emerge --update world' was able to continue. > > Reproducible: Always > Steps to Reproduce: > 1. emerge "=dev-java/blackdown-jdk-1.4.2.01-r2" > 2. emerge blackdown-jdk (so it will upgrade from 1.4.2.01-r2 to 1.4.2.02) > 3. Check the $PATH and $ROOTPATH (/etc/profile.env) > > Actual Results: > The $PATH and $ROOTPATH was not updated. It keeps showing > /opt/blackdown-jdk-1.4.2.01/bin and /opt/blackdown-jdk-1.4.2.01/jre/bin instead > of the new one. > > Expected Results: > The $PATH and $ROOTPATH should have been updated to include > /opt/blackdown-jdk-1.4.2.02/bin and /opt/blackdown-jdk-1.4.2.02/jre/bin instead > keep on using /opt/blackdown-1.4.2.01/bin and /opt/blackdown-jdk-1.4.2.01/jre/bin (In reply to comment #0) > Blackdown-jdk-1.4.2.02 is not updating the $PATH and $ROOTPATH environment when > being upgraded from Blackdown-jdk-1.4.2.01. > I've found that out during 'emerge --update world'. Sys-libs/db failed to emerge > because it could not find javac executable. After looking in the $PATH I've seen > that blackdown-jdk was still version 1.4.2.01 instead of 1.4.2.02, which was the > new one 'emerge --update world' had already emerged. After changing, manually, > the $PATH and $ROOTPATH, 'emerge --update world' was able to continue. > > Reproducible: Always > Steps to Reproduce: > 1. emerge "=dev-java/blackdown-jdk-1.4.2.01-r2" > 2. emerge blackdown-jdk (so it will upgrade from 1.4.2.01-r2 to 1.4.2.02) > 3. Check the $PATH and $ROOTPATH (/etc/profile.env) > > Actual Results: > The $PATH and $ROOTPATH was not updated. It keeps showing > /opt/blackdown-jdk-1.4.2.01/bin and /opt/blackdown-jdk-1.4.2.01/jre/bin instead > of the new one. > > Expected Results: > The $PATH and $ROOTPATH should have been updated to include > /opt/blackdown-jdk-1.4.2.02/bin and /opt/blackdown-jdk-1.4.2.02/jre/bin instead > keep on using /opt/blackdown-1.4.2.01/bin and /opt/blackdown-jdk-1.4.2.01/jre/bin Should run 'env-update && source /etc/profile' after the emerge, but it is not what happens. Sometimes the $PATH and $ROOTPATH is upgraded, but the environment still has the old $PATH. During the 'emerge --update world' that makes other packages which depends on JAVA executables to fail.(In reply to comment #0)
With the generation 2 setup, we don't need to change $PATH or $ROOTPATH any more as we install wrappers to /usr/bin.
