Bug#305219: java-package: plugin links are wrong because of wrong 'plugin_dir=' in postinst script
Package: java-package Version: 0.23 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I built a package from the latest Java 1.4.2_08 SDK from Sun. After installation I found, that the plugin-sylinks are dead. This is because the postinst script tells: plugin_dir=$j2se_base/plugin/$arch_dir but it should be plugin_dir=$j2se_base/jre/plugin/$arch_dir Regards, Daniel - -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (850, 'unstable'), (700, 'testing'), (110, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.8.15050330 Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) Versions of packages java-package depends on: ii coreutils 5.2.1-2The GNU core utilities ii debhelper 4.2.33 helper programs for debian/rules ii fakeroot 1.2.9 Gives a fake root environment - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCY/vEdg0kG0+YFBERAm6kAJ9HBo4T975052bpr0gWioX7V6UbuACfdaIn XJUb83thrXJi67+gnkGZ13k= =+FZ8 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#305219: java-package: plugin links are wrong because of wrong 'plugin_dir=' in postinst script
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Daniel Leidert wrote: [...] I built a package from the latest Java 1.4.2_08 SDK from Sun. After installation I found, that the plugin-sylinks are dead. This is because the postinst script tells: plugin_dir=$j2se_base/plugin/$arch_dir but it should be plugin_dir=$j2se_base/jre/plugin/$arch_dir Regards, Daniel [...] Daniel, thanks for the report. The current release in development has the fix in place already; this has been reported in bug #301806. Also, bugs like this should be set to normal; severity of a bug has very specific definition. Regards, - -- Barry Hawkins All Things Computed site: www.alltc.com weblog: www.yepthatsme.com Registered Linux User #368650 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD4DBQFCZAByHuKcDICy0QoRAuptAKCFiZOEePF2h58iSMIJcZ12rJXFEACY9Urg /2LJEcsYzp2XWJNOblbGxg== =3Owq -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#305219: java-package: plugin links are wrong because of wrong 'plugin_dir=' in postinst script
Am Montag, den 18.04.2005, 21:08 +0200 schrieb Daniel Leidert: Am Montag, den 18.04.2005, 14:46 -0400 schrieb Barry Hawkins: Daniel Leidert wrote: [...] I built a package from the latest Java 1.4.2_08 SDK from Sun. After installation I found, that the plugin-sylinks are dead. This is because the postinst script tells: plugin_dir=$j2se_base/plugin/$arch_dir but it should be plugin_dir=$j2se_base/jre/plugin/$arch_dir ^^^ Regards, Daniel [...] Daniel, thanks for the report. The current release in development has the fix in place already; this has been reported in bug #301806. O.k. I've found it now. Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#305219: java-package: plugin links are wrong because of wrong 'plugin_dir=' in postinst script
Am Montag, den 18.04.2005, 14:46 -0400 schrieb Barry Hawkins: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Daniel Leidert wrote: [...] I built a package from the latest Java 1.4.2_08 SDK from Sun. After installation I found, that the plugin-sylinks are dead. This is because the postinst script tells: plugin_dir=$j2se_base/plugin/$arch_dir but it should be plugin_dir=$j2se_base/jre/plugin/$arch_dir ^^^ Regards, Daniel [...] Daniel, thanks for the report. The current release in development has the fix in place already; this has been reported in bug #301806. I'm sorry, but the bug reported in #301806 is not related to the bug I've reported. #301806 tells something about the architecture specific part of the plugin-path. But now postinst script completely misses the right path. I'm sorry, if I missed the fact, that this new bug is already fixed. But this bug is not mentioned in the BTS. Also, bugs like this should be set to normal; severity of a bug has very specific definition. JFTP: I disagree. Crashing all browser Java plugins is IMHO an important bug, because this renders Java in browsers unusable. Regards, Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#305219: java-package: plugin links are wrong because of wrong 'plugin_dir=' in postinst script
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Daniel Leidert wrote: Am Montag, den 18.04.2005, 14:46 -0400 schrieb Barry Hawkins: [...] I'm sorry, but the bug reported in #301806 is not related to the bug I've reported. #301806 tells something about the architecture specific part of the plugin-path. But now postinst script completely misses the right path. I'm sorry, if I missed the fact, that this new bug is already fixed. But this bug is not mentioned in the BTS. [...] Prior to 0.23, only i386 users had plugin support; everyone had links that were i386-specific. In introducing arch-specific pathing, the JDK pathing for Sun and Blackdown appear to have been harmed. Sorry for not being more specific earlier, but this is what I mean by the fact that they are, indeed, related. I discovered your specific problem as part of fixing bug #301806; read the whole report and you will see the part about jre/ missing from the path. JFTP: I disagree. Crashing all browser Java plugins is IMHO an important bug, because this renders Java in browsers unusable. [...] Until 0.23, everyone but i386 users had unusable plugins. :-) Keep an eye out for 0.24, it will have the fix. Thanks for your use and support of Debian and java-package. Regards, - -- Barry Hawkins All Things Computed site: www.alltc.com weblog: www.yepthatsme.com Registered Linux User #368650 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCZAj2HuKcDICy0QoRAtBKAJ91oWbYpeehw41RvZsfR6PH4IYQ0QCeLbAZ NV4nj+EW8zggi6X5ZbG2jTg= =KtQh -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
