Bug#913785: ITP: android-platform-art -- Android Runtime Utilities
Package: wnpp Severity: wishlist * Package name: android-platform-art * Version : 8.1.0+r23-1 * Upstream Author : Google * License : Apache-2.0 * Languages : C++ * Description : Android Runtime Utilities * Homepage: https://android.googlesource.com/platform/art * Vcs : https://salsa.debian.org/android-tools-team/android-platform-art This package provides the following Android SDK components: * dexdump * dmtracedump Which was previously provided by src:android-platform-dalvik. signature.asc Description: OpenPGP digital signature
Bug#904978: ITP: protobuf-2 -- This is the protobuf pacakge but version 2.6.1 same as that foudn in jessie but is being packaged to unstable since kotlin-1.1.1 needs it. p.s kotlin-1.1.1 is also being
It needs JetBriains's fork of JDOM [1]. [1]: https://github.com/JetBrains/intellij-deps-jdom Emmanuel Bourg 於 2018年08月09日 16:33 寫道: >> We can do this to `picocontainer`, `protobuf`,`spullara-cli-parser` >> and `jdom`. > > We already have two version of jdom (libjdom1-java and libjdom2-java). > What is the version required by Kotlin? > > Emmanuel Bourg > signature.asc Description: OpenPGP digital signature
Bug#904978: ITP: protobuf-2 -- This is the protobuf pacakge but version 2.6.1 same as that foudn in jessie but is being packaged to unstable since kotlin-1.1.1 needs it. p.s kotlin-1.1.1 is also being
Is this version of protobuf only required by Kotlin? I am thinking that maybe we can just include all those legacy libraries (and possibly JetBrains-modified ones) inside either Kotlin or `intellij-core` as they tend to be used only by those 2 projects at the moment. Thus we can really save a great amount of time from waiting for the NEW queue. We can do this to `picocontainer`, `protobuf`,`spullara-cli-parser` and `jdom`. Saif Abdul Cassim 於 2018年07月30日 19:02 寫道: > kotlin is already bulky and needs atleast 8-9 more new pacakges and some of > them are older versions, including all of them will make things more messed > up when we try to update this. Kotlin 1.1.1 is not just for bootstrapping it > provides the full functionality of kotlin 1.1.1. > > On 30 July 2018 at 16:13, Colin Watson <mailto:cjwat...@debian.org>> wrote: > > On Mon, Jul 30, 2018 at 05:23:15PM +0800, 殷啟聰 | Kai-Chung Yan wrote: > > Yes, that Kotlin by Jetbrains. Packaging a language is quite > > complicated, and we are bootstrapping an older version (so the process > > can be a lot easier), and then we will update it to the latest version > > once it's accepted. > > If it's just for bootstrapping, I'd consider temporarily embedding the > older protobuf version in the kotlin source package instead, with a note > that this will be removed once you're on a current version. That should > be less work for ftpmasters, quite possibly even less work for you, and > it doesn't make it look like the old version of protobuf is being > packaged for general use. > > -- > Colin Watson [cjwat...@debian.org > <mailto:cjwat...@debian.org>] > > signature.asc Description: OpenPGP digital signature
Bug#904978: ITP: protobuf-2 -- This is the protobuf pacakge but version 2.6.1 same as that foudn in jessie but is being packaged to unstable since kotlin-1.1.1 needs it. p.s kotlin-1.1.1 is also being
Unfortuantely even the latest version of Kotlin still uses Protobuf 2.x, so it's not going anywhere in a short time. This package will only build the Java libraries, everything else is stripped. Though your suggestion works on another dependency of Kotlin, `spullara-cli-parser`, which is no longer used by the latest Kotlin. Thanks! Colin Watson 於 2018年07月30日 18:43 寫道: > On Mon, Jul 30, 2018 at 05:23:15PM +0800, 殷啟聰 | Kai-Chung Yan wrote: >> Yes, that Kotlin by Jetbrains. Packaging a language is quite >> complicated, and we are bootstrapping an older version (so the process >> can be a lot easier), and then we will update it to the latest version >> once it's accepted. > > If it's just for bootstrapping, I'd consider temporarily embedding the > older protobuf version in the kotlin source package instead, with a note > that this will be removed once you're on a current version. That should > be less work for ftpmasters, quite possibly even less work for you, and > it doesn't make it look like the old version of protobuf is being > packaged for general use. > signature.asc Description: OpenPGP digital signature
Bug#823933: ITP: android-platform-external-boringssl -- Fork of OpenSSL that is designed to meet Google's needs
Control: retitle -1 ITP: android-platform-external-boringssl -- Fork of OpenSSL that is designed to meet Google's needs This ITP was intended to fulfill the requirements of Android SDK packages. Now we have decided to package the BoringSSL fork inside AOSP as BoringSSL already states [1] that projects should rely on their own fork instead of the upstream one. Here is the updated description: * Package name: android-platform-external-boringssl * Version : 8.1.0+r23-1 * Upstream Author : Google * License : OpenSSL license, BSD, ISC * Programming lang: C, C++ * Description : Fork of OpenSSL that is designed to meet Google's needs * Homepage: https://android.googlesource.com/platform/external/boringssl * Salsa : https://salsa.debian.org/android-tools-team/android-platform-external-boringssl [1]: https://boringssl.googlesource.com/boringssl/+/HEAD/PORTING.md
Bug#898910: ITP: dd-plist -- Java library for working with property lists
Package: wnpp Severity: wishlist * Package-Name : dd-plist * Version : 1.20-1 * License : MIT * Programming-Lang: Java * Description : Java library for working with property lists * Vcs : https://salsa.debian.org/java-team/dd-plist This package builds the following binary package: * libdd-plist-java This package is a new dependency [1] by Gradle 4.4, which is what I have been working on. [1]: https://salsa.debian.org/seamlik-guest/gradle/commit/c1931b69bbdc91cb33f1f4e182621deb3e2c9a17 signature.asc Description: OpenPGP digital signature
Bug#892603: ITP: android-platform-system-extras-ext4 -- this package will contain the necessary tools required to make android images(.img) with the ext4 file systems and hence replace android-tools-f
Extending the existing "android-platform-system-extras" source package is more than sufficient signature.asc Description: OpenPGP digital signature
Bug#892519: ITP: maven-dependency-tree-2 -- Tree-based API for resolution of Maven project dependencies
Package: wnpp Severity: wishlist * Package Name : maven-dependency-tree-2 * Version : 2.2-1 * License : Apache-2.0 * Programming Lang: Java * Description : Tree-based API for resolution of Maven project dependencies * VCS : https://anonscm.debian.org/git/pkg-java/maven-dependency-tree-2.git This package builds the following binary package: * libmaven-dependency-tree-2-java This is a 2.x version of "maven-dependency-tree" [1]. The latest version of "maven-bundle-plugin" [2] is only compatible with this version, hence the new package. This package may be removed once "maven-bundle-plugin" fixes the issue [3]. [1]: https://tracker.debian.org/pkg/maven-dependency-tree [2]: https://tracker.debian.org/pkg/maven-bundle-plugin [3]: https://issues.apache.org/jira/browse/FELIX-5795 signature.asc Description: OpenPGP digital signature
Bug#892268: ITP: felix-resolver -- OSGi Resolver implementation by Apache Felix
Package: wnpp Severity: wishlist * Package Name : felix-resolver * Version : 1.14.0-1 * License : Apache-2.0 * Programming Lang: Java * Description : OSGi Resolver implementation by Apache Felix * Vcs : https://anonscm.debian.org/cgit/pkg-java/felix-resolver.git This is a subproject of Apache Felix, an OSGi implementation. It is also a dependency introduced by BND 3.x, which is a crucial part of the Java ecosystem. The Java team is now migrating BND from 2.x to 3.x, hence the new package. signature.asc Description: OpenPGP digital signature
Bug#890597: ITP: maven-repo-helper-extras -- Additional plugins complementing maven-repo-helper
Package: wnpp Severity: wishlist * Package Name : maven-repo-helper-extras * Version : 0.1 * License : Apache-2.0 * Programming Lang: Java * Description : Additional plugins complementing maven-repo-helper * URL : https://salsa.debian.org/seamlik-guest/maven-repo-helper-extras This package provides 2 Debhelper plugins that makes maintaining Maven packages easier. They are: * mh_shlibdeps: Calculates package dependencies based on Maven metadata. * mh_genlaunchers: Generates Java launcher scripts based on Maven metadata. "mh_shlibdeps" works just like "dh_shlibdeps". It examines the Maven artifacts installed by a package and generate "${maven:Depends}" in a ".substvars" file. "mh_genlaunchers" generates a Java program launcher script based on a ".maven-launchers" file. It has a syntax like: usr/bin/mh_shlibdeps org.debian.maven.Shlibdeps org.debian:maven-debian-utils:debian This file specifies the launcher location, main class name and the Maven artifact providing said main class. The reason why I invented a new project instead of adding them to "maven-repo-helper" is that I wanted to implement it using upstream code (e.g. maven-resolver [1]) and in pure Java (without shell script like "javahelper"). [1]: https://maven.apache.org/resolver signature.asc Description: OpenPGP digital signature
Bug#890222: ITP: jnacl -- Pure Java implementation of the NaCl: Networking and Cryptography library
Perhaps urge him to make a release? signature.asc Description: OpenPGP digital signature