Bug#869169: RFP: minisign -- A dead simple tool to sign files and verify signatures

Hi, Are there any updates on this? @fancycade do you have the package available somewhere by any chance? -- Regards, Chirayu Desai

Bug#869087: (no subject)

Hello, This bug looks to be the same as #944118 I opened a MR with the upstream fix mentioned in #33 https://salsa.debian.org/debian/tar/-/merge_requests/2 -- Regards, Chirayu Desai

Bug#944118: (no subject)

Hello, I opened a MR with the patch linked in #93 https://salsa.debian.org/debian/tar/-/merge_requests/2 -- Regards, Chirayu Desai

Bug#963058: upstream only supports x86

On Thu, 31 Dec 2020 09:36:47 +0100 Hans-Christoph Steiner wrote: > For the record, the particular bits of asm that I'm taking about are in > a different source package, but these packages are all interwoven and > should really be a single source package. These are the files in question: > >

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

Yeah, you can see them working on darwin arm64 at https://android-review.googlesource.com/q/darwin for example. There are preview builds available for the emulator for darwin arm64, but I haven't seen arm64 platform-tools yet. On Thu, Dec 31, 2020 at 2:21 PM Hans-Christoph Steiner wrote: >

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

That might just be for the emulator images though. I grabbed 'adb' from the build output, that's still x86-64 AOSP does not have host prebuilts for arm64 yet - see https://android.googlesource.com/platform/prebuilts/clang/host On Thu, Dec 31, 2020 at 2:15 PM 殷啟聰 | Kai-Chung Yan wrote: > > It

Bug#976891: [Android-tools-devel] Bug#976891: fastboot exits with "fake placeholder until fastboot builds" message

>From a quick check it looks the asm for ARM is present, it's just put directly in the header x86/mips (and their 64-bit variants) have AsmGetRegs*.S arm and aarch64 has it in the header file, see:

Bug#976891: [Android-tools-devel] Bug#976891: fastboot exits with "fake placeholder until fastboot builds" message

Hello, On Wed, Dec 23, 2020 at 10:12 PM Roger Shimizu wrote: > On Wed, Dec 23, 2020 at 5:38 AM Hans-Christoph Steiner > wrote: > > > > Thanks for jumping in Roger! I reviewed it with cdesai, and we thought > > those libraries were not used on the "host" version, only when built as > > part of

Bug#955695: This has been fixed upstream

: v1.5.3, v1.5.5, etc. Regards, Chirayu Desai

Bug#827214:

fixed android-framework-23/6.0.1+r72-1

Bug#835695: [Android-tools-devel] Bug#835695: android-platform-development: FTBFS: ld: cannot find -lETC1

Hi, I must apologize here, I mixed with src:android-platform-development with src:android-platform-dalvik. Either way, the issue was still multilib, and Kai-Chung Yan has fixed that and filed a RFS for this package. Version r55 should fix it once that is uploaded. Regards, Chirayu Desai On 08

Bug#835695: [Android-tools-devel] Bug#835695: android-platform-development: FTBFS: ld: cannot find -lETC1

Hi, This should be fixed in newer versions, we did a multilib move around 6.0.1+r16-1 which had broke some packages. A newer version, 6.0.1+r55 has been uploaded, is available in testing as of today. See https://tracker.debian.org/news/793698 On 08/28/2016 02:40 PM, Lucas Nussbaum wrote: >

Bug#831870: /usr/bin/mk-origtargz: Re: devscripts: [mk-origtargz] Fails to create tar with Files-Excluded

w3m 0.5.3-29 -- no debconf information >From f48188e767165bb735d9642b30e1fb20794ff06e Mon Sep 17 00:00:00 2001 From: Chirayu Desai <chirayudes...@gmail.com> Date: Thu, 25 Aug 2016 13:38:21 +0530 Subject: [PATCH] mk-origtargz: rm excluded --- scripts/mk-origtarg

Bug#834753: Patch sent upstream

Hi, I have uploaded the patch to upstream's code review system [1] [1]: https://android-review.googlesource.com/260250

Bug#834753: Fix pushed to git

Hi Santiago, Thanks for reporting the bug. I've pushed a fix for it to the master branch, http://deb.li/rKfh RAM was not an issue here. The buildscripts divided the number of available processors by 2, however that obviously wouldn't work for a single processor so I added a check to not do that

Bug#827216: More info.

So this bug was caused by an assert being hit in libutils It was in: #3 0x7790410b in android::VectorImpl::itemLocation (this=0x7fffc990, index=0) at libutils/VectorImpl.cpp:319 (Which is a build from current git, 6.0.1+r55 Android builds have NDEBUG set system wide during the

Bug#827216: Fixed.

http://deb.li/yXp2 fixes this. Can now build apps and use apktool.

Bug#833458: ITP: android-framework-23 -- Provides Android Marshmallow '23' API stubs, needed for building apps.

Source code is available at https://anonscm.debian.org/cgit/android-tools/android-framework-23.git/ On Thu, Aug 4, 2016 at 9:24 PM, Chirayu Desai <chir...@cdesai.in> wrote: > Package: wnpp > Severity: wishlist > Owner: Chirayu Desai <chir...@cdesai.in> > > * Package nam

Bug#833458: ITP: android-framework-23 -- Provides Android Marshmallow '23' API stubs, needed for building apps.

Package: wnpp Severity: wishlist Owner: Chirayu Desai <chir...@cdesai.in> * Package name: android-framework-23 Version : 6.0.1+r55 Upstream Author : The Android Open Source Project <initial-contribut...@android.com> * URL : https://android.googlesource.co

Bug#831870: devscripts: [mk-origtargz] Fails to create tar with Files-Excluded

Hi, On Wed, Jul 20, 2016 at 8:21 PM, Osamu Aoki <osamua...@e01.itscom.net> wrote: > Hi, > > Is this a bug or lack of documentation ... Apologies, I should've included more info. > > On Wed, Jul 20, 2016 at 05:10:01PM +0530, Chirayu Desai wrote: >> Package: de

Bug#831870: devscripts: [mk-origtargz] Fails to create tar with Files-Excluded

in archive tar: : Not found in archive tar: Exiting with failure status due to previous errors mk-origtargz: error: tar --delete tools/preload/sorttable.js gave error exit status 2 The file android-6.0.1_r43.tar.gz can be grabbed from [3]. It is big, 930M. Regards, Chirayu Desai [1]: http

Bug#827646: [Android-tools-devel] Bug#827646: apktool: refer directly to framework-res.apk from android-framework-res

Hi, I have opened a discussion with the maintainer at [1]. Cheers, Chirayu Desai [1]: https://github.com/iBotPeaches/Apktool/issues/1277 On Sun, Jun 19, 2016 at 8:57 AM, Paul Wise <p...@debian.org> wrote: > Package: apktool > Severity: wishlist > Usertags: cruft > > Cu

Bug#827264: aapt package aborts with exit code 134

Here's a log [1] from the android build of aapt / libaapt, very useful for comparison. [1]: http://sprunge.us/CYJL On Tue, 14 Jun 2016 17:32:37 +0530 Chirayu Desai <chir...@cdesai.in> wrote: > Package: aapt > Version: 1:6.0.1+r43-1 > Severity: important > > Dear Mainta

Bug#827216: [Android-tools-devel] Bug#827216: android-sdk: Process 'command 'aapt'' finished with non-zero exit value 134

That doesn't really say much. The "Abort message" is just abort. This happens with apktool as well, and is an aapt issue, so I filed a bug for it. It has more info, see: #827264 On Tue, Jun 14, 2016 at 5:02 PM, 殷啟聰 wrote: > Can you attach the outputs of running `gradle

Bug#827264: aapt package aborts with exit code 134

Package: aapt Version: 1:6.0.1+r43-1 Severity: important Dear Maintainers, I'm trying to use aapt to package an android app, but it fails to do so. I've tried this by running 'gradle build' with a sample app I have at [1], and also with 'apktool' by running 'apktool build' 'gradle build

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

Package: android-sdk Version: 24.3.3+2 Severity: important Dear Maintainers, I'm trying to build a sample app with the SDK by running 'gradle build'. App is available at [1]. After putting in the files mentioned in Bug #827214 and Bug #827215, the next failure is: Execution failed for task

Bug#827215: android-sdk: llvm-rs-cc is missing

Package: android-sdk Version: 24.3.3+2 Severity: grave Justification: renders package unusable Dear Maintainers, I'm trying to build a sample app with the SDK by running 'gradle build'. App is available at [1]. After putting in the files mentioned in Bug #827214, the next failure is: Execution

Bug#827214: android-sdk: failed to find target with hash string 'android-23' in: /usr/lib/android-sdk

Package: android-sdk Version: 24.3.3+2 Severity: grave Justification: renders package unusable Dear Maintainers, I'm trying to build a sample app with the SDK by running 'gradle build'. App is available at [1]. This is due to the files 'source.properties' and 'build.prop' missing from

Bug#826991: [Android-tools-devel] Bug#826991: fastboot missing libziparchive.so.0

Hi, This problem seems to have been fixed already in the source code. The issue here is that fastboot doesn't search in the multi-arch path (/usr/lib/x86_64-linux-gnu/android/) - you can verify that by installing the 'patchelf' package, and then running 'patchelf --print-rpath `which fastboot`',

Bug#827056: [Android-tools-devel] Bug#827056: aapt error: No such file or directory

On Sat, Jun 11, 2016 at 11:40 PM, Mouaad Aallam wrote: > Package: aapt > Version: 1:6.0.1+r16-1+b1 > Severity: important > > Hello, > > While testing building an app using android-sdk, aapt throwed the error[1]: > > java.io.IOException: Cannot run program >

Bug#824933: [Android-tools-devel] Bug#824933: Bug#824933: Bug#824933: Bug#824933: Bug#824933: Bug#824933: apktool: crashes with every APK

changes I want to make on top of this (shlib rpath usage), and I guess we could also merge upstream (r43 is currently present in the debian repos, r46 is the latest AOSP upstream) On Fri, Jun 10, 2016 at 10:12 PM, Markus Koschany <a...@debian.org> wrote: > On 10.06.2016 16:55, Chirayu De

Bug#824933: [Android-tools-devel] Bug#824933: Bug#824933: Bug#824933: Bug#824933: Bug#824933: apktool: crashes with every APK

On Fri, Jun 10, 2016 at 7:26 PM, Markus Koschany <a...@debian.org> wrote: > On 10.06.2016 14:15, Chirayu Desai wrote: > [...] >> Hi, >> I have just pushed my changes to apktool and frameworks/base. >> frameworks/base has some other changes from seamlik (android.ja

Bug#826761: [Android-tools-devel] Bug#826761: Bug#826761: Fix for the bug

; other. Of course this only applies to team maintained packages. [1] Ok, I will avoid CCing everybody for now for the team maintained packages. > > On 10.06.2016 15:25, Chirayu Desai wrote: >> Hi, >> >> I have pushed a fix for this at [1]. >> Before pushing that to

Bug#826761: Fix for the bug

Hi, I have pushed a fix for this at [1]. Before pushing that to Debian, there's a question I wanted to ask. I generated the changelog entry with 'dch', which put the nmu version / Non-maintainer upload entry in the changelog by itself. Makes sense, since I'm not a maintainer yet, my question here

Bug#824933: [Android-tools-devel] Bug#824933: Bug#824933: Bug#824933: apktool: crashes with every APK

On Fri, Jun 10, 2016 at 4:08 PM, Markus Koschany wrote: > On Wed, 8 Jun 2016 14:12:33 +0200 Hans-Christoph Steiner > wrote: >> >> framework-res.apk is not included in the SDK, only the OS. Packaging >> parts of the OS means we are making packages that upstream is

Bug#824930: [Android-tools-devel] Bug#824930: Bug#824930: apktool: creates directories and an empty 1.apk file in $HOME contain

Updated patch available at the same URL. On Thu, Jun 9, 2016 at 9:31 PM, Paul Wise <p...@debian.org> wrote: > On Thu, 2016-06-09 at 19:31 +0530, Chirayu Desai wrote: > >> Currently both android.jar and framework-res.apk are built from >> android-platform-frameworks-base,

Bug#824930: [Android-tools-devel] Bug#824930: Bug#824930: Bug#824930: Bug#824930: Bug#824930: apktool: creates directories and an empty 1.apk file in $HOME contain

I have it ready at [1] & [2] On Thu, Jun 9, 2016 at 9:11 AM, Paul Wise <p...@debian.org> wrote: > On Thu, 2016-06-09 at 00:32 +0530, Chirayu Desai wrote: > >> This was discussed on IRC, and since we already need to build >> framework-res.apk for android.jar (it i

Bug#824930: [Android-tools-devel] Bug#824930: Bug#824930: Bug#824930: Bug#824930: apktool: creates directories and an empty 1.apk file in $HOME

This was discussed on IRC, and since we already need to build framework-res.apk for android.jar (it is extracted and the contents are included as-is in the jar), we can also have a separate package for it, which I have ready at:

Bug#824930: [Android-tools-devel] Bug#824930: Bug#824930: apktool: creates directories and an empty 1.apk file in $HOME

On Sat, May 21, 2016 at 8:45 PM, Markus Koschany wrote: > Am 21.05.2016 um 14:38 schrieb Paul Wise: >> Package: apktool >> Version: 2.1.1+dfsg-1 >> Severity: normal >> Usertags: cruft >> >> For some reason apktool seems to think it is appropriate to create >> files in my home