Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#64102 - [android-tools] 29.0.4-1 breaks #63370 again

Attached to Project: Community Packages
Opened by Adam Fontenot (amfontenot) - Saturday, 12 October 2019, 03:52 GMT
Last edited by Chih-Hsuan Yen (yan12125) - Sunday, 13 October 2019, 13:48 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

I know someone else noticed this, because they requested reopening #63370, but there hasn't been any movement on that in 11 days, so I wanted to bring this directly to the maintainers' attention. Basically, 29.0.3-2 works just fine. After I updated to 29.0.4-1, the bug started occurring again.

Example:

fastboot: core/libsparse/sparse.cpp:131: int write_all_blocks(struct sparse_file *, struct output_file *): Assertion `pad >= 0' failed.
./flash-all.sh: line 21: 210320 Aborted (core dumped) fastboot flash bootloader bootloader-bullhead-bhz32c.img

This happens when attempting to flash an "official" image from Google, so it's not a problem with the image.

Maybe Google reverted the patch for this release? I don't have time to check.

Related bug: https://bugs.archlinux.org/task/63370
This task depends upon

Closed by  Chih-Hsuan Yen (yan12125)
Sunday, 13 October 2019, 13:48 GMT
Reason for closing:  Duplicate
Additional comments about closing:  Thanks for the report. I re-opened https://bugs.archlinux.org/task/63370.
Comment by Luca Weiss (z3ntu) - Saturday, 12 October 2019, 10:52 GMT
It looks like the patch was applied to master but not to the branch where the platform-tools-29.0.4 (or platform-tools-29.0.3) tag is from, so it will have to be applied in the PKGBUILD again.

edit: I've asked at https://issuetracker.google.com/issues/140538105#comment10 when the commit will land in a platform-tools tag but in the meantime the fix definitely has to be applied again.

Loading...