Bug#924591: fastboot format:ext4 misses /usr/lib/android-sdk/platform-tools/mke2fs

[Jonas Meurer]

Control: reopen -1

Hello,

Hans-Christoph Steiner:
> circular Depends:/Recommends: are easy, circular Build-Depends: are
> what's hard.  Plus using the /usr/bin/ method, that will make fastboot
> require e2fsprogs and other packages, rather than just recommend.


Unfortunately, the bug is not really fixed. The symlinks exist now, but
apparently /usr/bin/mke2fs doesn't work for fastboot format:

$ fastboot format:ext4:0xcd3771e00 userdata
Warning: userdata size is0xcd3779e00, but 0xcd3771e00 was requested
for formatting.
Invalid erase-block-size 512: must be a power of 2 and at least 4096.
Invalid logical-block-size 512: must be a power of 2 and at least 4096.
mke2fs 1.44.5 (15-Dec-2018)
/tmp/TemporaryFile-YMROG8: Unimplemented ext2 library function while
setting up superblock
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata

Cheers,
 jonas



signature.asc
Description: OpenPGP digital signature

Bug#924591: fastboot format:ext4 misses /usr/lib/android-sdk/platform-tools/mke2fs

[Hans-Christoph Steiner]

circular Depends:/Recommends: are easy, circular Build-Depends: are
what's hard.  Plus using the /usr/bin/ method, that will make fastboot
require e2fsprogs and other packages, rather than just recommend.

Bug#924591: fastboot format:ext4 misses /usr/lib/android-sdk/platform-tools/mke2fs

[Hans-Christoph Steiner]

why do you think patching would be better?  Seems like it would be more
maintenance work than the symlinks.

Bug#924591: fastboot format:ext4 misses /usr/lib/android-sdk/platform-tools/mke2fs

[seamlik]

I believe we should just patch the code and make it use programs in
`/usr/bin`. And we should do this for all other programs in AOSP. The
symlinks installed in the SDK directory are only intended to make IDEs
or Gradle.

Bug#924591: fastboot format:ext4 misses /usr/lib/android-sdk/platform-tools/mke2fs

[Jonas Meurer]

Package: fastboot
Version: 1:8.1.0+r23-4
Severity: serious

Hello,

after dist-upgrade to Buster, 'fastboot format:ext4' is broken. It tries
to execute '/usr/lib/android-sdk/platform-tools/mke2fs' which doesn't
exist and is not available in the Debian archive:

$ fastboot format:ext4:0xcd3771e00 userdata
Warning: userdata size is0xcd3779e00, but 0xcd3771e00 was requested for 
formatting.
Invalid erase-block-size 512: must be a power of 2 and at least 4096.
Invalid logical-block-size 512: must be a power of 2 and at least 4096.
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata

$ ls /usr/lib/android-sdk/platform-tools/mke2fs
ls: cannot access '/usr/lib/android-sdk/platform-tools/mke2fs': No such file or 
directory


I chose severity serious as this bug is a severe regression that makes
'fastboot format' unusable. Therefore, the bug should be fixed before
the release of Buster.

Cheers
 jonas


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages fastboot depends on:
ii  android-libadb 1:8.1.0+r23-4
ii  android-libbase1:8.1.0+r23-4
ii  android-libcutils  1:8.1.0+r23-4
ii  android-libf2fs-utils  8.1.0+r23-2
ii  android-libsparse  1:8.1.0+r23-4
ii  android-libutils   1:8.1.0+r23-4
ii  android-libziparchive  1:8.1.0+r23-4
ii  libc6  2.28-8
ii  libgcc11:8.3.0-2
ii  libstdc++6 8.3.0-2

fastboot recommends no packages.

fastboot suggests no packages.

-- no debconf information