Bug#354026: java-package: generated package should provide java1-runtime
tags 354026 + wontfix thanks Hi Thanks for the proposal, but I believe that the underlying premise that java-runtime should be the only should be used no longer matches the current de-facto standard of the Java Team. If you still feel this policy proposal is valid, please right back and I will (re-)propose it to the Java Team. ~Niels signature.asc Description: OpenPGP digital signature
Bug#354026: java-package: generated package should provide java1-runtime
severity 354026 normal retitle 354026 Debian Java Policy needs to be updated regarding java*-runtime usage reassign 354026 java-common stop On Thu, Feb 23, 2006 at 01:36:40AM +0700, William S wrote: [...] The packages generated by the make-jpkg tool do not provide the virtual package java1-runtime. However, several packages depend on java1-runtime only (and not java-runtime or java2-runtime). [...] Thanks for your use of Debian and java-package as well as your time in filing this bug report. The Debian Java Packaging Project has had an ongoing discussion about this issue, most recently on debian-java[0]. Neither java1-runtime nor java2-runtime are relevant anymore; our current concensus is that java-runtime should be used, possibly in conjunction with a classpath-runtime virtual package to account for differences between non-free JREs and the free runtimes for Java(TM). [...] Some examples from my sarge packages list: jflex 1.3.5-7 libdom1-java 0.19990107-6 libjdepend-java 2.9-1 libjzlib-java 1.0.5-1.1 [...] There are currently 115 packages that depend on java1-runtime in unstable. Since sarge is frozen and released, package version in it are not subject to change. [...] I cannot find any information on the Debian Java FAQ, but the Debian policy for Java states that the preferred virtual package name is java1-runtime. The discussion on the mailing list (http://lists.debian.org/debian-java/2005/04/msg00032.html) said that it will soon be fixed in experimental but the newest version on the mirrors is 0.27 and the packages it generates still do not provide java1-runtime. [...] [0] - http://lists.debian.org/debian-java/2006/02/msg6.html Regards, -- Barry Hawkins All Things Computed site: www.alltc.com weblog: www.yepthatsme.com Registered Linux User #368650 signature.asc Description: Digital signature
Bug#354026: java-package: generated package should provide java1-runtime
Package: java-package Version: 0.27 Severity: important The packages generated by the make-jpkg tool do not provide the virtual package java1-runtime. However, several packages depend on java1-runtime only (and not java-runtime or java2-runtime). Some examples from my sarge packages list: jflex 1.3.5-7 libdom1-java 0.19990107-6 libjdepend-java 2.9-1 libjzlib-java 1.0.5-1.1 Actually, I think those are all... I cannot find any information on the Debian Java FAQ, but the Debian policy for Java states that the preferred virtual package name is java1-runtime. The discussion on the mailing list (http://lists.debian.org/debian-java/2005/04/msg00032.html) said that it will soon be fixed in experimental but the newest version on the mirrors is 0.27 and the packages it generates still do not provide java1-runtime. I suggest adding java1-runtime to the Provides: line in the shell scripts. That is, unless you consider the Java2 runtimes to be packages that do not implement the methods from Java 1.1 that have been deprecated in Java 2. Thanks. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.8-2-386 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages java-package depends on: ii coreutils 5.2.1-2 The GNU core utilities ii debhelper 4.2.32 helper programs for debian/rules ii fakeroot1.2.10 Gives a fake root environment ii unzip 5.52-1sarge3 De-archiver for .zip files -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
