Bug#477443: setting package to maven2, tagging 477443
# Automatically generated email from bts, devscripts version 2.10.26 # # maven2 (2.0.9-1) unstable; urgency=low # # * Added bash-completion file (Closes: #477443). package maven2 tags 477443 + pending ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Processed: setting package to maven2, tagging 477443
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.10.26 # # maven2 (2.0.9-1) unstable; urgency=low # # * Added bash-completion file (Closes: #477443). package maven2 Ignoring bugs not assigned to: maven2 tags 477443 + pending Bug#477443: maven2: bash completions for mvn Tags were: patch Tags added: pending End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Processing of gjdoc_0.7.9-1_amd64.changes
gjdoc_0.7.9-1_amd64.changes uploaded successfully to localhost along with the files: gjdoc_0.7.9-1.dsc gjdoc_0.7.9.orig.tar.gz gjdoc_0.7.9-1.diff.gz gjdoc_0.7.9-1_amd64.deb Greetings, Your Debian queue daemon ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
gjdoc_0.7.9-1_amd64.changes ACCEPTED
Accepted: gjdoc_0.7.9-1.diff.gz to pool/main/g/gjdoc/gjdoc_0.7.9-1.diff.gz gjdoc_0.7.9-1.dsc to pool/main/g/gjdoc/gjdoc_0.7.9-1.dsc gjdoc_0.7.9-1_amd64.deb to pool/main/g/gjdoc/gjdoc_0.7.9-1_amd64.deb gjdoc_0.7.9.orig.tar.gz to pool/main/g/gjdoc/gjdoc_0.7.9.orig.tar.gz Override entries for your package: gjdoc_0.7.9-1.dsc - source devel gjdoc_0.7.9-1_amd64.deb - optional devel Announcing to [EMAIL PROTECTED] Thank you for your contribution to Debian. ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#460398:
I have this bug also/too in 1.2.26-2. smime.p7s Description: S/MIME cryptographic signature ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Processing of libformula_0.1.14-1_amd64.changes
libformula_0.1.14-1_amd64.changes uploaded successfully to localhost along with the files: libformula_0.1.14-1.dsc libformula_0.1.14.orig.tar.gz libformula_0.1.14-1.diff.gz libformula-java_0.1.14-1_all.deb libformula-java-doc_0.1.14-1_all.deb Greetings, Your Debian queue daemon ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#477867: java-gnome: adjust build-dependency (gcj not built on alpha, arm, hppa and hurd-i386)
Package: java-gnome Version: 4.0.6-1 Severity: serious User: [EMAIL PROTECTED] Usertags: gcj-bd gij/gcj and java-gcj-compat are not available (anymore) on the following architectures: alpha, arm, hppa and hurd-i386. This package has been identified as a package which build-depends on gcj or java-gcj-compat-dev and builds at least one architecture dependent package, and is unbuildable in unstable. If this report is a false positive, please close it. All gcj related build dependencies have to restricted to these architectures on which a java or java compatible development kit / compiler is available, i.e. java-gcj-compat [!alpha !arm !hppa !hurd-i386] As a second step please consider changing the java-gcj-compat-dev b-d to default-jdk-builddep, making the package independent of a specific implementation and depend on the jdk, which is most suitable for this architecture. default-jdk-builddep will depend in addition on java-gcj-compat-dev, even if the default jdk is another one (to allow to compile byte-code to native code using dh_nativejava). A package build-depending on default-jdk-builddep should use as JAVA_HOME /usr/lib/jvm/default-java, or as path for the tools /usr/lib/jvm/default-java/bin. If the package builds just architecture dependent binaries which contain only byte-code compiled to native code (packages which often end with -gcj), then the architecture restrictions on the build dependency may not be needed (however the package cannot be built anymore on those archs). In this case make sure that the binary packages get removed on these architectures. Please check the influence of a package upload on ongoing transitions before an upload. ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#477846: axis: adjust build-dependency (gcj not built on alpha, arm, hppa and hurd-i386)
Package: axis Version: 1.4-3 Severity: serious User: [EMAIL PROTECTED] Usertags: gcj-bd gij/gcj and java-gcj-compat are not available (anymore) on the following architectures: alpha, arm, hppa and hurd-i386. This package has been identified as a package which build-depends on gcj or java-gcj-compat-dev and builds at least one architecture dependent package, and is unbuildable in unstable. If this report is a false positive, please close it. All gcj related build dependencies have to restricted to these architectures on which a java or java compatible development kit / compiler is available, i.e. java-gcj-compat [!alpha !arm !hppa !hurd-i386] As a second step please consider changing the java-gcj-compat-dev b-d to default-jdk-builddep, making the package independent of a specific implementation and depend on the jdk, which is most suitable for this architecture. default-jdk-builddep will depend in addition on java-gcj-compat-dev, even if the default jdk is another one (to allow to compile byte-code to native code using dh_nativejava). A package build-depending on default-jdk-builddep should use as JAVA_HOME /usr/lib/jvm/default-java, or as path for the tools /usr/lib/jvm/default-java/bin. If the package builds just architecture dependent binaries which contain only byte-code compiled to native code (packages which often end with -gcj), then the architecture restrictions on the build dependency may not be needed (however the package cannot be built anymore on those archs). In this case make sure that the binary packages get removed on these architectures. Please check the influence of a package upload on ongoing transitions before an upload. ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#477858: eclipse: adjust build-dependency (gcj not built on alpha, arm, hppa and hurd-i386)
Package: eclipse Version: 3.2.2-5 Severity: serious User: [EMAIL PROTECTED] Usertags: gcj-bd gij/gcj and java-gcj-compat are not available (anymore) on the following architectures: alpha, arm, hppa and hurd-i386. This package has been identified as a package which build-depends on gcj or java-gcj-compat-dev and builds at least one architecture dependent package, and is unbuildable in unstable. If this report is a false positive, please close it. All gcj related build dependencies have to restricted to these architectures on which a java or java compatible development kit / compiler is available, i.e. java-gcj-compat [!alpha !arm !hppa !hurd-i386] As a second step please consider changing the java-gcj-compat-dev b-d to default-jdk-builddep, making the package independent of a specific implementation and depend on the jdk, which is most suitable for this architecture. default-jdk-builddep will depend in addition on java-gcj-compat-dev, even if the default jdk is another one (to allow to compile byte-code to native code using dh_nativejava). A package build-depending on default-jdk-builddep should use as JAVA_HOME /usr/lib/jvm/default-java, or as path for the tools /usr/lib/jvm/default-java/bin. If the package builds just architecture dependent binaries which contain only byte-code compiled to native code (packages which often end with -gcj), then the architecture restrictions on the build dependency may not be needed (however the package cannot be built anymore on those archs). In this case make sure that the binary packages get removed on these architectures. Please check the influence of a package upload on ongoing transitions before an upload. ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#477859: glib-java: adjust build-dependency (gcj not built on alpha, arm, hppa and hurd-i386)
Package: glib-java Version: 0.4.2-9 Severity: serious User: [EMAIL PROTECTED] Usertags: gcj-bd gij/gcj and java-gcj-compat are not available (anymore) on the following architectures: alpha, arm, hppa and hurd-i386. This package has been identified as a package which build-depends on gcj or java-gcj-compat-dev and builds at least one architecture dependent package, and is unbuildable in unstable. If this report is a false positive, please close it. All gcj related build dependencies have to restricted to these architectures on which a java or java compatible development kit / compiler is available, i.e. java-gcj-compat [!alpha !arm !hppa !hurd-i386] As a second step please consider changing the java-gcj-compat-dev b-d to default-jdk-builddep, making the package independent of a specific implementation and depend on the jdk, which is most suitable for this architecture. default-jdk-builddep will depend in addition on java-gcj-compat-dev, even if the default jdk is another one (to allow to compile byte-code to native code using dh_nativejava). A package build-depending on default-jdk-builddep should use as JAVA_HOME /usr/lib/jvm/default-java, or as path for the tools /usr/lib/jvm/default-java/bin. If the package builds just architecture dependent binaries which contain only byte-code compiled to native code (packages which often end with -gcj), then the architecture restrictions on the build dependency may not be needed (however the package cannot be built anymore on those archs). In this case make sure that the binary packages get removed on these architectures. Please check the influence of a package upload on ongoing transitions before an upload. ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#477887: librepository: adjust build-dependency (gcj not built on alpha, arm, hppa and hurd-i386)
Package: librepository Version: 0.1.4-2 Severity: serious User: [EMAIL PROTECTED] Usertags: gcj-bd gij/gcj and java-gcj-compat are not available (anymore) on the following architectures: alpha, arm, hppa and hurd-i386. This package has been identified as a package which build-depends on gcj or java-gcj-compat-dev and builds at least one architecture dependent package, and is unbuildable in unstable. If this report is a false positive, please close it. All gcj related build dependencies have to restricted to these architectures on which a java or java compatible development kit / compiler is available, i.e. java-gcj-compat [!alpha !arm !hppa !hurd-i386] As a second step please consider changing the java-gcj-compat-dev b-d to default-jdk-builddep, making the package independent of a specific implementation and depend on the jdk, which is most suitable for this architecture. default-jdk-builddep will depend in addition on java-gcj-compat-dev, even if the default jdk is another one (to allow to compile byte-code to native code using dh_nativejava). A package build-depending on default-jdk-builddep should use as JAVA_HOME /usr/lib/jvm/default-java, or as path for the tools /usr/lib/jvm/default-java/bin. If the package builds just architecture dependent binaries which contain only byte-code compiled to native code (packages which often end with -gcj), then the architecture restrictions on the build dependency may not be needed (however the package cannot be built anymore on those archs). In this case make sure that the binary packages get removed on these architectures. Please check the influence of a package upload on ongoing transitions before an upload. ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#477860: eclipse-cdt: adjust build-dependency (gcj not built on alpha, arm, hppa and hurd-i386)
Package: eclipse-cdt Version: 3.1.2-1 Severity: serious User: [EMAIL PROTECTED] Usertags: gcj-bd gij/gcj and java-gcj-compat are not available (anymore) on the following architectures: alpha, arm, hppa and hurd-i386. This package has been identified as a package which build-depends on gcj or java-gcj-compat-dev and builds at least one architecture dependent package, and is unbuildable in unstable. If this report is a false positive, please close it. All gcj related build dependencies have to restricted to these architectures on which a java or java compatible development kit / compiler is available, i.e. java-gcj-compat [!alpha !arm !hppa !hurd-i386] As a second step please consider changing the java-gcj-compat-dev b-d to default-jdk-builddep, making the package independent of a specific implementation and depend on the jdk, which is most suitable for this architecture. default-jdk-builddep will depend in addition on java-gcj-compat-dev, even if the default jdk is another one (to allow to compile byte-code to native code using dh_nativejava). A package build-depending on default-jdk-builddep should use as JAVA_HOME /usr/lib/jvm/default-java, or as path for the tools /usr/lib/jvm/default-java/bin. If the package builds just architecture dependent binaries which contain only byte-code compiled to native code (packages which often end with -gcj), then the architecture restrictions on the build dependency may not be needed (however the package cannot be built anymore on those archs). In this case make sure that the binary packages get removed on these architectures. Please check the influence of a package upload on ongoing transitions before an upload. ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#477889: libswirl-java: adjust build-dependency (gcj not built on alpha, arm, hppa and hurd-i386)
Package: libswirl-java Version: 1.0.13-2 Severity: serious User: [EMAIL PROTECTED] Usertags: gcj-bd gij/gcj and java-gcj-compat are not available (anymore) on the following architectures: alpha, arm, hppa and hurd-i386. This package has been identified as a package which build-depends on gcj or java-gcj-compat-dev and builds at least one architecture dependent package, and is unbuildable in unstable. If this report is a false positive, please close it. All gcj related build dependencies have to restricted to these architectures on which a java or java compatible development kit / compiler is available, i.e. java-gcj-compat [!alpha !arm !hppa !hurd-i386] As a second step please consider changing the java-gcj-compat-dev b-d to default-jdk-builddep, making the package independent of a specific implementation and depend on the jdk, which is most suitable for this architecture. default-jdk-builddep will depend in addition on java-gcj-compat-dev, even if the default jdk is another one (to allow to compile byte-code to native code using dh_nativejava). A package build-depending on default-jdk-builddep should use as JAVA_HOME /usr/lib/jvm/default-java, or as path for the tools /usr/lib/jvm/default-java/bin. If the package builds just architecture dependent binaries which contain only byte-code compiled to native code (packages which often end with -gcj), then the architecture restrictions on the build dependency may not be needed (however the package cannot be built anymore on those archs). In this case make sure that the binary packages get removed on these architectures. Please check the influence of a package upload on ongoing transitions before an upload. ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#477849: bsh: adjust build-dependency (gcj not built on alpha, arm, hppa and hurd-i386)
Package: bsh Version: 2.0b4-7 Severity: serious User: [EMAIL PROTECTED] Usertags: gcj-bd gij/gcj and java-gcj-compat are not available (anymore) on the following architectures: alpha, arm, hppa and hurd-i386. This package has been identified as a package which build-depends on gcj or java-gcj-compat-dev and builds at least one architecture dependent package, and is unbuildable in unstable. If this report is a false positive, please close it. All gcj related build dependencies have to restricted to these architectures on which a java or java compatible development kit / compiler is available, i.e. java-gcj-compat [!alpha !arm !hppa !hurd-i386] As a second step please consider changing the java-gcj-compat-dev b-d to default-jdk-builddep, making the package independent of a specific implementation and depend on the jdk, which is most suitable for this architecture. default-jdk-builddep will depend in addition on java-gcj-compat-dev, even if the default jdk is another one (to allow to compile byte-code to native code using dh_nativejava). A package build-depending on default-jdk-builddep should use as JAVA_HOME /usr/lib/jvm/default-java, or as path for the tools /usr/lib/jvm/default-java/bin. If the package builds just architecture dependent binaries which contain only byte-code compiled to native code (packages which often end with -gcj), then the architecture restrictions on the build dependency may not be needed (however the package cannot be built anymore on those archs). In this case make sure that the binary packages get removed on these architectures. Please check the influence of a package upload on ongoing transitions before an upload. ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#477891: libtritonus-java: adjust build-dependency (gcj not built on alpha, arm, hppa and hurd-i386)
Package: libtritonus-java Version: 20070428-6 Severity: serious User: [EMAIL PROTECTED] Usertags: gcj-bd gij/gcj and java-gcj-compat are not available (anymore) on the following architectures: alpha, arm, hppa and hurd-i386. This package has been identified as a package which build-depends on gcj or java-gcj-compat-dev and builds at least one architecture dependent package, and is unbuildable in unstable. If this report is a false positive, please close it. All gcj related build dependencies have to restricted to these architectures on which a java or java compatible development kit / compiler is available, i.e. java-gcj-compat [!alpha !arm !hppa !hurd-i386] As a second step please consider changing the java-gcj-compat-dev b-d to default-jdk-builddep, making the package independent of a specific implementation and depend on the jdk, which is most suitable for this architecture. default-jdk-builddep will depend in addition on java-gcj-compat-dev, even if the default jdk is another one (to allow to compile byte-code to native code using dh_nativejava). A package build-depending on default-jdk-builddep should use as JAVA_HOME /usr/lib/jvm/default-java, or as path for the tools /usr/lib/jvm/default-java/bin. If the package builds just architecture dependent binaries which contain only byte-code compiled to native code (packages which often end with -gcj), then the architecture restrictions on the build dependency may not be needed (however the package cannot be built anymore on those archs). In this case make sure that the binary packages get removed on these architectures. Please check the influence of a package upload on ongoing transitions before an upload. ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#477850: cairo-java: adjust build-dependency (gcj not built on alpha, arm, hppa and hurd-i386)
Package: cairo-java Version: 1.0.8-8 Severity: serious User: [EMAIL PROTECTED] Usertags: gcj-bd gij/gcj and java-gcj-compat are not available (anymore) on the following architectures: alpha, arm, hppa and hurd-i386. This package has been identified as a package which build-depends on gcj or java-gcj-compat-dev and builds at least one architecture dependent package, and is unbuildable in unstable. If this report is a false positive, please close it. All gcj related build dependencies have to restricted to these architectures on which a java or java compatible development kit / compiler is available, i.e. java-gcj-compat [!alpha !arm !hppa !hurd-i386] As a second step please consider changing the java-gcj-compat-dev b-d to default-jdk-builddep, making the package independent of a specific implementation and depend on the jdk, which is most suitable for this architecture. default-jdk-builddep will depend in addition on java-gcj-compat-dev, even if the default jdk is another one (to allow to compile byte-code to native code using dh_nativejava). A package build-depending on default-jdk-builddep should use as JAVA_HOME /usr/lib/jvm/default-java, or as path for the tools /usr/lib/jvm/default-java/bin. If the package builds just architecture dependent binaries which contain only byte-code compiled to native code (packages which often end with -gcj), then the architecture restrictions on the build dependency may not be needed (however the package cannot be built anymore on those archs). In this case make sure that the binary packages get removed on these architectures. Please check the influence of a package upload on ongoing transitions before an upload. ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#477903: sacjava: adjust build-dependency (gcj not built on alpha, arm, hppa and hurd-i386)
Package: sacjava Version: 1.3-1 Severity: serious User: [EMAIL PROTECTED] Usertags: gcj-bd gij/gcj and java-gcj-compat are not available (anymore) on the following architectures: alpha, arm, hppa and hurd-i386. This package has been identified as a package which build-depends on gcj or java-gcj-compat-dev and builds at least one architecture dependent package, and is unbuildable in unstable. If this report is a false positive, please close it. All gcj related build dependencies have to restricted to these architectures on which a java or java compatible development kit / compiler is available, i.e. java-gcj-compat [!alpha !arm !hppa !hurd-i386] As a second step please consider changing the java-gcj-compat-dev b-d to default-jdk-builddep, making the package independent of a specific implementation and depend on the jdk, which is most suitable for this architecture. default-jdk-builddep will depend in addition on java-gcj-compat-dev, even if the default jdk is another one (to allow to compile byte-code to native code using dh_nativejava). A package build-depending on default-jdk-builddep should use as JAVA_HOME /usr/lib/jvm/default-java, or as path for the tools /usr/lib/jvm/default-java/bin. If the package builds just architecture dependent binaries which contain only byte-code compiled to native code (packages which often end with -gcj), then the architecture restrictions on the build dependency may not be needed (however the package cannot be built anymore on those archs). In this case make sure that the binary packages get removed on these architectures. Please check the influence of a package upload on ongoing transitions before an upload. ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#477873: libgtk-java: adjust build-dependency (gcj not built on alpha, arm, hppa and hurd-i386)
Package: libgtk-java Version: 2.10.2-6 Severity: serious User: [EMAIL PROTECTED] Usertags: gcj-bd gij/gcj and java-gcj-compat are not available (anymore) on the following architectures: alpha, arm, hppa and hurd-i386. This package has been identified as a package which build-depends on gcj or java-gcj-compat-dev and builds at least one architecture dependent package, and is unbuildable in unstable. If this report is a false positive, please close it. All gcj related build dependencies have to restricted to these architectures on which a java or java compatible development kit / compiler is available, i.e. java-gcj-compat [!alpha !arm !hppa !hurd-i386] As a second step please consider changing the java-gcj-compat-dev b-d to default-jdk-builddep, making the package independent of a specific implementation and depend on the jdk, which is most suitable for this architecture. default-jdk-builddep will depend in addition on java-gcj-compat-dev, even if the default jdk is another one (to allow to compile byte-code to native code using dh_nativejava). A package build-depending on default-jdk-builddep should use as JAVA_HOME /usr/lib/jvm/default-java, or as path for the tools /usr/lib/jvm/default-java/bin. If the package builds just architecture dependent binaries which contain only byte-code compiled to native code (packages which often end with -gcj), then the architecture restrictions on the build dependency may not be needed (however the package cannot be built anymore on those archs). In this case make sure that the binary packages get removed on these architectures. Please check the influence of a package upload on ongoing transitions before an upload. ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#477852: classpath: adjust build-dependency (gcj not built on alpha, arm, hppa and hurd-i386)
Package: classpath Version: 2:0.97-1 Severity: serious User: [EMAIL PROTECTED] Usertags: gcj-bd gij/gcj and java-gcj-compat are not available (anymore) on the following architectures: alpha, arm, hppa and hurd-i386. This package has been identified as a package which build-depends on gcj or java-gcj-compat-dev and builds at least one architecture dependent package, and is unbuildable in unstable. If this report is a false positive, please close it. All gcj related build dependencies have to restricted to these architectures on which a java or java compatible development kit / compiler is available, i.e. java-gcj-compat [!alpha !arm !hppa !hurd-i386] As a second step please consider changing the java-gcj-compat-dev b-d to default-jdk-builddep, making the package independent of a specific implementation and depend on the jdk, which is most suitable for this architecture. default-jdk-builddep will depend in addition on java-gcj-compat-dev, even if the default jdk is another one (to allow to compile byte-code to native code using dh_nativejava). A package build-depending on default-jdk-builddep should use as JAVA_HOME /usr/lib/jvm/default-java, or as path for the tools /usr/lib/jvm/default-java/bin. If the package builds just architecture dependent binaries which contain only byte-code compiled to native code (packages which often end with -gcj), then the architecture restrictions on the build dependency may not be needed (however the package cannot be built anymore on those archs). In this case make sure that the binary packages get removed on these architectures. Please check the influence of a package upload on ongoing transitions before an upload. ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#477894: libvte-java: adjust build-dependency (gcj not built on alpha, arm, hppa and hurd-i386)
Package: libvte-java Version: 0.12.3-4 Severity: serious User: [EMAIL PROTECTED] Usertags: gcj-bd gij/gcj and java-gcj-compat are not available (anymore) on the following architectures: alpha, arm, hppa and hurd-i386. This package has been identified as a package which build-depends on gcj or java-gcj-compat-dev and builds at least one architecture dependent package, and is unbuildable in unstable. If this report is a false positive, please close it. All gcj related build dependencies have to restricted to these architectures on which a java or java compatible development kit / compiler is available, i.e. java-gcj-compat [!alpha !arm !hppa !hurd-i386] As a second step please consider changing the java-gcj-compat-dev b-d to default-jdk-builddep, making the package independent of a specific implementation and depend on the jdk, which is most suitable for this architecture. default-jdk-builddep will depend in addition on java-gcj-compat-dev, even if the default jdk is another one (to allow to compile byte-code to native code using dh_nativejava). A package build-depending on default-jdk-builddep should use as JAVA_HOME /usr/lib/jvm/default-java, or as path for the tools /usr/lib/jvm/default-java/bin. If the package builds just architecture dependent binaries which contain only byte-code compiled to native code (packages which often end with -gcj), then the architecture restrictions on the build dependency may not be needed (however the package cannot be built anymore on those archs). In this case make sure that the binary packages get removed on these architectures. Please check the influence of a package upload on ongoing transitions before an upload. ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#477881: libmx4j-java: adjust build-dependency (gcj not built on alpha, arm, hppa and hurd-i386)
Package: libmx4j-java Version: 3.0.2-1 Severity: serious User: [EMAIL PROTECTED] Usertags: gcj-bd gij/gcj and java-gcj-compat are not available (anymore) on the following architectures: alpha, arm, hppa and hurd-i386. This package has been identified as a package which build-depends on gcj or java-gcj-compat-dev and builds at least one architecture dependent package, and is unbuildable in unstable. If this report is a false positive, please close it. All gcj related build dependencies have to restricted to these architectures on which a java or java compatible development kit / compiler is available, i.e. java-gcj-compat [!alpha !arm !hppa !hurd-i386] As a second step please consider changing the java-gcj-compat-dev b-d to default-jdk-builddep, making the package independent of a specific implementation and depend on the jdk, which is most suitable for this architecture. default-jdk-builddep will depend in addition on java-gcj-compat-dev, even if the default jdk is another one (to allow to compile byte-code to native code using dh_nativejava). A package build-depending on default-jdk-builddep should use as JAVA_HOME /usr/lib/jvm/default-java, or as path for the tools /usr/lib/jvm/default-java/bin. If the package builds just architecture dependent binaries which contain only byte-code compiled to native code (packages which often end with -gcj), then the architecture restrictions on the build dependency may not be needed (however the package cannot be built anymore on those archs). In this case make sure that the binary packages get removed on these architectures. Please check the influence of a package upload on ongoing transitions before an upload. ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#477882: libgconf-java: adjust build-dependency (gcj not built on alpha, arm, hppa and hurd-i386)
Package: libgconf-java Version: 2.12.6-4 Severity: serious User: [EMAIL PROTECTED] Usertags: gcj-bd gij/gcj and java-gcj-compat are not available (anymore) on the following architectures: alpha, arm, hppa and hurd-i386. This package has been identified as a package which build-depends on gcj or java-gcj-compat-dev and builds at least one architecture dependent package, and is unbuildable in unstable. If this report is a false positive, please close it. All gcj related build dependencies have to restricted to these architectures on which a java or java compatible development kit / compiler is available, i.e. java-gcj-compat [!alpha !arm !hppa !hurd-i386] As a second step please consider changing the java-gcj-compat-dev b-d to default-jdk-builddep, making the package independent of a specific implementation and depend on the jdk, which is most suitable for this architecture. default-jdk-builddep will depend in addition on java-gcj-compat-dev, even if the default jdk is another one (to allow to compile byte-code to native code using dh_nativejava). A package build-depending on default-jdk-builddep should use as JAVA_HOME /usr/lib/jvm/default-java, or as path for the tools /usr/lib/jvm/default-java/bin. If the package builds just architecture dependent binaries which contain only byte-code compiled to native code (packages which often end with -gcj), then the architecture restrictions on the build dependency may not be needed (however the package cannot be built anymore on those archs). In this case make sure that the binary packages get removed on these architectures. Please check the influence of a package upload on ongoing transitions before an upload. ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#477883: libjaxp1.2-java: adjust build-dependency (gcj not built on alpha, arm, hppa and hurd-i386)
Package: libjaxp1.2-java Version: 1.2.01-2 Severity: serious User: [EMAIL PROTECTED] Usertags: gcj-bd gij/gcj and java-gcj-compat are not available (anymore) on the following architectures: alpha, arm, hppa and hurd-i386. This package has been identified as a package which build-depends on gcj or java-gcj-compat-dev and builds at least one architecture dependent package, and is unbuildable in unstable. If this report is a false positive, please close it. All gcj related build dependencies have to restricted to these architectures on which a java or java compatible development kit / compiler is available, i.e. java-gcj-compat [!alpha !arm !hppa !hurd-i386] As a second step please consider changing the java-gcj-compat-dev b-d to default-jdk-builddep, making the package independent of a specific implementation and depend on the jdk, which is most suitable for this architecture. default-jdk-builddep will depend in addition on java-gcj-compat-dev, even if the default jdk is another one (to allow to compile byte-code to native code using dh_nativejava). A package build-depending on default-jdk-builddep should use as JAVA_HOME /usr/lib/jvm/default-java, or as path for the tools /usr/lib/jvm/default-java/bin. If the package builds just architecture dependent binaries which contain only byte-code compiled to native code (packages which often end with -gcj), then the architecture restrictions on the build dependency may not be needed (however the package cannot be built anymore on those archs). In this case make sure that the binary packages get removed on these architectures. Please check the influence of a package upload on ongoing transitions before an upload. ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#477853: commons-daemon: adjust build-dependency (gcj not built on alpha, arm, hppa and hurd-i386)
Package: commons-daemon Version: 1.0.2~svn20061127-6 Severity: serious User: [EMAIL PROTECTED] Usertags: gcj-bd gij/gcj and java-gcj-compat are not available (anymore) on the following architectures: alpha, arm, hppa and hurd-i386. This package has been identified as a package which build-depends on gcj or java-gcj-compat-dev and builds at least one architecture dependent package, and is unbuildable in unstable. If this report is a false positive, please close it. All gcj related build dependencies have to restricted to these architectures on which a java or java compatible development kit / compiler is available, i.e. java-gcj-compat [!alpha !arm !hppa !hurd-i386] As a second step please consider changing the java-gcj-compat-dev b-d to default-jdk-builddep, making the package independent of a specific implementation and depend on the jdk, which is most suitable for this architecture. default-jdk-builddep will depend in addition on java-gcj-compat-dev, even if the default jdk is another one (to allow to compile byte-code to native code using dh_nativejava). A package build-depending on default-jdk-builddep should use as JAVA_HOME /usr/lib/jvm/default-java, or as path for the tools /usr/lib/jvm/default-java/bin. If the package builds just architecture dependent binaries which contain only byte-code compiled to native code (packages which often end with -gcj), then the architecture restrictions on the build dependency may not be needed (however the package cannot be built anymore on those archs). In this case make sure that the binary packages get removed on these architectures. Please check the influence of a package upload on ongoing transitions before an upload. ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#477874: libgui-commands-java: adjust build-dependency (gcj not built on alpha, arm, hppa and hurd-i386)
Package: libgui-commands-java Version: 1.1.43-2 Severity: serious User: [EMAIL PROTECTED] Usertags: gcj-bd gij/gcj and java-gcj-compat are not available (anymore) on the following architectures: alpha, arm, hppa and hurd-i386. This package has been identified as a package which build-depends on gcj or java-gcj-compat-dev and builds at least one architecture dependent package, and is unbuildable in unstable. If this report is a false positive, please close it. All gcj related build dependencies have to restricted to these architectures on which a java or java compatible development kit / compiler is available, i.e. java-gcj-compat [!alpha !arm !hppa !hurd-i386] As a second step please consider changing the java-gcj-compat-dev b-d to default-jdk-builddep, making the package independent of a specific implementation and depend on the jdk, which is most suitable for this architecture. default-jdk-builddep will depend in addition on java-gcj-compat-dev, even if the default jdk is another one (to allow to compile byte-code to native code using dh_nativejava). A package build-depending on default-jdk-builddep should use as JAVA_HOME /usr/lib/jvm/default-java, or as path for the tools /usr/lib/jvm/default-java/bin. If the package builds just architecture dependent binaries which contain only byte-code compiled to native code (packages which often end with -gcj), then the architecture restrictions on the build dependency may not be needed (however the package cannot be built anymore on those archs). In this case make sure that the binary packages get removed on these architectures. Please check the influence of a package upload on ongoing transitions before an upload. ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#477844: ant: adjust build-dependency (gcj not built on alpha, arm, hppa and hurd-i386)
Package: ant Version: 1.7.0-5 Severity: serious User: [EMAIL PROTECTED] Usertags: gcj-bd gij/gcj and java-gcj-compat are not available (anymore) on the following architectures: alpha, arm, hppa and hurd-i386. This package has been identified as a package which build-depends on gcj or java-gcj-compat-dev and builds at least one architecture dependent package, and is unbuildable in unstable. If this report is a false positive, please close it. All gcj related build dependencies have to restricted to these architectures on which a java or java compatible development kit / compiler is available, i.e. java-gcj-compat [!alpha !arm !hppa !hurd-i386] As a second step please consider changing the java-gcj-compat-dev b-d to default-jdk-builddep, making the package independent of a specific implementation and depend on the jdk, which is most suitable for this architecture. default-jdk-builddep will depend in addition on java-gcj-compat-dev, even if the default jdk is another one (to allow to compile byte-code to native code using dh_nativejava). A package build-depending on default-jdk-builddep should use as JAVA_HOME /usr/lib/jvm/default-java, or as path for the tools /usr/lib/jvm/default-java/bin. If the package builds just architecture dependent binaries which contain only byte-code compiled to native code (packages which often end with -gcj), then the architecture restrictions on the build dependency may not be needed (however the package cannot be built anymore on those archs). In this case make sure that the binary packages get removed on these architectures. Please check the influence of a package upload on ongoing transitions before an upload. ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#477869: grinvin: adjust build-dependency (gcj not built on alpha, arm, hppa and hurd-i386)
Package: grinvin Version: 1.0.3.dfsg.1-1 Severity: serious User: [EMAIL PROTECTED] Usertags: gcj-bd gij/gcj and java-gcj-compat are not available (anymore) on the following architectures: alpha, arm, hppa and hurd-i386. This package has been identified as a package which build-depends on gcj or java-gcj-compat-dev and builds at least one architecture dependent package, and is unbuildable in unstable. If this report is a false positive, please close it. All gcj related build dependencies have to restricted to these architectures on which a java or java compatible development kit / compiler is available, i.e. java-gcj-compat [!alpha !arm !hppa !hurd-i386] As a second step please consider changing the java-gcj-compat-dev b-d to default-jdk-builddep, making the package independent of a specific implementation and depend on the jdk, which is most suitable for this architecture. default-jdk-builddep will depend in addition on java-gcj-compat-dev, even if the default jdk is another one (to allow to compile byte-code to native code using dh_nativejava). A package build-depending on default-jdk-builddep should use as JAVA_HOME /usr/lib/jvm/default-java, or as path for the tools /usr/lib/jvm/default-java/bin. If the package builds just architecture dependent binaries which contain only byte-code compiled to native code (packages which often end with -gcj), then the architecture restrictions on the build dependency may not be needed (however the package cannot be built anymore on those archs). In this case make sure that the binary packages get removed on these architectures. Please check the influence of a package upload on ongoing transitions before an upload. ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#477868: kaffe: adjust build-dependency (gcj not built on alpha, arm, hppa and hurd-i386)
Package: kaffe Version: 2:1.1.8-4 Severity: serious User: [EMAIL PROTECTED] Usertags: gcj-bd gij/gcj and java-gcj-compat are not available (anymore) on the following architectures: alpha, arm, hppa and hurd-i386. This package has been identified as a package which build-depends on gcj or java-gcj-compat-dev and builds at least one architecture dependent package, and is unbuildable in unstable. If this report is a false positive, please close it. All gcj related build dependencies have to restricted to these architectures on which a java or java compatible development kit / compiler is available, i.e. java-gcj-compat [!alpha !arm !hppa !hurd-i386] As a second step please consider changing the java-gcj-compat-dev b-d to default-jdk-builddep, making the package independent of a specific implementation and depend on the jdk, which is most suitable for this architecture. default-jdk-builddep will depend in addition on java-gcj-compat-dev, even if the default jdk is another one (to allow to compile byte-code to native code using dh_nativejava). A package build-depending on default-jdk-builddep should use as JAVA_HOME /usr/lib/jvm/default-java, or as path for the tools /usr/lib/jvm/default-java/bin. If the package builds just architecture dependent binaries which contain only byte-code compiled to native code (packages which often end with -gcj), then the architecture restrictions on the build dependency may not be needed (however the package cannot be built anymore on those archs). In this case make sure that the binary packages get removed on these architectures. Please check the influence of a package upload on ongoing transitions before an upload. ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#477847: bouncycastle: adjust build-dependency (gcj not built on alpha, arm, hppa and hurd-i386)
Package: bouncycastle Version: 1.39-1 Severity: serious User: [EMAIL PROTECTED] Usertags: gcj-bd gij/gcj and java-gcj-compat are not available (anymore) on the following architectures: alpha, arm, hppa and hurd-i386. This package has been identified as a package which build-depends on gcj or java-gcj-compat-dev and builds at least one architecture dependent package, and is unbuildable in unstable. If this report is a false positive, please close it. All gcj related build dependencies have to restricted to these architectures on which a java or java compatible development kit / compiler is available, i.e. java-gcj-compat [!alpha !arm !hppa !hurd-i386] As a second step please consider changing the java-gcj-compat-dev b-d to default-jdk-builddep, making the package independent of a specific implementation and depend on the jdk, which is most suitable for this architecture. default-jdk-builddep will depend in addition on java-gcj-compat-dev, even if the default jdk is another one (to allow to compile byte-code to native code using dh_nativejava). A package build-depending on default-jdk-builddep should use as JAVA_HOME /usr/lib/jvm/default-java, or as path for the tools /usr/lib/jvm/default-java/bin. If the package builds just architecture dependent binaries which contain only byte-code compiled to native code (packages which often end with -gcj), then the architecture restrictions on the build dependency may not be needed (however the package cannot be built anymore on those archs). In this case make sure that the binary packages get removed on these architectures. Please check the influence of a package upload on ongoing transitions before an upload. ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#477888: libservlet2.4-java: adjust build-dependency (gcj not built on alpha, arm, hppa and hurd-i386)
Package: libservlet2.4-java Version: 5.0.30-7 Severity: serious User: [EMAIL PROTECTED] Usertags: gcj-bd gij/gcj and java-gcj-compat are not available (anymore) on the following architectures: alpha, arm, hppa and hurd-i386. This package has been identified as a package which build-depends on gcj or java-gcj-compat-dev and builds at least one architecture dependent package, and is unbuildable in unstable. If this report is a false positive, please close it. All gcj related build dependencies have to restricted to these architectures on which a java or java compatible development kit / compiler is available, i.e. java-gcj-compat [!alpha !arm !hppa !hurd-i386] As a second step please consider changing the java-gcj-compat-dev b-d to default-jdk-builddep, making the package independent of a specific implementation and depend on the jdk, which is most suitable for this architecture. default-jdk-builddep will depend in addition on java-gcj-compat-dev, even if the default jdk is another one (to allow to compile byte-code to native code using dh_nativejava). A package build-depending on default-jdk-builddep should use as JAVA_HOME /usr/lib/jvm/default-java, or as path for the tools /usr/lib/jvm/default-java/bin. If the package builds just architecture dependent binaries which contain only byte-code compiled to native code (packages which often end with -gcj), then the architecture restrictions on the build dependency may not be needed (however the package cannot be built anymore on those archs). In this case make sure that the binary packages get removed on these architectures. Please check the influence of a package upload on ongoing transitions before an upload. ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#477851: charva: adjust build-dependency (gcj not built on alpha, arm, hppa and hurd-i386)
Package: charva Version: 1.1.4-2 Severity: serious User: [EMAIL PROTECTED] Usertags: gcj-bd gij/gcj and java-gcj-compat are not available (anymore) on the following architectures: alpha, arm, hppa and hurd-i386. This package has been identified as a package which build-depends on gcj or java-gcj-compat-dev and builds at least one architecture dependent package, and is unbuildable in unstable. If this report is a false positive, please close it. All gcj related build dependencies have to restricted to these architectures on which a java or java compatible development kit / compiler is available, i.e. java-gcj-compat [!alpha !arm !hppa !hurd-i386] As a second step please consider changing the java-gcj-compat-dev b-d to default-jdk-builddep, making the package independent of a specific implementation and depend on the jdk, which is most suitable for this architecture. default-jdk-builddep will depend in addition on java-gcj-compat-dev, even if the default jdk is another one (to allow to compile byte-code to native code using dh_nativejava). A package build-depending on default-jdk-builddep should use as JAVA_HOME /usr/lib/jvm/default-java, or as path for the tools /usr/lib/jvm/default-java/bin. If the package builds just architecture dependent binaries which contain only byte-code compiled to native code (packages which often end with -gcj), then the architecture restrictions on the build dependency may not be needed (however the package cannot be built anymore on those archs). In this case make sure that the binary packages get removed on these architectures. Please check the influence of a package upload on ongoing transitions before an upload. ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#477872: libgnome-java: adjust build-dependency (gcj not built on alpha, arm, hppa and hurd-i386)
Package: libgnome-java Version: 2.12.7-4 Severity: serious User: [EMAIL PROTECTED] Usertags: gcj-bd gij/gcj and java-gcj-compat are not available (anymore) on the following architectures: alpha, arm, hppa and hurd-i386. This package has been identified as a package which build-depends on gcj or java-gcj-compat-dev and builds at least one architecture dependent package, and is unbuildable in unstable. If this report is a false positive, please close it. All gcj related build dependencies have to restricted to these architectures on which a java or java compatible development kit / compiler is available, i.e. java-gcj-compat [!alpha !arm !hppa !hurd-i386] As a second step please consider changing the java-gcj-compat-dev b-d to default-jdk-builddep, making the package independent of a specific implementation and depend on the jdk, which is most suitable for this architecture. default-jdk-builddep will depend in addition on java-gcj-compat-dev, even if the default jdk is another one (to allow to compile byte-code to native code using dh_nativejava). A package build-depending on default-jdk-builddep should use as JAVA_HOME /usr/lib/jvm/default-java, or as path for the tools /usr/lib/jvm/default-java/bin. If the package builds just architecture dependent binaries which contain only byte-code compiled to native code (packages which often end with -gcj), then the architecture restrictions on the build dependency may not be needed (however the package cannot be built anymore on those archs). In this case make sure that the binary packages get removed on these architectures. Please check the influence of a package upload on ongoing transitions before an upload. ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#477854: cacao: adjust build-dependency (gcj not built on alpha, arm, hppa and hurd-i386)
Package: cacao Version: 0.98-2 Severity: serious User: [EMAIL PROTECTED] Usertags: gcj-bd gij/gcj and java-gcj-compat are not available (anymore) on the following architectures: alpha, arm, hppa and hurd-i386. This package has been identified as a package which build-depends on gcj or java-gcj-compat-dev and builds at least one architecture dependent package, and is unbuildable in unstable. If this report is a false positive, please close it. All gcj related build dependencies have to restricted to these architectures on which a java or java compatible development kit / compiler is available, i.e. java-gcj-compat [!alpha !arm !hppa !hurd-i386] As a second step please consider changing the java-gcj-compat-dev b-d to default-jdk-builddep, making the package independent of a specific implementation and depend on the jdk, which is most suitable for this architecture. default-jdk-builddep will depend in addition on java-gcj-compat-dev, even if the default jdk is another one (to allow to compile byte-code to native code using dh_nativejava). A package build-depending on default-jdk-builddep should use as JAVA_HOME /usr/lib/jvm/default-java, or as path for the tools /usr/lib/jvm/default-java/bin. If the package builds just architecture dependent binaries which contain only byte-code compiled to native code (packages which often end with -gcj), then the architecture restrictions on the build dependency may not be needed (however the package cannot be built anymore on those archs). In this case make sure that the binary packages get removed on these architectures. Please check the influence of a package upload on ongoing transitions before an upload. ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#477879: libjaxp1.3-java: adjust build-dependency (gcj not built on alpha, arm, hppa and hurd-i386)
Package: libjaxp1.3-java Version: 1.3.04-2 Severity: serious User: [EMAIL PROTECTED] Usertags: gcj-bd gij/gcj and java-gcj-compat are not available (anymore) on the following architectures: alpha, arm, hppa and hurd-i386. This package has been identified as a package which build-depends on gcj or java-gcj-compat-dev and builds at least one architecture dependent package, and is unbuildable in unstable. If this report is a false positive, please close it. All gcj related build dependencies have to restricted to these architectures on which a java or java compatible development kit / compiler is available, i.e. java-gcj-compat [!alpha !arm !hppa !hurd-i386] As a second step please consider changing the java-gcj-compat-dev b-d to default-jdk-builddep, making the package independent of a specific implementation and depend on the jdk, which is most suitable for this architecture. default-jdk-builddep will depend in addition on java-gcj-compat-dev, even if the default jdk is another one (to allow to compile byte-code to native code using dh_nativejava). A package build-depending on default-jdk-builddep should use as JAVA_HOME /usr/lib/jvm/default-java, or as path for the tools /usr/lib/jvm/default-java/bin. If the package builds just architecture dependent binaries which contain only byte-code compiled to native code (packages which often end with -gcj), then the architecture restrictions on the build dependency may not be needed (however the package cannot be built anymore on those archs). In this case make sure that the binary packages get removed on these architectures. Please check the influence of a package upload on ongoing transitions before an upload. ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#477843: antlr: adjust build-dependency (gcj not built on alpha, arm, hppa and hurd-i386)
Package: antlr Version: 2.7.7-4 Severity: serious User: [EMAIL PROTECTED] Usertags: gcj-bd gij/gcj and java-gcj-compat are not available (anymore) on the following architectures: alpha, arm, hppa and hurd-i386. This package has been identified as a package which build-depends on gcj or java-gcj-compat-dev and builds at least one architecture dependent package, and is unbuildable in unstable. If this report is a false positive, please close it. All gcj related build dependencies have to restricted to these architectures on which a java or java compatible development kit / compiler is available, i.e. java-gcj-compat [!alpha !arm !hppa !hurd-i386] As a second step please consider changing the java-gcj-compat-dev b-d to default-jdk-builddep, making the package independent of a specific implementation and depend on the jdk, which is most suitable for this architecture. default-jdk-builddep will depend in addition on java-gcj-compat-dev, even if the default jdk is another one (to allow to compile byte-code to native code using dh_nativejava). A package build-depending on default-jdk-builddep should use as JAVA_HOME /usr/lib/jvm/default-java, or as path for the tools /usr/lib/jvm/default-java/bin. If the package builds just architecture dependent binaries which contain only byte-code compiled to native code (packages which often end with -gcj), then the architecture restrictions on the build dependency may not be needed (however the package cannot be built anymore on those archs). In this case make sure that the binary packages get removed on these architectures. Please check the influence of a package upload on ongoing transitions before an upload. ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#477893: libxalan2-java: adjust build-dependency (gcj not built on alpha, arm, hppa and hurd-i386)
Package: libxalan2-java Version: 2.7.1-1 Severity: serious User: [EMAIL PROTECTED] Usertags: gcj-bd gij/gcj and java-gcj-compat are not available (anymore) on the following architectures: alpha, arm, hppa and hurd-i386. This package has been identified as a package which build-depends on gcj or java-gcj-compat-dev and builds at least one architecture dependent package, and is unbuildable in unstable. If this report is a false positive, please close it. All gcj related build dependencies have to restricted to these architectures on which a java or java compatible development kit / compiler is available, i.e. java-gcj-compat [!alpha !arm !hppa !hurd-i386] As a second step please consider changing the java-gcj-compat-dev b-d to default-jdk-builddep, making the package independent of a specific implementation and depend on the jdk, which is most suitable for this architecture. default-jdk-builddep will depend in addition on java-gcj-compat-dev, even if the default jdk is another one (to allow to compile byte-code to native code using dh_nativejava). A package build-depending on default-jdk-builddep should use as JAVA_HOME /usr/lib/jvm/default-java, or as path for the tools /usr/lib/jvm/default-java/bin. If the package builds just architecture dependent binaries which contain only byte-code compiled to native code (packages which often end with -gcj), then the architecture restrictions on the build dependency may not be needed (however the package cannot be built anymore on those archs). In this case make sure that the binary packages get removed on these architectures. Please check the influence of a package upload on ongoing transitions before an upload. ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#477895: libxmlrpc3-java: adjust build-dependency (gcj not built on alpha, arm, hppa and hurd-i386)
Package: libxmlrpc3-java Version: 3.1-1 Severity: serious User: [EMAIL PROTECTED] Usertags: gcj-bd gij/gcj and java-gcj-compat are not available (anymore) on the following architectures: alpha, arm, hppa and hurd-i386. This package has been identified as a package which build-depends on gcj or java-gcj-compat-dev and builds at least one architecture dependent package, and is unbuildable in unstable. If this report is a false positive, please close it. All gcj related build dependencies have to restricted to these architectures on which a java or java compatible development kit / compiler is available, i.e. java-gcj-compat [!alpha !arm !hppa !hurd-i386] As a second step please consider changing the java-gcj-compat-dev b-d to default-jdk-builddep, making the package independent of a specific implementation and depend on the jdk, which is most suitable for this architecture. default-jdk-builddep will depend in addition on java-gcj-compat-dev, even if the default jdk is another one (to allow to compile byte-code to native code using dh_nativejava). A package build-depending on default-jdk-builddep should use as JAVA_HOME /usr/lib/jvm/default-java, or as path for the tools /usr/lib/jvm/default-java/bin. If the package builds just architecture dependent binaries which contain only byte-code compiled to native code (packages which often end with -gcj), then the architecture restrictions on the build dependency may not be needed (however the package cannot be built anymore on those archs). In this case make sure that the binary packages get removed on these architectures. Please check the influence of a package upload on ongoing transitions before an upload. ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#477866: jakarta-log4j: adjust build-dependency (gcj not built on alpha, arm, hppa and hurd-i386)
Package: jakarta-log4j Version: 1.2.15-2 Severity: serious User: [EMAIL PROTECTED] Usertags: gcj-bd gij/gcj and java-gcj-compat are not available (anymore) on the following architectures: alpha, arm, hppa and hurd-i386. This package has been identified as a package which build-depends on gcj or java-gcj-compat-dev and builds at least one architecture dependent package, and is unbuildable in unstable. If this report is a false positive, please close it. All gcj related build dependencies have to restricted to these architectures on which a java or java compatible development kit / compiler is available, i.e. java-gcj-compat [!alpha !arm !hppa !hurd-i386] As a second step please consider changing the java-gcj-compat-dev b-d to default-jdk-builddep, making the package independent of a specific implementation and depend on the jdk, which is most suitable for this architecture. default-jdk-builddep will depend in addition on java-gcj-compat-dev, even if the default jdk is another one (to allow to compile byte-code to native code using dh_nativejava). A package build-depending on default-jdk-builddep should use as JAVA_HOME /usr/lib/jvm/default-java, or as path for the tools /usr/lib/jvm/default-java/bin. If the package builds just architecture dependent binaries which contain only byte-code compiled to native code (packages which often end with -gcj), then the architecture restrictions on the build dependency may not be needed (however the package cannot be built anymore on those archs). In this case make sure that the binary packages get removed on these architectures. Please check the influence of a package upload on ongoing transitions before an upload. ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#477880: libglade-java: adjust build-dependency (gcj not built on alpha, arm, hppa and hurd-i386)
Package: libglade-java Version: 2.12.8-4 Severity: serious User: [EMAIL PROTECTED] Usertags: gcj-bd gij/gcj and java-gcj-compat are not available (anymore) on the following architectures: alpha, arm, hppa and hurd-i386. This package has been identified as a package which build-depends on gcj or java-gcj-compat-dev and builds at least one architecture dependent package, and is unbuildable in unstable. If this report is a false positive, please close it. All gcj related build dependencies have to restricted to these architectures on which a java or java compatible development kit / compiler is available, i.e. java-gcj-compat [!alpha !arm !hppa !hurd-i386] As a second step please consider changing the java-gcj-compat-dev b-d to default-jdk-builddep, making the package independent of a specific implementation and depend on the jdk, which is most suitable for this architecture. default-jdk-builddep will depend in addition on java-gcj-compat-dev, even if the default jdk is another one (to allow to compile byte-code to native code using dh_nativejava). A package build-depending on default-jdk-builddep should use as JAVA_HOME /usr/lib/jvm/default-java, or as path for the tools /usr/lib/jvm/default-java/bin. If the package builds just architecture dependent binaries which contain only byte-code compiled to native code (packages which often end with -gcj), then the architecture restrictions on the build dependency may not be needed (however the package cannot be built anymore on those archs). In this case make sure that the binary packages get removed on these architectures. Please check the influence of a package upload on ongoing transitions before an upload. ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#477897: libxml-commons-resolver1.1-java: adjust build-dependency (gcj not built on alpha, arm, hppa and hurd-i386)
Package: libxml-commons-resolver1.1-java Version: 1.2-1 Severity: serious User: [EMAIL PROTECTED] Usertags: gcj-bd gij/gcj and java-gcj-compat are not available (anymore) on the following architectures: alpha, arm, hppa and hurd-i386. This package has been identified as a package which build-depends on gcj or java-gcj-compat-dev and builds at least one architecture dependent package, and is unbuildable in unstable. If this report is a false positive, please close it. All gcj related build dependencies have to restricted to these architectures on which a java or java compatible development kit / compiler is available, i.e. java-gcj-compat [!alpha !arm !hppa !hurd-i386] As a second step please consider changing the java-gcj-compat-dev b-d to default-jdk-builddep, making the package independent of a specific implementation and depend on the jdk, which is most suitable for this architecture. default-jdk-builddep will depend in addition on java-gcj-compat-dev, even if the default jdk is another one (to allow to compile byte-code to native code using dh_nativejava). A package build-depending on default-jdk-builddep should use as JAVA_HOME /usr/lib/jvm/default-java, or as path for the tools /usr/lib/jvm/default-java/bin. If the package builds just architecture dependent binaries which contain only byte-code compiled to native code (packages which often end with -gcj), then the architecture restrictions on the build dependency may not be needed (however the package cannot be built anymore on those archs). In this case make sure that the binary packages get removed on these architectures. Please check the influence of a package upload on ongoing transitions before an upload. ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#477900: libsaxon-java: adjust build-dependency (gcj not built on alpha, arm, hppa and hurd-i386)
Package: libsaxon-java Version: 1:6.5.5-4 Severity: serious User: [EMAIL PROTECTED] Usertags: gcj-bd gij/gcj and java-gcj-compat are not available (anymore) on the following architectures: alpha, arm, hppa and hurd-i386. This package has been identified as a package which build-depends on gcj or java-gcj-compat-dev and builds at least one architecture dependent package, and is unbuildable in unstable. If this report is a false positive, please close it. All gcj related build dependencies have to restricted to these architectures on which a java or java compatible development kit / compiler is available, i.e. java-gcj-compat [!alpha !arm !hppa !hurd-i386] As a second step please consider changing the java-gcj-compat-dev b-d to default-jdk-builddep, making the package independent of a specific implementation and depend on the jdk, which is most suitable for this architecture. default-jdk-builddep will depend in addition on java-gcj-compat-dev, even if the default jdk is another one (to allow to compile byte-code to native code using dh_nativejava). A package build-depending on default-jdk-builddep should use as JAVA_HOME /usr/lib/jvm/default-java, or as path for the tools /usr/lib/jvm/default-java/bin. If the package builds just architecture dependent binaries which contain only byte-code compiled to native code (packages which often end with -gcj), then the architecture restrictions on the build dependency may not be needed (however the package cannot be built anymore on those archs). In this case make sure that the binary packages get removed on these architectures. Please check the influence of a package upload on ongoing transitions before an upload. ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#477875: libjmathtex-java: adjust build-dependency (gcj not built on alpha, arm, hppa and hurd-i386)
Package: libjmathtex-java Version: 0.7~pre-3 Severity: serious User: [EMAIL PROTECTED] Usertags: gcj-bd gij/gcj and java-gcj-compat are not available (anymore) on the following architectures: alpha, arm, hppa and hurd-i386. This package has been identified as a package which build-depends on gcj or java-gcj-compat-dev and builds at least one architecture dependent package, and is unbuildable in unstable. If this report is a false positive, please close it. All gcj related build dependencies have to restricted to these architectures on which a java or java compatible development kit / compiler is available, i.e. java-gcj-compat [!alpha !arm !hppa !hurd-i386] As a second step please consider changing the java-gcj-compat-dev b-d to default-jdk-builddep, making the package independent of a specific implementation and depend on the jdk, which is most suitable for this architecture. default-jdk-builddep will depend in addition on java-gcj-compat-dev, even if the default jdk is another one (to allow to compile byte-code to native code using dh_nativejava). A package build-depending on default-jdk-builddep should use as JAVA_HOME /usr/lib/jvm/default-java, or as path for the tools /usr/lib/jvm/default-java/bin. If the package builds just architecture dependent binaries which contain only byte-code compiled to native code (packages which often end with -gcj), then the architecture restrictions on the build dependency may not be needed (however the package cannot be built anymore on those archs). In this case make sure that the binary packages get removed on these architectures. Please check the influence of a package upload on ongoing transitions before an upload. ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
libformula_0.1.14-1_amd64.changes ACCEPTED
Accepted: libformula-java-doc_0.1.14-1_all.deb to pool/main/libf/libformula/libformula-java-doc_0.1.14-1_all.deb libformula-java_0.1.14-1_all.deb to pool/main/libf/libformula/libformula-java_0.1.14-1_all.deb libformula_0.1.14-1.diff.gz to pool/main/libf/libformula/libformula_0.1.14-1.diff.gz libformula_0.1.14-1.dsc to pool/main/libf/libformula/libformula_0.1.14-1.dsc libformula_0.1.14.orig.tar.gz to pool/main/libf/libformula/libformula_0.1.14.orig.tar.gz Override entries for your package: libformula-java-doc_0.1.14-1_all.deb - optional doc libformula-java_0.1.14-1_all.deb - optional libs libformula_0.1.14-1.dsc - source libs Announcing to [EMAIL PROTECTED] Thank you for your contribution to Debian. ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
tomcat5.5 5.5.26-1 MIGRATED to testing
FYI: The status of the tomcat5.5 source package in Debian's testing distribution has changed. Previous version: 5.5.25-5 Current version: 5.5.26-1 -- This email is automatically generated; [EMAIL PROTECTED] is responsible. See http://people.debian.org/~henning/trille/ for more information. ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
