Package Details: android-sdk-platform-tools r24-1

Git Clone URL: https://aur.archlinux.org/android-sdk-platform-tools.git (read-only)
Package Base: android-sdk-platform-tools
Description: Platform-Tools for Google Android SDK (adb and fastboot)
Upstream URL: http://developer.android.com/sdk/index.html
Keywords: android development
Licenses: custom
Conflicts: adb
Provides: adb, android-tools
Submitter: Gordin
Maintainer: chrbayer
Last Packager: chrbayer
Votes: 1089
Popularity: 10.791385
First Submitted: 2011-01-29 23:08
Last Updated: 2016-06-20 07:38

Dependencies (2)

Required by (34)

Sources (3)

Latest Comments

Fandekasp commented on 2016-07-20 09:54

Fixed by replacing the first sha256sum with ef1672ecc3430bb11511fce57370f28b0db47d37df7f1b3298970880b2e221de

Fandekasp commented on 2016-07-20 09:46

Same here

==> Validating source files with sha256sums...
platform-tools_r24-linux.zip ... FAILED
adb.service ... Passed
license.html ... Passed
==> ERROR: One or more files did not pass the validity check!

SuperIce97 commented on 2016-07-19 01:49

I'm having a sha256sum check failure. Was the download recently updated?

chrbayer commented on 2016-05-21 17:00

Thank you very much for pointing this out, I changed the post_install to simple inform the user to source /etc/profile on its own.

grawity commented on 2016-05-21 16:06

That install scripts run as root isn't the problem – the problem is that environment doesn't magically propagate 'upwards'. You have something like this:

bash (user)
└─makepkg -i
··└─sudo pacman…
····└─pacman -U android-etc.pkg.tar.xz
······└─sh -c ". /tmp/pacman/android-etc.install && post_install"

Changing PATH from post_install only affects that last 'sh' process, not any 'above' processes.

yan12125 commented on 2016-05-21 13:35

Don't add `source` commands to install scripts. Install scripts are run as root and a `source` command in these scripts does not make sense. And I don't think PKGBUILD can change users' environment. What *.install should do is just asking users to relogin or reopen the terminal, just like what android-sdk does. [1]

[1] https://aur.archlinux.org/cgit/aur.git/tree/android-sdk.install?h=android-sdk

duttondj commented on 2016-03-17 15:22

The PKGBUILD should run:

source /etc/profile.d/android-sdk-platform-tools.sh
source /etc/profile.d/android-sdk-platform-tools.csh

That should allow you to run adb immediately after install. Otherwise, you would just have to open a new terminal.

chrbayer commented on 2016-03-13 11:45

what do you mean with not able to run adb?
Can you provide some logging data?

physicalit commented on 2016-03-13 11:21

not being able to run "adb" after install should be considered a real bug for this package.

isfeldt34 commented on 2016-03-12 12:28

works just fine changing the line arch=x86_64 to arch=i686. since this is a 32Bit machine, other than that, all is well! and adb works as well here.

All comments