Bug#778975: [Android-tools-devel] Bug#778975: Mention adb help

Thanks for the help. But I am getting error opening the diff with Kompare? 2015年4月24日 下午11:33於 Simon Sickle si...@simonsickle.com寫道： Hello. I am new to this (submitting patches on Debian) but attached to this email, you will find a proposed patch to this issue. If I am doing this incorrectly,

Bug#778975: Mention adb help

On Fri, 24 Apr 2015 11:29:52 -0400 Simon Sickle si...@simonsickle.com wrote: Hello. I am new to this (submitting patches on Debian) but attached to this email, you will find a proposed patch to this issue. If I am doing this incorrectly, please let me know. Thanks everyone!

Bug#683666: I Will Help Update Gradle to the Latest Version

I am a would-be GSoC student this year currently working on the integration of Android SDK into Debian and updating Gradle and Groovy is within our to-do list. Hence I will help update Gradle to the latest version during this summer. -- /* * 殷啟聰 | Kai-Chung Yan * Full-time student of Providence

Bug#787707: ITP: bintray-client-java -- Bintray REST Client Java API Bindings

Package: wnpp Severity: wishlist X-Debbugs-CC: pkg-java-maintain...@lists.alioth.debian.org * Package name: bintray-client-java * Version: 0.10 * Upstream: JFrog developers * License: Apache-2.0 * Language: Java * Homepage: https://bintray.com/jfrog/bintray-tools/bintray-client-java * Alioth Git:

Bug#795946: ITP: android-platform-frameworks-compile -- Android compiler frameworks

Package: wnpp Severity: wishlist Owner: android-tools-de...@lists.alioth.debian.org * Package Name: android-platform-frameworks-compile Version: 5.1.1+r8 Upstream Author: Android Open Source Project * URL: https://android.googlesource.com/platform/frameworks/compile/libbcc * License: Apache

Bug#795995: ITP: android-platform-libcore -- Core Java libraries for Android

Package: wnpp Severity: wishlist Owner: android-tools-de...@lists.alioth.debian.org * Package Name: android-platform-external-libunwind Version: 5.1.1+r8 Upstream Author: Android Open Source Project * URL: https://android.googlesource.com/platform/libcore * License: Apache 2.0 Programming

Bug#793863: Add new package f2fs-tools-dev for external development use

Source: f2fs-tools Version: 1.4.1-1 Severity: wishlist Tags: patch X-Debbugs-CC: komaldsukh...@gmail.com,h...@at.or.at,a...@gambaru.de,android-tools-de...@lists.alioth.debian.org Hi, I am packaging Android SDK which requires a libf2fs_fmt.so compiled from libf2fs.c, f2fs_format.c and

Bug#793863: Add new package f2fs-tools-dev for external development use

Cheng vch...@debian.org: Control: tag -1 - patch + newcomer Hi Kai-Chung, On Tue, Jul 28, 2015 at 2:51 AM, 殷啟聰 seamli...@gmail.com wrote: Source: f2fs-tools Version: 1.4.1-1 Severity: wishlist Tags: patch X-Debbugs-CC: komaldsukh...@gmail.com,h...@at.or.at,a...@gambaru.de,android-tools

Bug#793863: New patch available

Control: tags -1 patch Control: retitle -1 Add new packages for external development use Hi Vincent and other maintainers, This is my new patch, it adds the following packages: - libf2fs-dev - libf2fs-format-dev - libf2fs-format1 - libf2fs1 I added two patches to achieve this.

Bug#794232: Add new packages for libzopfli.so

Source: zopfli Version: 1.0.0-1 Severity: wishlist Tags: patch Hi, I am packaging Android SDK and I found the zipalign tool requires the dynamic library version of zopfli, which is so-called libzopfli.so. Current zopfli package does not contain the library, so I wrote a patch to change that.

Bug#793863: Improved patch available

Hi, During the work on Android SDK I corrected some compiler flags for libf2fs_format.so, please consider this improved patch. You can also view the patch at https://github.com/seamlik/debianpkg-f2fs-tools/compare/master...modify-autotools. Thank you. Regards, Kai-Chung Yan diff --git

Bug#794522: RFS: safe-iop/0.3.1-1 [ITP] -- Safe integer operations library

Package: sponsorship-requests Severity: wishlist * Package name: safe-iop Version: 0.3.1-1 * URL: http://code.google.com/p/safe-iop * License: public-domain Section: libs Dear mentors, I am looking for a sponsor for my new package safe-iop, which builds those binary packages: * libsafe-iop0

Bug#790131: Retitle #790131 to safe-iop

Control: retitle -1 ITP: safe-iop -- Safe integer operations library safe-iop is no part of Android, hence rename it to safe-iop. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#459219: Android SDK toolchain in Debian GSOC project

in this email licensed under CC 3.0 http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com EB80 462B 08E1 A0DE A73A 2C2F 9F3D C7A4 E1C4 D2D8 -- /* * 殷啟聰 | Kai-Chung Yan * 一生只向真理與妻子低頭 * Full-time student of National Taichung University of Education * LinkedIn: https

Bug#795173: ITP: android-platform-external-libunwind -- libunwind for Android

Package: wnpp Severity: wishlist Owner: android-tools-de...@lists.alioth.debian.org * Package Name: android-platform-external-libunwind Version: 5.1.1+r8 Upstream Author: Android Open Source Project * URL: https://android.googlesource.com/platform/external/libunwind * License: MIT

Bug#793795: Please re-import full upstream and reveal the code repository URL

Package: zopfli Version: 1.0.0-1 Severity: wishlist Comparing Debian's zopfli to the upstream we can find that Debian's orig tarball lacks some components like src/zopflipng and the makefile's contents are also diferrent. Please re-import the upstream tarball from https://github.com/google/zopfli

Bug#793795: Please re-import full upstream and reveal the code repository URL

files in a new package like zopfli-dev. Cheers, Kai-Chung Yan László Böszörményi (GCS) g...@debian.org 於 2015年7月28日週二 上午12:04寫道： Control: tags -1 + moreinfo On Mon, Jul 27, 2015 at 5:45 PM, 殷啟聰 seamli...@gmail.com wrote: Package: zopfli Version: 1.0.0-1 Severity: wishlist Comparing

Bug#790131: ITP: android-platform-external-safe-iop -- safe integer operations library

Hi, I am also working on Android SDK in Debian. Why not name the source package safe-iop instead? This project is external and no need to include android in the name. You can fetch the source from GitHub https://github.com/redpig/safe-iop. I was about to package it and I found your ITP. Cheers,

Bug#790131: ITP: android-platform-external-safe-iop -- safe integer operations library

Hi Herrmann, Thanks for the packaging! However I do not agree that safe-iop is part of Android SDK. It is an external project but used by Android, like e2fsprogs and f2fs-tools. So we should follow the upstream, name it safe-iop and the binary package libsafe-iop-dev, and the version should be

Bug#793614: ITP: android-platform-dalvik -- Java virtual machine for Android

Package: wnpp Severity: wishlist Owner: android-tools-de...@lists.alioth.debian.org * Package Name: android-platform-dalvik Version: 5.1.1+r8 Upstream Author: Android Open Source Project * URL: https://android.googlesource.com/platform/dalvik * License: Apache-2.0 Programming Lang: C, C++,

Bug#793611: ITP: android-platform-external-libselinux -- Security-Enhanced Linux in Android

Package: wnpp Severity: wishlist Owner: android-tools-de...@lists.alioth.debian.org * Package Name: android-platform-external-libselinux Version: 5.1.1+r8 Upstream Author: Android Open Source Project * URL: https://android.googlesource.com/platform/external/libselinux * License: public-domain

Bug#793863: Add new package f2fs-tools-dev for external development use

Hi Vincent, Sorry for the late reply. I have fixed the FTBFS and it's buildable now. Please check the patch attached or visit . Here is the changes: * FTBFS because I installed the binaries to /usr/sbin(lib)

Bug#793911: groovy should not release with stretch

On Tue, 28 Jul 2015 22:38:40 +0200 Moritz Muehlenhoff wrote: > Package: groovy > Severity: serious > > A separate source package groovy2 was uploaded, so reverse dependencies > need to be migrated to that one and groovy removed. > > Cheers, > Moritz > > Hi Moritz and all

Bug#789609: AOSP Does Not Support PowerPC

The Android Open Source Project only supports x86, MIPS and ARM, so I don't think we should build it on other architectures even if there seems to be no errors. But anyway in the next upload for 6.0.0_r26, this package only produces one arch-independent package contains only some headers, which

Bug#806375: Should Be Reassigned to android-platform-system-core But Won't Be Fixed by Next Upload

According to the CVE descriptions, these bugs belongs to libutils. Since Android 5.1.1, libutils has been moved to src:android-platform-system-core (See ), so after the next upload (6.0.0_r24) I will reassign this bug

Bug#793863: Add new package f2fs-tools-dev for external development use

Hi Vincent, Since you became silent again..., several days ago we submitted the patch to upstream, but they are also really sloow in accepting it... Maybe you can do it before the upstream does? Thank you! Regards, Kai-Chung Yan -- /* * 殷啟聰 | Kai-Chung Yan * 一生只向真理與妻子低頭 * Full-time student

Bug#793863: Add new package f2fs-tools-dev for external development use

Hi Vincent, There are several reasons that dh-exec does simplify things, especially when we are maintaining a package that produces multiple binary packages: 1. If you don't write *.install files, debhelper will install all files under debian/tmp to the binary package with the same name of the

Bug#826761: android-sdk: JDK missing

＠Mouaad In your commit [1], you forgot to increment the version of other 4 packages to "+3" in debian/rules. It would be better if this can be handled by a text-substitution function :) [1]: https://gitlab.com/Aallam/debian_android-sdk-meta/commit/67438f67fe529656eaea8dd368671ab17814b0c2

Bug#825617: Should Enable Parallel Builds According to DEB_BUILD_OPTIONS

Package: gradle-debian-helper Version: 1.1 Severity: wishlist Gradle supports parallel building through "--parallel" and "--max-workers". Currently gradle-debian-helper does not honor the parallel options in DEB_BUILD_OPTIONS and I have to write this: ``` ifneq (,$(filter

Bug#826870: android-sdk: Gradle missing

I agree that Gradle should be put in Recommends.

Bug#826761: android-sdk: JDK missing

@Mouaad This patch look nice. Could you push it to Alioth along with the patch adding default-jdk? Thank you! Would be better if you use some sed command to process the version string. You can retrieve the package version by including "/usr/share/dpkg/pkg-info.mk" and access the variable

Bug#827216: android-sdk: Process 'command 'aapt'' finished with non-zero exit value 134

Can you attach the outputs of running `gradle build --debug` and the detailed "Abort message"?

Bug#825539: ITP: okio -- Modern I/O API for Java

Package: wnpp Severity: wishlist * Package name: okio Version : 1.8.0-1 * Upstream Author : Square, Inc. * License : Apache-2.0 * Programming lang: Java * Description : Modern I/O API for Java * URL : https://github.com/square/okio * Alioth :

Bug#810596: ITP: android-platform-system-extras -- debugging/inspection tools for Android

Package: wnpp Severity: wishlist Owner: android-tools-de...@lists.alioth.debian.org * Package Name: android-platform-system-extras Version: 6.0.0+r26 Upstream Author: Android Open Source Project * URL: https://android.googlesource.com/platform/system/extras * License: Apache-2.0 Programming

Bug#810618: Please Install More Headers

Source: zopfli Version: 1.0.1-2 Severity: wishlist Owner: android-tools-de...@lists.alioth.debian.org Hi Laszlo, unfortunately zipalign in android-platform-build needs zopfli/deflate.h and potentially more other headers but your package currently only installs zopfli/zopfli.h. So it would be

Bug#811053: *.poms Should Not Be Required to Ensure Trailing Newline

Package: maven-repo-helper Version: 1.8.12 Severity: normal If the $package.poms contains only one line, say: debian/foo.pom --usj-name=foo maven-repo-helper will not install any .pom or symlinks to usr/share/maven-repo. But if I append a newline to the end, it works without any problem. And

Bug#811053: *.poms Should Not Be Required to Ensure Trailing Newline

Thank you for responding so rapidly! I am packaging android-platform-libcore in . Actually I think this is also the reason why src:gradle currently only installs .pom but without symlinks.

Bug#813899: ITP: android-platform-libnativehelper -- Support functions for Android's class libraries

functions for Android's class libraries libnativehelper is a dependency of dexdump of src:android-platform-dalvik, which is a tool in Android SDK. -- /* * 殷啟聰 | Kai-Chung Yan * 一生只向真理與妻子低頭 * Full-time student of National Taichung University of Education * LinkedIn: <https://linkedin.com/in/seam

Bug#811716: android-platform-frameworks-native: FTBFS with GCC 6: redeclaration of C++ built-in type

Control: reassign -1 src:android-platform-system-core 1:6.0.0+r26-1~stage1.1 Control: tags + moreinfo libutils is already moved to src:android-platform-system-core hence I reassign this bug. However I haven't tested GCC 6 for the latest libutils, but I guess it will fail too because I haven't use

Bug#811716: android-platform-frameworks-native: FTBFS with GCC 6: redeclaration of C++ built-in type

Control: reassign -1 android-platform-system-core 1:6.0.0+r26-1~stage1.1 Control: tags -1 + moreinfo Control: retitle -1 libutils: FTBFS with GCC 6: redeclaration of C++ built-in type Apologies for my unfamiliarity of Debian Bugs Tracking System :(

Bug#806375: CVE-2015-6609 CVE-2015-6602 CVE-2015-3875

Control: reassign -1 android-libutils 1:6.0.0+r26-1~stage1.1 Control: tags -1 confirmed fixed-upstream It is fixed since Android 6.0.1 Release 13.

Bug#814964: ITP: android-platform-development -- Source pacakge for etc1tool

Package: wnpp Severity: wishlist * Package Name: android-platform-development Version : 6.0.1+r16-1 * Upstream Author : Android Open Source Project * URL : https://android.googlesource.com/platform/development * License : Apache-2.0 * Programming Lang: C++ *

Bug#814202: android-platform-dalvik: FTBFS: unable to load addon maven_repo_helper

Control: reopen -1 Version: 6.0.1+r16-2 Unfortunately I couldn't successfully fix this bug. FTBFS again for the same reason. dpkg-buildpackage does not support clean-indep | clean-arch yet, really a pity.

Bug#815137: Release 56.1 Is Available

Source: icu4j Version: 4.2.1.1-3 Severity: wishlist The Android Frameworks for developing Android applications depends on icu4j-56, please update this source package to at least 56. Better to avoid creating another libicu4j-56-java :( Would be better if it is migrated to Git.

Bug#814600: android-tools: B-D on obsolete android-system-dev

"-include /usr/include/android/arch/linux-x86/AndroidConfig.h" should be replaced with "-include android/arch/AndroidConfig.h", and you should add android-platform-build-headers to BDs. FYI, AndroidConfig.h is now moved to /usr/include/${DEB_HOST_MULTIARCH}/android/arch

Bug#817008: unfulfilled dependencies

I don't really know too much about the transition process, do you mean it will block the transition of src:android-sdk-meta itself? And of course I will wait and see what will happen to my packages. >From > we

Bug#817008: unfulfilled dependencies

I am confident that 24.3.3+2 solved the bug, but I prefer to wait for the package getting accepted. Just want to be cautious :)

Bug#817863: RFS: android-platform-system-core/1:6.0.1+r16-3

from http://www.example.com. Changes since the last upload: * Fix package name typo: android-{zipfile=>libzipfile}(-dev) Regards, Kai-Chung Yan -- /* * 殷啟聰 | Kai-Chung Yan * 一生只向真理與妻子低頭 * Undergraduate student in National Taichung University of Education * LinkedIn: <http

Bug#819188: RFS: icu4j/57.1-1

There are Google stuff? Could you point me to the files? Thanks!

Bug#817823: [Android-tools-devel] arm64 & armhf builds?

X-Debbugs-CC: android-tools-de...@lists.alioth.debian.org X-Debbugs-CC: codeh...@debian.org adb and fastboot are part of the Android SDK which are only officially supported on x86 platforms. Strictly speaking, Google only supports its i386 version, because the official SDK are mostly 32-bit

Bug#819188: RFS: icu4j/57.1-1

Package: sponsorship-requests Severity: normal X-Debbugs-CC: debian-j...@lists.debian.org Dear mentors, I am looking for a sponsor for my package "icu4j" * Package name: icu4j Version : 57.1-1 Upstream Author : IBM * URL : http://www.icu-project.org * License

Bug#819193: Change BD to libicu4j-4.2-java

Source: lucene2 Version: 2.9.4+ds1-4 Severity: wishlist Control: block -1 819192 Owner: Kai-Chung Yan src:icu4j is going to be updated to 57.1 which will break src:lucene2. The current workaround is to change the BD from libicu4j-java to libicu4j-4.2-java.

Bug#819193: Change BD to libicu4j-4.2-java

Control: block -1 by 819192

Bug#819192: ITP: icu4j-4.2 -- Library for Unicode support and internationalization

Package: wnpp Severity: wishlist Owner: Kai-Chung Yan * Package name: icu4j-4.2 Version : 4.2.1.1 * Upstream Author : IBM * URL : http://www.icu-project.org * License : ICU * Programming Lang: Java * Description : Library for Unicode

Bug#819193: Change BD to libicu4j-4.2-java

Control: block -1 819192 First icu4j-4.2 must be uploaded.

Bug#819188: RFS: icu4j/57.1-1

Control: block -1 by 819192 819193

Bug#817823: [Android-tools-devel] arm64 & armhf builds?

So, looks like the LAVA team does need adb & fastboot on all ARM platforms, right? :) I was wrong about android-libunwind. Actually I remember it was android-libbacktrace, which is needed by adb, who FTBFS in the other platforms. What if android-libbacktrace still FTBFS on ARM? In that case, adb

Bug#817823: RM: android-libcutils android-libcutils-dev android-liblog android-liblog-dev [arm64 armel armhf mips mips64el mipsel powerpc ppc64el s390x] -- ANAIS; old binaries in architectures not all

Thank you for reporting this, looks like this is really blocking the migration. I have been watching [1] but not [2] so I did not notice the problem... :( When will this RM be processed? Ftp-master people randomly select and process a bug? Or should I do anything to "agree" to this RM as I am one

Bug#816083: android-platform-build: Please change B-D for the android-platform-frameworks-native transition

Control: tags -1 confirmed I'm sorry that the transition has affected libpng1.6. android-sdk-meta being uninstallable does not seem to be the problem here. The problem is src:android-platform-build still depends on android-libutils-dev, which is however moved to src:android-platform-system-core

Bug#814600: android-tools: B-D on obsolete android-system-dev

Anyone is fixing this bug? Having my tips it shouldn't be hard to fix. I believe this bug is currently stopping src:android-platform-system-core from getting into testing. We should either fix this bug or remove this package ASAP. See

Bug#817008: unfulfilled dependencies

Thank you for reporting the bug. Actually the reason to this is that I used ${source:Version} for "android-sdk-platform-tools" and "android-sdk-build-tools", which is substituted to the version of the source package rather than their own. I have fixed it but not yet uploaded it. The reason of

Bug#804011: ITP: airline -- Java annotation-based framework for parsing command line parameters

Hi Emmanuel, What is the status of this package? I am packaging OkHttp which requires Airline. If you are unable to do it at the time I can give you a hand.

Bug#824720: ITP: android-platform-external-conscrypt -- Java Security Provider that uses OpenSSL

Package: wnpp Severity: wishlist * Package name: android-platform-external-conscrypt Version : 6.0.1+r16-1 * Upstream Author : The Android Open Source Project * License : Apache-2.0 * Programming lang: Java * Description : Java Security Provider that uses OpenSSL * URL

Bug#823933: ITP: boringssl -- Fork of OpenSSL that is designed to meet Google's needs

Package: wnpp Severity: wishlist * Package name: boringssl Version : 3.0-1 * Upstream Author : Google * License : OpenSSL license, BSD, ISC * Programming lang: C, C++, Go * Description : Fork of OpenSSL that is designed to meet Google's needs * URL :

Bug#819188: RFS: icu4j/57.1-1

I believe this issue is due to . According to the buildlog it was using ant_1.9.7-1 which contained that bug. The new revision 1.9.7-2 is uploaded, hope it works. And I believe IBM's copyright has been covered by the first section in d/copyright? ``` Files: *

Bug#819188: RFS: icu4j/57.1-1

Hi Gianfranco, I've added sections for Google and Unicode Inc. to d/copyright and uploaded it to mentors.debian.net. Could you please take a look again? Thank you! Since this package is maintained by pkg-java team, I don't know if it is appropriate to file this RFS outside of the team. If you

Bug#819074: point gradle to plugins

I have updated the package to 2.0.0 and also tweaked it a little bit: 1. Install Maven artifacts into /usr/share/maven-repo 2. Auto-generate POMs using Gradle Thus, by adding Debian's maven-repo into the build scripts and change the Android plugin's classpath version to either "2.0.0" or

Bug#832590: ITP: android-platform-external-jsilver -- Pure-Java implementation of Clearsilver

Package: wnpp Severity: wishlist * Package name: android-platform-external-jsilver Version : 6.0.0+r55 * Upstream Author : Google * License : Apache-2.0 * Programming lang: Java * Description : Pure-Java implementation of Clearsilver * URL :

Bug#819074: [Android-tools-devel] Bug#819074: point gradle to plugins

All built-in plugins are included in the Gradle project, it does not need to download the plugins when using. But one still needs to download custom plugins. Before gradle-debian-helper, packages in Debian also needs to specify the local Maven repo URL. I think it would be a bad idea to

Bug#832518: ITP: jacoco -- Free code coverage library for Java

Package: wnpp Severity: wishlist * Package name: jacoco Version : 0.7.7-1 * Upstream Author : EclEmma * License : EPL-1.0 * Programming lang: Java * Description : Free code coverage library for Java * URL : http://www.eclemma.org/jacoco * Alioth :

Bug#833998: ITP: uncommons-maths -- Maths library for Java

Package: wnpp Severity: wishlist * Package name: uncommons-maths Version : 1.2.3-1 * Upstream Author : Daniel W. Dyer * License : Apache-2.0 * Programming lang: Java * Description : Maths library for Java * URL : http://maths.uncommons.org * Alioth :

Bug#833566: ITP: android-platform-external-doclava -- Custom Javadoc doclet by Google

Package: wnpp Severity: wishlist * Package name: android-platform-external-doclava Version : 6.0.1+r55-1 * Upstream Author : Google * License : Apache-2.0 * Programming lang: Java * Description : Custom Javadoc doclet by Google * URL :

Bug#798794: Exception in thread "main" java.awt.AWTError

This bug can be seen if you run "draw9patch" of Android SDK even if you installed default-jdk & libawk-wrapper-java. By following a thread [1] on Ask Ubuntu I successfully run "draw9patch". The workaround is: Uncomment ``` assistive_technologies=org.GNOME.Accessibility.AtkWrapper``` in file .

Bug#832108: ITP: android-platform-frameworks-data-binding -- Data Binding Library for Android

Package: wnpp Severity: wishlist * Package name: android-platform-frameworks-data-binding Version : 2.0.0-1 * Upstream Author : The Android Open Source Project * License : Apache-2.0 * Programming lang: Java * Description : Data Binding Library * URL :

Bug#852903: android-platform-tools-swt: FTBFS: ProfileProvider.java:92: error: cannot find symbol

`hasUpperCaseCharacter()` has been removed from android-platform-tools-base 2.2.2, and android-platform-tools-swt is already abandoned by upstream. Therefore I have no intention to fix this bug at the moment. android-sdk-meta does not depend on this package either, so removng it won't affect

Bug#855262: Set System Encoding as UTF-8

Package: gradle-debian-helper Version: 1.5.1 Severity: wishlist On Debian Buildd the default encoding on Java is usually not UTF-8, which results in compilation failure on source files containing CJK symbols or even a "©". Currently we need to add `-Dfile.encoding=UTF-8` to

Bug#855861: ITP: libscout -- Third-party libraries detector for Android apps

Package: wnpp Severity: wishlist * Package Name: libscout * Version : 0.0~git20161124~dcd2a9e-1 * Upstream Author : Erik Derr * License : EPL-1.0 * Programming Lang: Java * Description : Third-party libraries detector for Android apps * URL

Bug#855270: ITP: wala -- Static analysis on Java bytecode and related languages

Package: wnpp Severity: wishlist * Package Name: wala * Version : 1.3.9-1 * Upstream Author : IBM Corporation * License : EPL-1.0 * Programming Lang: Java * Description : Static analysis on Java bytecode and related languages * URL : http://wala.sourceforge.net

Bug#855274: ITP: smali-1 -- assembler/disassembler for Android's dex format

Package: wnpp Severity: wishlist * Package Name: smali-1 * Version : 1.4.2-1 * License : BSD-3-clause * Programming Lang: Java * Description : assembler/disassembler for Android's dex format * URL : https://github.com/JesusFreke/smali * Alioth :

Bug#856386: android-debian-helper -- Helper Tools for Building Android Apps Using Debian's Android SDK

Package: wnpp Severity: wishlist * Package Name: android-debian-helper * Version : 0.1 * License : Apache-2.0 * Programming Lang: Java * Description : Helper Tools for Building Android Apps Using Debian's Android SDK * Alioth :

Bug#819869: nvidia-legacy-check: lock during install

I can confirm this bug. Whenever I install this package, it stuck at "unpacking" stage forever. Seems there's a problem in the pre-installation script.

Bug#819869: nvidia-legacy-check: lock during install

This is not the problem of debconf. After dpkg started unpacking the package it froze, and some mimutes later the terminal gave "NMI watch dog soft lockup" errors. I added "acpi=off" to GRUB boot options and I succeeded in installing this package. Before turning off ACPI, runing "lspci" always

Bug#836391: gradle: recent update of jsch to version 0.1.54 breaks Gradle based projects

We did a binary upload to Debian, but seems that Ubuntu syncs the packages by source and builds them again. I think someone at the Ubuntu side should do a binary upload to e.g. 2.13-4ubuntu1. I filed a bug about this to Launchpad.

Bug#838753: arm64 Does Not Seem to Be Supported

Package: qemubuilder Version: 0.81 Severity: important When I was creating an image for arm64, qemubuilder complained that arm64 does not seem to be supported. I used the kernel image extracted from `linux-image-4.7.0-1-arm64`, and initrd from

Bug#839832: ITP: android-platform-tools-swt -- Android SDK GUI utilities using SWT

Package: wnpp Severity: wishlist * Package name: android-platform-tools-swt Version : 2.0.0-1 * Upstream Author : The Android Open Source Project * License : Apache-2.0 * Programming lang: Java * Description : Android SDK GUI utilities using SWT * URL :

Bug#840317: Please Separate CLI, GUI and Library Packages

Source: proguard Version: 5.3-1 Severity: wishlist Currently src:proguard builds a single pkg:proguard package providing both the GUI, CLI programs, the Gradle plugin and the library. Since Gradle depends on Progaurd's library, even if a package build-depends on default-jdk-headless it still

Bug#837882: Gradle Fails to Load Its pom.xml

Package: libpolyglot-maven-java Version: 0.8~tobrien+git20120905-3 Severity: important Executing a simple Gradle script that declares the dependency on "pmaven-common.jar": ``` apply plugin: 'java' repositories { maven { url '/usr/share/maven-repo' } } dependencies { compile

Bug#837873: Please Provide Development Packages lib7z0 & lib7z-dev

Source: p7zip Version: 16.02+dfsg-1 Severity: wishlist In Android 7, the AOSP-forked libunwind compiles against lib7z.so and its header files. Could you please provide separated packages for them?

Bug#837873: Headers Needed by android-platform-external-libunwind

The header files needed when building android-platform-external-libunwind includes: * 7zCrc.h * 7zTypes.h * Sha256.h * Xz.h * XzCrc64.h

Bug#838542: [Android-tools-devel] Bug#838542: Bug#838542: android-platform-system-core: profile build does not actually work

src:android-platform-build also has build-profiles, which eliminates the circular dependency. Beyond Nougat, this circular dependency would be removed since android-platform-build-headers are no longer needed. Out of topic here: Build-profiles are pretty good ways to deal with bootstrapping

Bug#838542: [Android-tools-devel] Bug#838542: android-platform-system-core: profile build does not actually work

Hi Wookey, Thanks for your bug report! I have spotted the issue and fixed it in VCS. Please see: . libunwind and safe-iop are indeed needed in stage1, as well as pandoc (I guess you had typos?).

Bug#838033: Please Switch to libandroid-json-java from dusty libandroid-json-org-java

Source: closure-compiler Version: 20130227+dfsg1-8 Severity: minor This package build-depends on libandroid-json-org-java which is very old. libandroid-json-java is part of src:android-platform-libcore [1] which is actively maintained and part of the Android SDK packaging force. Please consider

Bug#838034: Please Switch to libandroid-json-java from Dusty libandroid-json-org-java

Source: zabbix Version: 1:3.0.4+dfsg-1 Severity: minor This package build-depends on libandroid-json-org-java which is very old. libandroid-json-java is part of src:android-platform-libcore [1] which is actively maintained and part of the Android SDK packaging force. Please consider switching

Bug#839053: ITP: android-platform-system-tools-aidl -- Bindings generator of AIDL interfaces

Package: wnpp Severity: wishlist * Package name: android-platform-system-tools-aidl Version : 1:7.0.0+r1 * Upstream Author : The Android Open Source Project * License : Apache-2.0 * Programming lang: C++ * Description : Bindings generator of AIDL interfaces * URL

Bug#811053: *.poms Should Not Be Required to Ensure Trailing Newline

I can definitely reproduce this bug in src:android-platform-libcore . I guess this bug only appears if your package uses bare maven-repo-helper wthout Maven or maven-debian-helper?

Bug#841491: Inject A Task for Generating Maven POMs

Package: gradle-debian-helper Version: 1.3 Severity: wishlist By default a Gradle project does not contain any Maven POMs which are important metadata for a Java package in Debian. So far I have been writing custom tasks [1] for my packages in order to let Gradle generate the POMs, as I don't

Bug#844021: libnative-platform-java 0.11-4 is not compatible with programs built with 0.10*

Control: tags -1 moreinfo Gradle 3.1 is now uploaded, looks like this bug is fixed?

Bug#845606: The Bytecode Should Not Be Targeting Java 1.2

Package: libasm-java Version: 5.1-1 Severity: important The current package of libasm-java contains classes that targets the ancient Java 1.2 where generics is not supported. When I was building a package for Jack (Java Android Compiler Kit) which uses the generics code in ASM, it yielded the

Bug#811053: *.poms Should Not Be Required to Ensure Trailing Newline

Actually, not all programs think `debian/libandroid-dex-java.poms` has a trailing new line. Inside the text, it is like: `line1\n` While the version without trailing new line would be: `line1` So some program considers this file has one line regardless the trailing new line. And the bug is,

Bug#844021: libnative-platform-java 0.11-4 is not compatible with programs built with 0.10*

Hi Vincent, FYI, there's been a patch [1] in gradle/3.1-1 which disable the buildSrc test during the build. It's this test who causes FTBFS [1]: https://anonscm.debian.org/cgit/pkg-java/gradle.git/tree/debian/patches/disable_buildSrc_tests.patch?h=debian/3.1-1

  1   2   3   >