Bug#963058: [Android-tools-devel] Bug#963058: still ftbfs on arm64

[殷啟聰 | Kai-Chung Yan]

It looks like upstream does not support anything but x86, and they've added 
assembly code.  So unless someone steps up to port that to ARM, the ARM 
binaries will be removed.



Curiously, the master branch of AOSP SDK now seems to support ARM64: 
https://ci.android.com/builds/submitted/7058119/sdk_arm64-sdk/latest



OpenPGP_signature
Description: OpenPGP digital signature

Bug#960897: Update android-platform-external-libunwind and build for ppc64el

[殷啟聰 | Kai-Chung Yan]

> According to the source trees at both 
> https://github.com/Unity-Technologies/android-libunwind and 
> https://android.googlesource.com/platform/external/libunwind/, ppc64[le] 
> systems are supported.  

I doubt it. Android never officially supported architectures other than x86, 
ARM or MIPS. And these days MIPS support is being removed. The source tree for 
PowerPC is probably from the original `libunwind` and never touched by Google.

Even if it builds successfully in PowerPC, I'm quite sure it was never tested.



signature.asc
Description: OpenPGP digital signature

Bug#933264: gradle: update SID version to new version?

[殷啟聰 | Kai-Chung Yan]

Newer version of Gradle requires Kotlin, which is being worked on right now. 
See https://java-team.pages.debian.net/gsoc-kotlin-blog



signature.asc
Description: OpenPGP digital signature

Bug#931215: many well known Android devices not supported

[殷啟聰 | Kai-Chung Yan]

Control: severity -1 wishlist

> You raised the severity of this bug to serious.

I think that was by mistake. Since this is a "metabug", I am now giving it a 
`wishlist`.



signature.asc
Description: OpenPGP digital signature

Bug#924591: this requires linking in libsparse, which is from Android sources

[殷啟聰 | Kai-Chung Yan]

> So your choice --- we can either reassign this bug back to fastboot or
> android-sdk-platforms-tools, or I can downgrade the severity of this
> bug for e2fsprogs down to wishlist[1].  Let me know how you want to
> handle this.

I would say downgrade it for the moment. We can deal with it after Buster.

Indeed this is quite tricky. I agree that `e2fsprogs` shouldn't depend on 
`libsparse`. I like the `dlopen` approach but it increases the maintenance 
burden a little bit. But anyway I am too mentally tired of yet another AOSP 
fork making into Debian's archive...



signature.asc
Description: OpenPGP digital signature

Bug#915144: Restrict Tar to at least 1.29b for `--verbatim-files-from`

[殷啟聰 | Kai-Chung Yan]

Package: pristine-tar
Version: 1.45
Severity: normal

I was checking out the tarball on Debian/kFreeBSD and got the following error:

```
seamlik@debian:~/Documents/debian/android-platform-system-core$ pristine-tar 
checkout ../android-platform-system-core_8.1.0+r23.orig.tar.xz 
tar: unrecognized option '--verbatim-files-from'
Try 'tar --help' or 'tar --usage' for more information.
pristine-tar: command failed: tar cf 
/tmp/pristine-tar.nwyer_kTay/recreatetarball --owner 0 --group 0 
--numeric-owner -C /tmp/pristine-tar.nwyer_kTay/workdir --no-recursion --mode 
0644 --verbatim-files-from --files-from /tmp/pristine-tar.nwyer_kTay/manifest
pristine-tar: failed to generate tarball
```

And on kFreeBSD Tar is only in 1.28 which does not support 
`--verbatime-files-from`.



signature.asc
Description: OpenPGP digital signature

Bug#859195: Assigning the "fixed" version

[殷啟聰 | Kai-Chung Yan]

Control: fixed -1 1:8.1.0+r23-1~stage1

This bug seems to be caused by 2 SSL patches which were removed in the Oreo 
upload. For more info please see the report by Bernhard Übelacker at 
.



signature.asc
Description: OpenPGP digital signature

Bug#913785: ITP: android-platform-art -- Android Runtime Utilities

[殷啟聰 | Kai-Chung Yan]

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#913551: [build-rdeps] Provide an option to grep user-defined component

[殷啟聰 | Kai-Chung Yan]

Package: devscripts
Version: 2.18.4
Severity: wishlist

The default behavior is to grep `main` `contrib` `non-free`, but Ubuntu has a 
different set of components. Without an option to specify user-defined 
components, `build-rdeps` can't grep the whole Ubuntu archive.

There is a downstream bug at Launchpad 
.



signature.asc
Description: OpenPGP digital signature

Bug#859195: *** Error in `adb': free(): invalid pointer: 0x81fa9590 ***

[殷啟聰 | Kai-Chung Yan]

Control: tags -1 unreproducible

`adb shell` works for me. Can you reproduce the problem?

I believe it was an incompatibility between upstream libssl and ADB. We now use 
BoringSSL instead.



signature.asc
Description: OpenPGP digital signature

Bug#802469: android-tools-adb: adb client cannot setup server to listen on tcp transport via -a option

[殷啟聰 | Kai-Chung Yan]

Control: tags -1 moreinfo

ADB from Android Oreo defaults to start the daemon on a TCP socket. I suppose 
this bug report no longer applies?



signature.asc
Description: OpenPGP digital signature

Bug#759611: android-tools-fastboot: fastboot fails to detect device over USB3.0

[殷啟聰 | Kai-Chung Yan]

`fastboot` has been updated since. Can you still reproduce the problem?



signature.asc
Description: OpenPGP digital signature

Bug#738128: android-tools-adb: adb server locks out subsequent users by using common unix-domain socket location without cleanup

[殷啟聰 | Kai-Chung Yan]

ADB is now updated to Oreo release, and I just tested `start-server` regarding 
your report.

> "adb start-server" starts the adb service with a unix-domain socket by
> default (local:5037 maps to /tmp/5037).  This is potentially a risky
> process (e.g. like the symlink attack from the logfile mentioned in
> #688280). 

I don't see any mapped file created under `/tmp` any more. I believe this 
behavior is changed by now.

> In addition to being risky, adb does not clean up its unix-domain
> socket when it shuts down, but leaves the socket in place.

What I can confirm is that after I run `adb kill-server` the 5037 TCP port is 
no longer listened.

Can anyone else confirm on the problem again?



signature.asc
Description: OpenPGP digital signature

Bug#911322: Please link fastboot with system libraries

[殷啟聰 | Kai-Chung Yan]

Control: tags -1 wontfix
Control: severity -1 wishlist

I will just keep this bug open so people with similar confusion will see this.



signature.asc
Description: OpenPGP digital signature

Bug#893368: fastboot too old

[殷啟聰 | Kai-Chung Yan]

> /nexus5x-bullhead-install/bullhead-opm3.171019.016$ ./flash-all.sh 
> fastboot too old
> 
> ie. the latest Android Google Nexus factory images cannot be flashed.

Thanks for the report. Now that `fastboot` has been updated to Oreo release, is 
it still too old? Please let me know if you find the problem fixed.



signature.asc
Description: OpenPGP digital signature

Bug#858764: adb shell crashes with invalid pointer error

[殷啟聰 | Kai-Chung Yan]

> the command `adb shell` crashes with the following error:
> 
> $ adb shell
> * daemon not running. starting it now on port 5037 *
> *** Error in `adb': free(): invalid pointer: 0x5653aea7bba0 ***

Thanks for the report.

ADB has been updated to Oreo release, and I can't reproduce the problem. It 
runs perfectly on my system. So if you don't mind, I would like to close the 
bug in a couple of days.



signature.asc
Description: OpenPGP digital signature

Bug#912421: RM: android-platform-system-core [mipsel mips mips64el] -- NBS; stopped building on mips*

[殷啟聰 | Kai-Chung Yan]

Control: retitle -1 RM: android-libadb-dev android-libadb adb fastboot [mipsel 
mips mips64el] -- NBS; not built on mips* anymore

Thanks Mattia. I added the "RM:" back, now it looks a bit better. :)



signature.asc
Description: OpenPGP digital signature

Bug#912421: RM: android-platform-system-core [mipsel mips mips64el] -- NBS; stopped building on mips*

[殷啟聰 | Kai-Chung Yan]

Thanks for the report.

In fact `android-libadb-dev`, `android-libadb`, `adb` and `fastboot` are no 
longer built on MIPS architectures, so please remove them and them only. Other 
packages build fine on MIPS for now.

I'm not sure how to specify a removal of binary packages on the bug system 
though. Can we retitle the bug to a list of binary packages?



signature.asc
Description: OpenPGP digital signature

Bug#911322: [Android-tools-devel] Bug#911322: Please link fastboot with system libraries

[殷啟聰 | Kai-Chung Yan]

> All of these already exist in the archive: libselinux1, libsepol1, libunwind8

That is because AOSP has forked those projects and added something else to the 
code, which many components of Android SDK need. As a result, the upstream 
version of those libraries are not compatible any more.

There are also other third-party libraries our packages use, like lib7z. As 
long as the upstream version is compatible, we will use the upstream one.

Merging those AOSP changes is unwise since the developers never intended to 
even maintain the API stability. That's why we always update the packages so 
they are the same upstream version and the ABI version in their SONAME is 
always "0". They will do it themselves when they decide to (for example [1]).

[1]: 
https://github.com/tytso/e2fsprogs/commit/db6f320912cfde97be9bf108997db1e85e323de7#diff-a31e97167f71125b93d46819fd0238b3



signature.asc
Description: OpenPGP digital signature

Bug#911322: [Android-tools-devel] Bug#911322: Please link fastboot with system libraries

[殷啟聰 | Kai-Chung Yan]

> Any reasons why fastboot is linked againt the bundled libraries of
> android?

Those libraries (e.g. liblog, libutils) are used by Android SDK only and not 
for general use, and due to their generic SONAME it would be unwise to put them 
in `/usr/lib`, so we put them in a dedicated directory.

> Please link against the system libraries.

What do you mean? `fastboot` and all other Android SDK components use the 
system libraries, for example `glibc` and `pthread`.



signature.asc
Description: OpenPGP digital signature

Bug#911262: fastboot: no fastboot version 8 in experimental

[殷啟聰 | Kai-Chung Yan]

There is an circular dependency between `android-platform-system-core` and 
`android-platform-system-extras` and the way we solve it is to do staged 
uploads on `android-platform-system-core`. `fastboot` is disable on stage1, and 
we will bring it back in a full upload soon.



signature.asc
Description: OpenPGP digital signature

Bug#909949: RFS: android-platform-system-extras/8.1.0+r23-1 (experimental)

[殷啟聰 | Kai-Chung Yan]

Hello Roger,

> 
> The problem is you didn't mention +ds or +repack in version in d/changelog.
> I guess the version need to be changed to 8.1.0+r23+ds-1 or 
> 8.1.0+r23+repack-1.
> 
> Cheers,
> 

Truth to be told, almost all packages in Debian are "repacked" either by 
applying a different compression (ZIP to TARXZ) and/or stripping out 
incompatible/unnecessary files. And as a result, almost all packages would have 
had a "+repackXX" in the version strings, which is quite unnecessary. The 
Android Tools team does not have such tradition of adding that suffix.

I repacked it manually because `uscan` (or specifically `mk-origtargz`) failed 
to do so with an error, which happens on many of our packages. It was reported 
[1] but seems the fault is on `tar`. Hans probably didn't bother to do it so he 
simply imported the original tarball anyway...

Additionally, 8.1.0+r23 is never uploaded to the archive, so adding a 
"+repackXX" suffix isn't really mandatory.

[1]: https://bugs.debian.org/831870



signature.asc
Description: OpenPGP digital signature

Bug#898705: [Android-tools-devel] Bug#898705: android-platform-libcore 8.1 upload to unstable?

[殷啟聰 | Kai-Chung Yan]

I am going to upload the Oreo version of src:android-platform-libcore to 
`unstable` on 9 October if no one objects.

The Oreo (8.x) of this package only builds `android-platform-libcore-headers` 
and `libandroid-json-java` so the majority of the SDK don't really rely on this 
source package any more. Besides, the majority of the SDK is already removed 
from `testing`...



signature.asc
Description: OpenPGP digital signature

Bug#909949: RFS: android-platform-system-extras/8.1.0+r23-1 (experimental)

[殷啟聰 | Kai-Chung Yan]

Thanks for the sponsor again, Roger!

I did push the changes already, check 
.

Or do you mean you want a dedicated merge request so you can leave comments 
their so that in a more sophisticated way? That's probably not viable...



signature.asc
Description: OpenPGP digital signature

Bug#909949: RFS: android-platform-system-extras/8.1.0+r23-1 (experimental)

[殷啟聰 | Kai-Chung Yan]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "android-platform-system-extras"

* Package name: android-platform-system-extras
  Version : 8.1.0+r23-1
  Upstream Author : Android Open Source Project
* URL : https://android.googlesource.com/platform/system/extras
* License : Apache-2.0
  Section : devel

It builds those binary packages:

* android-libext4-utils - Android ext4 utility library
* android-libext4-utils-dev - Android ext4 utility library - Development files
* android-libf2fs-utils - Android F2FS utility library
* android-libf2fs-utils-dev - Android F2FS utility library - Development files
* android-sdk-ext4-utils - Android ext4-utils tools (new package, hence the 
need for sponsor)

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/android-platform-system-extras

Alternatively, one can download the package with dget using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/a/android-platform-system-extras/android-platform-system-extras_8.1.0+r23-1.dsc

This upload will enable us to update fastboot to 8.1.0.

Changes since the last upload:

[ Hans-Christoph Steiner ]
* New upstream release
* d/copyright: Use HTTPS URLs
* Switch to Salsa

[ Saif Abdul Cassim ]
* New package android-sdk-ext4-utils providing:
  * mkuserimg
  * ext4fixup
  * make_ext4fs
  * This package is replacing the obsolete android-tools-fsutils

[ Kai-Chung Yan ]
* Debhelper level => 11
* d/rules: Use dh-auto-build instead of plain make thanks to Helmut Grohne
* Fix the conflicting types errors (Closes: #892170)
* Standards-Version => 4.2.1

Regards,
殷啟聰 | Kai-Chung Yan



signature.asc
Description: OpenPGP digital signature

Bug#905820: android-platform-external-boringssl: Incomplete debian/copyright?

[殷啟聰 | Kai-Chung Yan]

> Uploaded; thanks! Please address the Lintian errors on the next upload,
> mind you...

Thanks for the upload. Already fixed the error now, don't know why Lintian 
never told me about that...



signature.asc
Description: OpenPGP digital signature

Bug#909305: RFS: android-platform-system-core/1:8.1.0+r23-1~stage1.1

[殷啟聰 | Kai-Chung Yan]

> Yes, but for case of ~stageX in version, you need to just change 1
> byte or 2 to comfort lintian.
> Why not?

Maybe a new versioning scheme would be better, for example, 
"1:8.1.0+r23-1~stage1+revision1". The current one is indeed not ideal.
> This time seems OK for mips*
> - 
> http://debomatic-mips.debian.net/distribution#experimental/android-platform-system-core/8.1.0+r23-1~stage1.2/buildlog
> - 
> http://debomatic-mipsel.debian.net/distribution#experimental/android-platform-system-core/8.1.0+r23-1~stage1.2/buildlog
> - 
> http://debomatic-mips64el.debian.net/distribution#experimental/android-platform-system-core/8.1.0+r23-1~stage1.2/buildlog

Yep it's finally building. Thanks for uploading! Just got the uploading 
permission for the package, would be smoother to handle it in the future.



signature.asc
Description: OpenPGP digital signature

Bug#909305: RFS: android-platform-system-core/1:8.1.0+r23-1~stage1.1

[殷啟聰 | Kai-Chung Yan]

Hello Roger,
> -1~stageX means preparing version -1.

Well, it means preparing a version that is earlier than -1. 
> Hope you can address some lintian on next upload:
> - 
> http://debomatic-armel.debian.net/distribution#experimental/android-platform-system-core/8.1.0+r23-1~stage1.1/lintian

Most of the Lintian warnings are too trivial and of low priority. Getting the 
Oreo SDK ready as fast as possible is my current goal. But there are some 
warnings that are actually false-positive, e.g. hardening and ldcondif-trigger. 
We only override "E" tags and leave the rest as is so they serve as a reminder 
of such bugs from the build-tools.

> 
> Just uploaded to experimental.

Thank you for the sponsor!

Alas, MIPS still FTBFS... I finally fixed the bug and tested it on mips64el. 
Could you please upload it once again? It should be on the same URL on 
. Thanks!



signature.asc
Description: OpenPGP digital signature

Bug#909305: RFS: android-platform-system-core/1:8.1.0+r23-1~stage1.1

[殷啟聰 | Kai-Chung Yan]

Hello Roger! 
> I just quickly checked the version on salsa, and find d/changelog is
> not uploaded yet.

I was planning to push the changes to Salsa after it gets uploaded. I just did 
it a while ago.

> So could you change the version to 1:8.1.0+r23-1~stage2 ?

No, we will stick with this version. This release isn't a stage2 one but a fix 
for the previous release, which FTBFS on armel and MIPS family.



signature.asc
Description: OpenPGP digital signature

Bug#909305: RFS: android-platform-system-core/1:8.1.0+r23-1~stage1.1

[殷啟聰 | Kai-Chung Yan]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "android-platform-system-core"

* Package name: android-platform-system-core
  Version : 1:8.1.0+r23-1~stage1.1
  Upstream Author : Android Open Source Project
* URL : https://android.googlesource.com/platform/system/core
* License : Apache-2.0
  Section : devel

It builds those binary packages:

 adb   - Android Debug Bridge
 android-libadb - Library for Android Debug Bridge
 android-libadb-dev - Library for Android Debug Bridge - Development files
 android-libbacktrace - Android backtrace library
 android-libbacktrace-dev - Android backtrace library - Development files
 android-libbase - Android base library
 android-libbase-dev - Android base library - Development files
 android-libcrypto-utils - Android crypto-utils library
 android-libcrypto-utils-dev - Android crypto-utils library - Development files
 android-libcutils - Android utils library for C
 android-libcutils-dev - Android utils library for C - Development files
 android-liblog - Android NDK logger interfaces
 android-liblog-dev - Android NDK logger interfaces - Development files
 android-libsparse - Library for sparse files
 android-libsparse-dev - Library for sparse files - Development files
 android-libutils - Android Utility Function Library
 android-libutils-dev - Android Utility Function Library - Development files
 android-libziparchive - Library for ZIP archives
 android-libziparchive-dev - Library for ZIP archives - Development files
 android-platform-system-core-headers - Shared headers in AOSP repository 
platform/system/core
 android-sdk-libsparse-utils - Android sparse image creation tool
 android-tools-adb - transitional package
 android-tools-fastboot - transitional package
 android-tools-mkbootimg - transitional package
 append2simg - Transitional package
 img2simg   - Transitional package
 mkbootimg  - Creates Android boot images
 simg2img   - Transitional package

To access further information about this package, please visit the following 
URL:

https://mentors.debian.net/package/android-platform-system-core

Changes since the last upload:

  * Do not build anything depending on BoringSSL when building on MIPS
* Do not build-depend on Pandoc or libusb when building on MIPS
  * Standards-Version => 4.2.1
  * libadb: Link against libatomic so that the build won't fail on armel

You can find more changes at 
.


Regards,
Kai-Chung Yan



signature.asc
Description: OpenPGP digital signature

Bug#906134: RFS

[殷啟聰 | Kai-Chung Yan]

Hello Jason,

I am not a DD, but this thread might seem inappropriate to appear as a 
"sponsorship-requests" bug. How about posting it to debian-mentors [1] and then 
closing this bug?

[1]: https://lists.debian.org/debian-mentors



signature.asc
Description: OpenPGP digital signature

Bug#905820: android-platform-external-boringssl: Incomplete debian/copyright?

[殷啟聰 | Kai-Chung Yan]

> No, sorry, please provide a HTTP-accessible link to .dsc with all the
> sources, etc. Just like a regular sponsor request…

I understand now, sorry I haven't used that procedure for a long time...

Here it is: 
https://mentors.debian.net/package/android-platform-external-boringssl

And the link to the DSC is: 
https://mentors.debian.net/debian/pool/main/a/android-platform-external-boringssl/android-platform-external-boringssl_8.1.0+r23-2.dsc



signature.asc
Description: OpenPGP digital signature

Bug#905820: android-platform-external-boringssl: Incomplete debian/copyright?

[殷啟聰 | Kai-Chung Yan]

Hello Chris,

> Sorry, please provide a .dsc; I am very busy, alas...

Understood...

I have attached the .buildinfo, .dsc and .changes files, hopefully they are 
sufficient?
Format: 3.0 (quilt)
Source: android-platform-external-boringssl
Binary: android-libboringssl, android-libboringssl-dev
Architecture: armel armhf arm64 amd64 i386 ppc64el
Version: 8.1.0+r23-2
Maintainer: Android Tools Maintainers 

Uploaders: Kai-Chung Yan 
Homepage: https://android.googlesource.com/platform/external/boringssl
Standards-Version: 4.2.1
Vcs-Browser: 
https://salsa.debian.org/android-tools-team/android-platform-external-boringssl
Vcs-Git: 
https://salsa.debian.org/android-tools-team/android-platform-external-boringssl.git
Build-Depends: debhelper (>= 11), dh-exec
Package-List:
 android-libboringssl deb libs optional 
arch=armel,armhf,arm64,amd64,i386,ppc64el
 android-libboringssl-dev deb libdevel optional 
arch=armel,armhf,arm64,amd64,i386,ppc64el
Checksums-Sha1:
 97fae12ac5fbec3282eb17f5d00543e14c094811 20346200 
android-platform-external-boringssl_8.1.0+r23.orig.tar.gz
 10393ba6868a536c9a1d9a0953db8f1e901dc156 7668 
android-platform-external-boringssl_8.1.0+r23-2.debian.tar.xz
Checksums-Sha256:
 51eb22c5f68ce49e35a1726623a257e8e89b29c23bf374a3420a8ac88afe2078 20346200 
android-platform-external-boringssl_8.1.0+r23.orig.tar.gz
 84873533e9be896bb1e252722edb91471fe71e7e018222d9e7669262fda57ec5 7668 
android-platform-external-boringssl_8.1.0+r23-2.debian.tar.xz
Files:
 cdc934e3446620108599fa3870c4c103 20346200 
android-platform-external-boringssl_8.1.0+r23.orig.tar.gz
 6fe74238b3fe7a8bcc75f3626bbed99b 7668 
android-platform-external-boringssl_8.1.0+r23-2.debian.tar.xz
Format: 1.0
Source: android-platform-external-boringssl
Binary: android-libboringssl android-libboringssl-dev
Architecture: source
Version: 8.1.0+r23-2
Checksums-Md5:
 a2d3c17ee2c770c5b3aef455fa03d89d 1559 
android-platform-external-boringssl_8.1.0+r23-2.dsc
Checksums-Sha1:
 fb64107b1154cb4e6a9d880c69e83e03ea13fb35 1559 
android-platform-external-boringssl_8.1.0+r23-2.dsc
Checksums-Sha256:
 a33239d1b82852424cec91575ce3796c72a24b5abf6b0aa254ce1501f5fd2309 1559 
android-platform-external-boringssl_8.1.0+r23-2.dsc
Build-Origin: Ubuntu
Build-Architecture: amd64
Build-Date: Fri, 21 Sep 2018 17:34:00 +0800
Installed-Build-Depends:
 autoconf (= 2.69-11),
 automake (= 1:1.16.1-1.1ubuntu1),
 autopoint (= 0.19.8.1-7),
 autotools-dev (= 20180224.1),
 base-files (= 10.1ubuntu6),
 base-passwd (= 3.5.45),
 bash (= 4.4.18-2ubuntu3),
 binutils (= 2.31.1-6ubuntu1),
 binutils-common (= 2.31.1-6ubuntu1),
 binutils-x86-64-linux-gnu (= 2.31.1-6ubuntu1),
 bsdmainutils (= 11.1.2ubuntu2),
 bsdutils (= 1:2.32-0.1ubuntu1),
 build-essential (= 12.5ubuntu2),
 bzip2 (= 1.0.6-9),
 coreutils (= 8.28-1ubuntu1),
 cpp (= 4:8.2.0-1ubuntu1),
 cpp-8 (= 8.2.0-7ubuntu1),
 dash (= 0.5.8-2.10),
 debconf (= 1.5.69),
 debhelper (= 11.3.2ubuntu1),
 debianutils (= 4.8.6),
 dh-autoreconf (= 19),
 dh-exec (= 0.23build1),
 dh-strip-nondeterminism (= 0.042-1),
 diffutils (= 1:3.6-1),
 dpkg (= 1.19.0.5ubuntu5),
 dpkg-dev (= 1.19.0.5ubuntu5),
 dwz (= 0.12-2),
 fdisk (= 2.32-0.1ubuntu1),
 file (= 1:5.34-2),
 findutils (= 4.6.0+git+20180808-2),
 g++ (= 4:8.2.0-1ubuntu1),
 g++-8 (= 8.2.0-7ubuntu1),
 gcc (= 4:8.2.0-1ubuntu1),
 gcc-8 (= 8.2.0-7ubuntu1),
 gcc-8-base (= 8.2.0-7ubuntu1),
 gettext (= 0.19.8.1-7),
 gettext-base (= 0.19.8.1-7),
 grep (= 3.1-2ubuntu1),
 groff-base (= 1.22.3-10),
 gzip (= 1.6-5ubuntu1),
 hostname (= 3.20),
 init-system-helpers (= 1.54),
 install-info (= 6.5.0.dfsg.1-4),
 intltool-debian (= 0.35.0+20060710.4),
 libacl1 (= 2.2.52-3build1),
 libarchive-zip-perl (= 1.63-1),
 libasan5 (= 8.2.0-7ubuntu1),
 libatomic1 (= 8.2.0-7ubuntu1),
 libattr1 (= 1:2.4.47-2build1),
 libaudit-common (= 1:2.8.3-1ubuntu2),
 libaudit1 (= 1:2.8.3-1ubuntu2),
 libbinutils (= 2.31.1-6ubuntu1),
 libblkid1 (= 2.32-0.1ubuntu1),
 libbsd0 (= 0.9.1-1),
 libbz2-1.0 (= 1.0.6-9),
 libc-bin (= 2.28-0ubuntu1),
 libc-dev-bin (= 2.28-0ubuntu1),
 libc6 (= 2.28-0ubuntu1),
 libc6-dev (= 2.28-0ubuntu1),
 libcap-ng0 (= 0.7.9-1),
 libcc1-0 (= 8.2.0-7ubuntu1),
 libcroco3 (= 0.6.12-2),
 libdb5.3 (= 5.3.28+dfsg1-0.1),
 libdebconfclient0 (= 0.213ubuntu1),
 libdpkg-perl (= 1.19.0.5ubuntu5),
 libelf1 (= 0.170-0.5),
 libfdisk1 (= 2.32-0.1ubuntu1),
 libffi6 (= 3.2.1-8),
 libfile-stripnondeterminism-perl (= 0.042-1),
 libgcc-8-dev (= 8.2.0-7ubuntu1),
 libgcc1 (= 1:8.2.0-7ubuntu1),
 libgcrypt20 (= 1.8.3-1ubuntu1),
 libgdbm-compat4 (= 1.14.1-6),
 libgdbm5 (= 1.14.1-6),
 libglib2.0-0 (= 2.58.0-4),
 libgmp10 (= 2:6.1.2+dfsg-3),
 libgomp1 (= 8.2.0-7ubuntu1),
 libgpg-error0 (= 1.32-1),
 libicu60 (= 60.2-6ubuntu1),
 libisl19 (= 0.20-2),
 libitm1 (= 8.2.0-7ubuntu1),
 liblsan0 (= 8.2.0-7ubuntu1),
 liblz4-1 (= 1.8.2-1ubuntu1),
 liblzma5 (= 5.2.2-1.3),
 libmagic-mgc (= 1:5.34-2),
 libmagic1 (= 1:5.34-2),
 libmount1 (= 2.32-0.1ubuntu1),
 libmpc3 (= 1.1.0-1),
 libmpfr6 (= 4.0.1-1),
 libmpx2 (= 8.2.0-7ubuntu1),
 libncursesw6 (= 6.1+20180210-4ubuntu1),
 

Bug#905820: android-platform-external-boringssl: Incomplete debian/copyright?

[殷啟聰 | Kai-Chung Yan]

Hello Chris,
> I will happily sponsor individual uploads if provided with a .dsc but I
> am not in a position to evaluate the DM (I assume?) status.

Then sponsor it is, thanks. I just gave you access to the repository, and 
prepared the changelog. We use the standard git-buildpackage workflow.

> Or, you can ask the rest of your team?

The only actively-involved DD (eighthave) isn't active these days, so had to 
ask you.



signature.asc
Description: OpenPGP digital signature

Bug#905820: android-platform-external-boringssl: Incomplete debian/copyright?

[殷啟聰 | Kai-Chung Yan]

Hello Chris,

I just polished [1] the changelog file and I'm about to upload the fix. Could 
you grant me the upload rights to this package? Thank you.

Cheers,
Kai-Chung Yan

[1]: 
https://salsa.debian.org/android-tools-team/android-platform-external-boringssl/commit/f38e0d39c033508d3eaffe354ebedcac33e74813



signature.asc
Description: OpenPGP digital signature

Bug#896436: gradle FTBFS: error fetching java api url when building with openjdk-10

[殷啟聰 | Kai-Chung Yan]

@ebourg

Shouldn't this be fixed at the `java-common` side instead of here? Switching 
back to `default-jdk` seems like a step back to me.



signature.asc
Description: OpenPGP digital signature

Bug#853310: android-platform-system-core: ftbfs with GCC-7

[殷啟聰 | Kai-Chung Yan]

> Anyway, I sponsored this upload targetting experimental.

Thank you for the sponsor. I am surprised it got cleared in the queue so 
quickly.

There's a FTFBS on MIPS, I think I can handle it.



signature.asc
Description: OpenPGP digital signature

Bug#853310: android-platform-system-core: ftbfs with GCC-7

[殷啟聰 | Kai-Chung Yan]

> Who are the DD in the team? Are there other contributors currently
> following the process to become a DD?

Mostly Hans (eighthave) is the DD involved a lot, and Markus (apo) occasionally 
helps. I am currently going through the process of becoming a DD but it is 
going very slowly.

> It would have helped if you had given me the URL of the repository.
> Anyway, I'm willing to sponsor the update (even though I don't know much
> about Android Tools) but I have a few comments:

Thank you for the sponsor, it will help us a lot!

The repository is at 
. 
Sorry about that, I thought it was too trivial.

> 1/ your RFS mentions the need to do a "stage1" upload but you actually
> manually dropped the package and the build dependencies that were tagged
> stage1, why did you do that?

"stage1" is everything but "fastboot". "fastboot" depends on some libraries in 
"android-platform-system-extras" which also depend on libraries in this source 
package, making a circular dependency. We are going to upload the full version 
after "android-platform-system-extras" gets uploaded.

"buildd" does not support staged uploads, so we have to manually remove 
"fastboot", hence the "~stage1" part of the version.

> 2/ I don't understand why you replace "android-tools-mkbootimg" with
> "mkbootimg". The latter package has a very generic name while the former
> was rather explicit. It looks like a step backwards. Yes, now it matches
> the name of the executable inside the package, but I'm not sure it
> justifies introducing a new package and dealing with a transitional
> package. What was your rationale? And you should have documented your
> rationale in the commit messages and in the changelog entry.

We have renamed "adb" and "fastboot" as well, and we are doing the same for 
"mkbootimg" this time. For the moment, the names of these programs have been 
well-known and exclusive in the society, so I don't think the "android-tools-" 
prefix is necessary. For a name, they seem not that generic to me as I've seen 
something more so (e.g. "docker" and "node", which did caused name conflicts in 
Debian).

Another reason has been mentioned by you: They match the executables.

There are other executables built by this package with names more generic, like 
"img2simg" and "append2simg". We put them together in a single package (as you 
can see in the changelog") because they belong to the same subproject 
"libsparse". Unfortunately "mkbootimg" lives on its own so I just make it its 
own package.



signature.asc
Description: OpenPGP digital signature

Bug#853310: android-platform-system-core: ftbfs with GCC-7

[殷啟聰 | Kai-Chung Yan]

Hello Raphael,

Sorry for being dormant on the matter. We had been in the process of updating 
the whole SDK suite to Oreo but it is blocked by an upload of this package. The 
latest update produces several new packages so I don't have the permission to 
upload it, and the DDs in the team were too busy as well.

It would be wonderful if you could sponsor the upload. We have prepared 
everything on Salsa, all you need to do is to change "UNRELEASED" to 
"experimental" in the changelog. The RFS [1] has more details.

Cheers,
Kai-Chung Yan

[1]: 
https://alioth-lists.debian.net/pipermail/android-tools-devel/2018q3/003388.html



signature.asc
Description: OpenPGP digital signature

Bug#851860: [Android-tools-devel] Bug#851860: Intent to NMU google-android-installers to fix longstanding l10n bugs

[殷啟聰 | Kai-Chung Yan]

Hello Helge,

I am one of the devs at `android-tools` team although I don't maintain the 
contrib installer packages like this. AFAIK Mouaad is MIA after his work in 
GSoC 2016, but I can say he will be fine with the NMU and he is not preparing 
for a new release yet. Please go ahead with your other NMUs on the l10n as well.

Thank you for the contribution!



signature.asc
Description: OpenPGP digital signature

Bug#905836: Uninstallable on a Clean Sid - update-alternatives Fails to Create a Symbolic Link

[殷啟聰 | Kai-Chung Yan]

Package: openjdk-10-jre-headless
Version: 10.0.2+13-1
Severity: grave

This package fails to install on the Docker image "debian:sid-slim". The 
postinst fails to execute successfully. Below is the log:

```
seamlik@zenbook:~$ sudo docker run --rm -it debian:sid-slim bash
[sudo] password for seamlik: 
root@24f6024890b9:/# apt update
Get:1 http://cdn-fastly.deb.debian.org/debian sid InRelease [233 kB]
Get:2 http://cdn-fastly.deb.debian.org/debian sid/main amd64 Packages [8195 kB]
Fetched 8427 kB in 15s (566 kB/s)   
   
Reading package lists... Done
Building dependency tree   
Reading state information... Done
29 packages can be upgraded. Run 'apt list --upgradable' to see them.
root@24f6024890b9:/# apt install openjdk-10-jre-headless
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following additional packages will be installed:
  ca-certificates ca-certificates-java dbus fontconfig-config fonts-dejavu-core 
java-common
  krb5-locales libapparmor1 libavahi-client3 libavahi-common-data 
libavahi-common3 libbsd0
  libcups2 libdbus-1-3 libexpat1 libfontconfig1 libfreetype6 libgssapi-krb5-2 
libjpeg62-turbo
  libk5crypto3 libkeyutils1 libkrb5-3 libkrb5support0 liblcms2-2 libnspr4 
libnss3 libpcsclite1
  libpng16-16 libsqlite3-0 libssl1.1 libx11-6 libx11-data libxau6 libxcb1 
libxdmcp6 libxext6
  libxi6 libxrender1 libxtst6 lsb-base openssl sensible-utils ucf x11-common
Suggested packages:
  default-dbus-session-bus | dbus-session-bus default-jre cups-common krb5-doc 
krb5-user
  liblcms2-utils pcscd libnss-mdns fonts-dejavu-extra fonts-ipafont-gothic 
fonts-ipafont-mincho
  fonts-wqy-microhei | fonts-wqy-zenhei fonts-indic
The following NEW packages will be installed:
  ca-certificates ca-certificates-java dbus fontconfig-config fonts-dejavu-core 
java-common
  krb5-locales libapparmor1 libavahi-client3 libavahi-common-data 
libavahi-common3 libbsd0
  libcups2 libdbus-1-3 libexpat1 libfontconfig1 libfreetype6 libgssapi-krb5-2 
libjpeg62-turbo
  libk5crypto3 libkeyutils1 libkrb5-3 libkrb5support0 liblcms2-2 libnspr4 
libnss3 libpcsclite1
  libpng16-16 libsqlite3-0 libssl1.1 libx11-6 libx11-data libxau6 libxcb1 
libxdmcp6 libxext6
  libxi6 libxrender1 libxtst6 lsb-base openjdk-10-jre-headless openssl 
sensible-utils ucf
  x11-common
0 upgraded, 45 newly installed, 0 to remove and 29 not upgraded.
Need to get 50.1 MB of archives.
After this operation, 210 MB of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 http://cdn-fastly.deb.debian.org/debian sid/main amd64 sensible-utils all 
0.0.12 [15.8 kB]
Get:2 http://cdn-fastly.deb.debian.org/debian sid/main amd64 lsb-base all 
9.20170808 [28.1 kB]
Get:3 http://cdn-fastly.deb.debian.org/debian sid/main amd64 libapparmor1 amd64 
2.13-8 [91.3 kB]
Get:4 http://cdn-fastly.deb.debian.org/debian sid/main amd64 libdbus-1-3 amd64 
1.12.10-1 [211 kB]
Get:5 http://cdn-fastly.deb.debian.org/debian sid/main amd64 libexpat1 amd64 
2.2.5-3 [96.8 kB]
Get:6 http://cdn-fastly.deb.debian.org/debian sid/main amd64 dbus amd64 
1.12.10-1 [233 kB]
Get:7 http://cdn-fastly.deb.debian.org/debian sid/main amd64 krb5-locales all 
1.16-2 [94.7 kB]
Get:8 http://cdn-fastly.deb.debian.org/debian sid/main amd64 ucf all 3.0038 
[67.8 kB]
Get:9 http://cdn-fastly.deb.debian.org/debian sid/main amd64 libssl1.1 amd64 
1.1.0h-4 [1352 kB]
Get:10 http://cdn-fastly.deb.debian.org/debian sid/main amd64 openssl amd64 
1.1.0h-4 [744 kB]  
Get:11 http://cdn-fastly.deb.debian.org/debian sid/main amd64 ca-certificates 
all 20180409 [161 kB]
Get:12 http://cdn-fastly.deb.debian.org/debian sid/main amd64 java-common all 
0.68 [14.3 kB]   
Get:13 http://cdn-fastly.deb.debian.org/debian sid/main amd64 
libavahi-common-data amd64 0.7-4 [122 kB]
Get:14 http://cdn-fastly.deb.debian.org/debian sid/main amd64 libavahi-common3 
amd64 0.7-4 [54.4 kB]
Get:15 http://cdn-fastly.deb.debian.org/debian sid/main amd64 libavahi-client3 
amd64 0.7-4 [57.8 kB]
Get:16 http://cdn-fastly.deb.debian.org/debian sid/main amd64 libkeyutils1 
amd64 1.5.9-9.3 [13.0 kB]
Get:17 http://cdn-fastly.deb.debian.org/debian sid/main amd64 libkrb5support0 
amd64 1.16-2 [62.8 kB]
Get:18 http://cdn-fastly.deb.debian.org/debian sid/main amd64 libk5crypto3 
amd64 1.16-2 [121 kB]   
Get:19 http://cdn-fastly.deb.debian.org/debian sid/main amd64 libkrb5-3 amd64 
1.16-2 [316 kB]  
Get:20 http://cdn-fastly.deb.debian.org/debian sid/main amd64 libgssapi-krb5-2 
amd64 1.16-2 [158 kB]
Get:21 http://cdn-fastly.deb.debian.org/debian sid/main amd64 libcups2 amd64 
2.2.8-5 [322 kB]  
Get:22 http://cdn-fastly.deb.debian.org/debian sid/main amd64 liblcms2-2 amd64 
2.9-2 [145 kB]  
Get:23 http://cdn-fastly.deb.debian.org/debian sid/main amd64 libjpeg62-turbo 
amd64 1:1.5.2-2+b1 [134 kB]
Get:24 http://cdn-fastly.deb.debian.org/debian sid/main amd64 libpng16-16 amd64 
1.6.34-2 [288 kB]  
Get:25 

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

[殷啟聰 | Kai-Chung Yan]

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

[殷啟聰 | Kai-Chung Yan]

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

[殷啟聰 | Kai-Chung Yan]

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

[殷啟聰 | Kai-Chung Yan]

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#899005: Maven POM refers to a non-existing parent

[殷啟聰 | Kai-Chung Yan]

Package: libfindbugs-java
Version: 3.1.0~preview2-3
Severity: important

The Maven POM (installed at 
`/usr/share/maven-repo/com/google/code/findbugs/findbugs/debian/findbugs-debian.pom`
 refers to a parent POM `org.sonatype.oss:oss-parent:debian` which is not 
provided by this package. In fact, this POM is not provided by any package in 
the archive. Gradle projects will fail to resolve the artifact by showing 
errors like:

```
Could not resolve com.google.code.findbugs:findbugs:debian.
  Required by:
  project :codeQuality
   > Could not resolve com.google.code.findbugs:findbugs:debian.
  > Could not parse POM 
/usr/share/maven-repo/com/google/code/findbugs/findbugs/debian/findbugs-debian.pom
 > Could not find org.sonatype.oss:oss-parent:debian.
   Searched in the following locations:
   
file:/usr/share/maven-repo/org/sonatype/oss/oss-parent/debian/oss-parent-debian.pom
   
file:/usr/share/maven-repo/org/sonatype/oss/oss-parent/debian/oss-parent-debian.jar
```



signature.asc
Description: OpenPGP digital signature

Bug#898910: ITP: dd-plist -- Java library for working with property lists

[殷啟聰 | Kai-Chung Yan]

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#898610: Should stop running tests during build as they are for `autopkgtest`

[殷啟聰 | Kai-Chung Yan]

Package: maven-debian-helper
Version: 2.3~exp1
Severity: wishlist

Java team does not have a generalized `autopkgtest` workflow or suite, so I am 
setting it `wishlist` for now.



signature.asc
Description: OpenPGP digital signature

Bug#894290: gradle should raise the source/target level to the minimum supported by the default JDK

[殷啟聰 | Kai-Chung Yan]

Control: reassign -1 gradle-debian-helper 1.6

I would say this is not the fault of Gradle itself, but it the tricks can be 
provided by `gradle-debian-helper`. We shouldn't modify the behavior of the 
build tools too much.

Let's keep the severity as is for now, as FTBFS is quite serious indeed.



signature.asc
Description: OpenPGP digital signature

Bug#895886: testng: jcommander classes not found

[殷啟聰 | Kai-Chung Yan]

Yeah, I misunderstood you too.

Strange, if `htsjdk` does not configure `jcommander` in `maven.rules`, `1.x` 
should have been replaced by `debian` on the fly. Maybe `gradle-debian-helper` 
ignores test classpath?



signature.asc
Description: OpenPGP digital signature

Bug#895886: testng: jcommander classes not found

[殷啟聰 | Kai-Chung Yan]

By `debian/maven.rules` I mean [1]. It's at line 3. This file configures Gradle 
as well.

Gradle understands the relocations, but it won't add it to the build classpath, 
that's why it fails.

[1]: https://sources.debian.org/src/testng/6.9.12-2/debian/maven.rules



signature.asc
Description: OpenPGP digital signature

Bug#895886: testng: jcommander classes not found

[殷啟聰 | Kai-Chung Yan]

Control: tags -1 |confirmed

I relocated `jcommander` from version `1.x` to `debian`, but unfortunately 
Gradle does not recognize Maven artifact relocations.

To fix this, simply remove the line about `jcommander` in `debian/maven.rules`.

Hmm, now I have no idea why it used `1.x` in the first place. (I am not the 
original maintainer)
|


signature.asc
Description: OpenPGP digital signature

Bug#895601: [Android-tools-devel] Bug#895601: simg2img: Please build simg2img and img2simg for other architectures, specifically arm64

[殷啟聰 | Kai-Chung Yan]

I personally agree with enabling other architectures. You never know if there 
are arch-specific bugs if you don't build them. And now that we have LAVA to 
test them for us, which is a win-win.

Bug#847428: Package the Entire "eclipse.jdt.core"

[殷啟聰 | Kai-Chung Yan]

Thank you for this!

However, the Jack & Jill toolchain is deprecated now and we no longer plan to 
package it...



signature.asc
Description: OpenPGP digital signature

Bug#880886: maven-bundle-plugin FTBFS with libmaven-dependency-tree-java

[殷啟聰 | Kai-Chung Yan]

Control:  forwarded -1 https://issues.apache.org/jira/browse/FELIX-5795



signature.asc
Description: OpenPGP digital signature

Bug#880886: maven-bundle-plugin FTBFS with libmaven-dependency-tree-java

[殷啟聰 | Kai-Chung Yan]

forwarded -1 https://issues.apache.org/jira/browse/FELIX-5795



signature.asc
Description: OpenPGP digital signature

Bug#883327: repo: Why is this package in contrib if all of its dependencies are in main?

[殷啟聰 | Kai-Chung Yan]

As far as I know, "repo" clones its code from AOSP with Git and then use the 
downloaded "repo" to do the job. This behavior is similar to a "XXX-installer" 
package, that's why we put it in "contrib".



signature.asc
Description: OpenPGP digital signature

Bug#880886: maven-bundle-plugin FTBFS with libmaven-dependency-tree-java

[殷啟聰 | Kai-Chung Yan]

I removed the javadoc package now and it builds find in Sid. Shall I upload it 
right now?

(I still need the upload permission)



signature.asc
Description: OpenPGP digital signature

Bug#880886: maven-bundle-plugin FTBFS with libmaven-dependency-tree-java

[殷啟聰 | Kai-Chung Yan]

I adopted the patch from Fedora and it looks good. The package builds fine now 
and 154 of its reverse-build-dependencies built successfully. 27 failed:

* activemq-activeio
* activemq
* apache-directory-server
* dnssecjava
* istack-commons
* jackson-datatype-joda
* javassist
* jayway-jsonpath
* jboss-xnio
* jcommander
* jruby
* jsoup
* kryo-serializers
* libcommons-lang3-java
* libhtmlcleaner-java
* libitext5-java
* libpgjava
* libxbean-java
* libxml-security-java
* openhft-chronicle-bytes
* openhft-chronicle-core
* openhft-chronicle-wire
* openhft-lang
* openjpa
* sisu-ioc
* tika
* undertow

They either failed in compilation due to Java 9 or failed in tests. But I would 
say the result is confident enough to prove that the patch works.

However this package fails to build in Sid currently because of Java 9. I 
attached the log. The Maven Javadoc Plugin failed to honor the compile 
classpath.
I: Copying COW directory
I: forking: rm -rf /media/data/VMs/pbuilder/build/cow.29816
I: forking: cp -al /media/data/VMs/pbuilder/default.cow /media/data/VMs/pbuilder/build/cow.29816
I: removed stale ilistfile /media/data/VMs/pbuilder/build/cow.29816/.ilist
I: forking: chroot /media/data/VMs/pbuilder/build/cow.29816 cowdancer-ilistcreate /.ilist 'find . -xdev -path ./home -prune -o \( \( -type l -o -type f \) -a -links +1 -print0 \) | xargs -0 stat --format '%d %i ''
I: Invoking pbuilder
I: forking: pbuilder build --buildplace /media/data/VMs/pbuilder/build/cow.29816 --buildresult /var/cache/pbuilder/result/ --no-targz --internal-chrootexec 'chroot /media/data/VMs/pbuilder/build/cow.29816 cow-shell' /media/data/Documents/debian/maven-bundle-plugin_3.5.0-1.dsc
W: /home/seamlik/.pbuilderrc does not exist
I: Running in no-targz mode
I: using fakeroot in build.
I: pbuilder: network access will be disabled during build
I: Current time: Tue Mar 20 22:40:43 CST 2018
I: pbuilder-time-stamp: 1521556843
I: copying local configuration
W: No local /etc/mailname to copy, relying on /media/data/VMs/pbuilder/build/cow.29816/etc/mailname to be correct
I: mounting /proc filesystem
I: mounting /sys filesystem
I: creating /{dev,run}/shm
I: mounting /dev/pts filesystem
I: redirecting /dev/ptmx to /dev/pts/ptmx
I: Mounting /media/data/VMs/pbuilder/deb
I: policy-rc.d already exists
I: Using pkgname logfile
I: Current time: Tue Mar 20 22:40:43 CST 2018
I: pbuilder-time-stamp: 1521556843
I: Obtaining the cached apt archive contents
I: Copying source file
I: copying [/media/data/Documents/debian/maven-bundle-plugin_3.5.0-1.dsc]
I: copying [/media/data/Documents/debian/maven-bundle-plugin_3.5.0.orig.tar.xz]
I: copying [/media/data/Documents/debian/maven-bundle-plugin_3.5.0-1.debian.tar.xz]
I: Extracting source
dpkg-source: warning: extracting unsigned source package (maven-bundle-plugin_3.5.0-1.dsc)
dpkg-source: info: extracting maven-bundle-plugin in maven-bundle-plugin-3.5.0
dpkg-source: info: unpacking maven-bundle-plugin_3.5.0.orig.tar.xz
dpkg-source: info: unpacking maven-bundle-plugin_3.5.0-1.debian.tar.xz
dpkg-source: info: applying remove_bndlib_spring_support.diff
dpkg-source: info: applying support_plexus_utils_1_5.diff
dpkg-source: info: applying use-changelog-date-as-pom.properties-timestamp.patch
dpkg-source: info: applying maven-archiver3-869361.patch
dpkg-source: info: applying maven3-compatibility.patch
dpkg-source: info: applying 0001-Port-to-current-maven-dependency-tree.patch
I: Installing the build-deps
I: user script /media/data/VMs/pbuilder/build/cow.29816/tmp/hooks/D00deps starting
dpkg-scanpackages: info: Wrote 2 entries to output Packages file.

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Get:1 file:/media/data/VMs/pbuilder/deb ./ InRelease
Ign:1 file:/media/data/VMs/pbuilder/deb ./ InRelease
Get:2 file:/media/data/VMs/pbuilder/deb ./ Release
Ign:2 file:/media/data/VMs/pbuilder/deb ./ Release
Get:3 file:/media/data/VMs/pbuilder/deb ./ Packages
Ign:3 file:/media/data/VMs/pbuilder/deb ./ Packages
Get:3 file:/media/data/VMs/pbuilder/deb ./ Packages
Ign:3 file:/media/data/VMs/pbuilder/deb ./ Packages
Get:3 file:/media/data/VMs/pbuilder/deb ./ Packages
Ign:3 file:/media/data/VMs/pbuilder/deb ./ Packages
Get:3 file:/media/data/VMs/pbuilder/deb ./ Packages
Ign:3 file:/media/data/VMs/pbuilder/deb ./ Packages
Get:3 file:/media/data/VMs/pbuilder/deb ./ Packages
Ign:3 file:/media/data/VMs/pbuilder/deb ./ Packages
Get:3 file:/media/data/VMs/pbuilder/deb ./ Packages [2786 B]
Get:4 http://cdn-fastly.deb.debian.org/debian sid InRelease [241 kB]
Get:5 http://cdn-fastly.deb.debian.org/debian sid/main amd64 Packages.diff/Index [27.9 kB]
Get:6 http://cdn-fastly.deb.debian.org/debian sid/main amd64 Packages 2018-03-20-0828.04.pdiff [29.6 kB]
Get:6 http://cdn-fastly.deb.debian.org/debian sid/main amd64 Packages 2018-03-20-0828.04.pdiff [29.6 kB]
Fetched 298 kB in 8s (37.7 kB/s)
Reading package lists...
Building dependency tree...
Reading state information...
11 packages can be upgraded. Run 'apt list 

Bug#875336: FTBFS with Java 9: _ as identifier

[殷啟聰 | Kai-Chung Yan]

I just tried building it and Groovy was fine enough, but now Gradle 
complains

Theoretically, ALL Gradle packages FTBFS since the current version is too old 
to play with Java 9's fancy version number.



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

[殷啟聰 | Kai-Chung Yan]

Extending the existing "android-platform-system-extras" source package is more 
than sufficient



signature.asc
Description: OpenPGP digital signature

Bug#875336: FTBFS with Java 9: _ as identifier

[殷啟聰 | Kai-Chung Yan]

I recently updated the package to 3.5.0 just to find out the current Groovy 
(2.4.8) does not support Java 9 [1]. Groovy was used by the bootstrapping 
script. Setting source & target to Java 8 doesn't solve the problem either.

[1]: https://github.com/gradle/gradle/issues/2995



signature.asc
Description: OpenPGP digital signature

Bug#892519: ITP: maven-dependency-tree-2 -- Tree-based API for resolution of Maven project dependencies

[殷啟聰 | Kai-Chung Yan]

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#891695: "mh_linkjar" and "mh_installpoms" Do Not Support "--relocate"

[殷啟聰 | Kai-Chung Yan]

Because I was trying to get around with the error of "mh_linkjar" I admit 
that is a wrong attempt.

But never mind, the point is to let all "mh_" sequence support all options in 
"*.poms" files but ignore whatever is irrelevant to them.



signature.asc
Description: OpenPGP digital signature

Bug#880886: maven-bundle-plugin FTBFS with libmaven-dependency-tree-java

[殷啟聰 | Kai-Chung Yan]

This is getting awkward... Maven Bundle Plugin does not only rely on old Maven 
Dependency Tree, but also targets Maven 2.x [1]. What's worse, Maven Dependency 
Tree 2.x also relies on Maven 2.x [2].

I tried building Maven Dependency Tree 2.2 against Maven 3.x and found that it 
uses removed APIs, and that patching it would make a huge code change. Maybe 
someone else would have a better skill than me to do the job, but I simply 
don't think this is a good or sustainable idea...

[1]: 
https://github.com/apache/felix/blob/ae8f8bbeb6ecaae8e2d27824077c5d39c54e54a5/pom.xml#L182
[2]: 
https://github.com/apache/maven-dependency-tree/blob/maven-dependency-tree-2.2/pom.xml#L53



signature.asc
Description: OpenPGP digital signature

Bug#892268: ITP: felix-resolver -- OSGi Resolver implementation by Apache Felix

[殷啟聰 | Kai-Chung Yan]

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#880886: maven-bundle-plugin FTBFS with libmaven-dependency-tree-java

[殷啟聰 | Kai-Chung Yan]

I propose to bring back Maven Dependency Tree 2.x as a new package that 
coexists with its latest version.

Even in the latest (3.5.0) version, Maven Bundle Plugin still uses those 
deprecated APIs in Maven Dependency Tree 2.x. These deprecated APIs have been 
removed from Maven Dependency Tree 3.x. A fix to adapt to the new APIs would be 
non-trivial (and potentially wasting energy of the maintainers), as I have 
tried...

I have reported this issue upstream [1].

P.S.: Rebuilding Maven Bundle Plugin is needed for the "bnd" upgrade, that's 
way I stumbled upon this...

[1]: https://issues.apache.org/jira/browse/FELIX-5795



signature.asc
Description: OpenPGP digital signature

Bug#891695: "mh_linkjar" and "mh_installpoms" Do Not Support "--relocate"

[殷啟聰 | Kai-Chung Yan]

I put this in the .poms:

> debian/pom.xml --no-parent --usj-name=osgi.cmpn 
> --relocate=org.osgi:org.osgi.compendium:debian

The point is to let all mh_ sequences support all options and simply ignore 
anything that's irrelevant to themselves.



signature.asc
Description: OpenPGP digital signature

Bug#891695: "mh_linkjar" and "mh_installpoms" Do Not Support "--relocate"

[殷啟聰 | Kai-Chung Yan]

Package: maven-repo-helper
Version: 1.9.2
Severity: important

If I use "jh_maven_repo_helper" and then add a "relocate" option to 
".poms", "mh_linkjar" shows the following error:

> Invalid option: relocate

So I move the "relocate" option to "debian/rules" as

```make
override_mh_installpoms:
    mh_installpoms --relocate=org.osgi:org.osgi.compendium:debian
``

This time, "mh_installpoms" shows said error.

FYI: I was updating "osgi-compendium" to release 6 which renames itself to 
"osgi.cmpn.jar".



signature.asc
Description: OpenPGP digital signature

Bug#885580: debhelper: dh add-ons are order sensitive

[殷啟聰 | Kai-Chung Yan]

I encountered a similar situation, hope this help with the issue.

I was developing a addon called "maven-repo-helper-extras" who depends on 
"maven-repo-helper" [1]. The dh sequences in my addon need to be inserted after 
the sequences introduced by "maven-repo-helper", so I was seeking a way to 
establish addon relationship inside a Perl script. Niels Thykier finally 
pointed me to this solution:

```perl
use Debian::Debhelper::Sequence::maven_repo_helper;

insert_after("mh_install", "mh_shlibdeps");
insert_after("mh_shlibdeps, mh_genlaunchers");
```

Thus I can use "dh $@ --with maven_repo_helper_extras" in "debian/rules" 
without applying "maven-repo-helper" as well. Interestingly, it also works even 
if I apply both addon to dh in no matter what order. Seems "debhelper" already 
handles duplicated sequence insertion pretty well.

[1]: https://tracker.debian.org/pkg/maven-repo-helper



signature.asc
Description: OpenPGP digital signature

Bug#890597: ITP: maven-repo-helper-extras -- Additional plugins complementing maven-repo-helper

[殷啟聰 | Kai-Chung Yan]

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#584882: devscripts: [build-rdeps] should offer a list-only output of packages, too

[殷啟聰 | Kai-Chung Yan]

I believe the "--quiet" option in at least 2.17.12 (currently in Buster) solves 
this issue.



signature.asc
Description: OpenPGP digital signature

Bug#890345: Depending on "default-jre-headless" Should be Sufficient

[殷啟聰 | Kai-Chung Yan]

Package: jflex
Version: 1.6.1-2
Severity: wishlist

"jflex" seems to me a commandline program, thus depending on 
"default-jre-headless" should be sufficient. Right now it depends on 
"default-jre" and "pbuilder" always fetches the whole graphical stack while 
building "libsmali-java".



signature.asc
Description: OpenPGP digital signature

Bug#890222: ITP: jnacl -- Pure Java implementation of the NaCl: Networking and Cryptography library

[殷啟聰 | Kai-Chung Yan]

Perhaps urge him to make a release?



signature.asc
Description: OpenPGP digital signature

Bug#888741: Does Not Honor defaultTasks

[殷啟聰 | Kai-Chung Yan]

Package: gradle-debian-helper
Version: 1.6
Severity: normal

One may specify the default tasks to run in a Gradle script, thus avoid messing 
with the commandline. However gradle-debian-helper makes it impossible to use 
this feature, for it adds a "jar" task if no task is specified.

It could be fixed inside the Gradle plugin since the "defaultTasks" property 
can be configured dynamically.

Bug#879175: androidsdk-tools: Duplicate of android-platform-tools-swt

[殷啟聰 | Kai-Chung Yan]

(I am one maintainer of android-platform-tools-swt)

To be honest, both should be removed since Google has abandoned 
android-platform-tools-swt. That's why it remains unbuildable as of today.



signature.asc
Description: OpenPGP digital signature

Bug#876764: Update to Release 2.0.0 and Point Homepage to GitHub

[殷啟聰 | Kai-Chung Yan]

Package: libscout
Version: 0.0~git20161124~dcd2a9e-1
Severity: minor

Upstream has newer release now and they also moved the code to GitHub [1].

[1]: https://github.com/reddr/LibScout



signature.asc
Description: OpenPGP digital signature