Processing commands for [email protected]:

> reassign 640576 src:scilab
Bug #640576 [src:scilab-celestlab] scilab-celestlab: FTBFS: Error: libjvm.so: 
cannot open shared object file: No such file or directory
Bug reassigned from package 'src:scilab-celestlab' to 'src:scilab'.
Bug No longer marked as found in versions scilab-celestlab/2.1.1-1-3.
> forcemerge 640576 639924
Bug#640576: scilab-celestlab: FTBFS: Error: libjvm.so: cannot open shared 
object file: No such file or directory
Bug#639924: FTBFS because of the openjdk move to multiarch
Bug#640573: FTBFS because of the openjdk move to multiarch
Bug#640578: FTBFS because of the openjdk move to multiarch
Bug#640579: FTBFS because of the openjdk move to multiarch
Bug#640584: FTBFS because of the openjdk move to multiarch
Bug#640616: FTBFS because of the openjdk move to multiarch
Bug#640617: FTBFS because of the openjdk move to multiarch
Bug#640632: scilab-jims: FTBFS: Error: libjvm.so: cannot open shared object 
file: No such file or directory
Bug#641764: Don't start scilab "Could not load JVM dynamic library (libjava)."
Forcibly Merged 639924 640573 640576 640578 640579 640584 640616 640617 640632 
641764.

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
640573: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640573
640617: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640617
640576: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640576
640579: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640579
640632: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640632
641764: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641764
640584: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640584
639924: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639924
640578: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640578
640616: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640616
Debian Bug Tracking System
Contact [email protected] with problems


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to