[Android-tools-devel] autopkgtest ppc64el is blocking the last migration to testing
Hans-Christoph Steiner
hans at at.or.at
Mon Jan 18 10:55:19 GMT 2021
Roger Shimizu:
> Dear Hans,
>
> On Thu, Jan 14, 2021 at 7:17 PM Hans-Christoph Steiner <hans at at.or.at> wrote:
>>
>>
>> If anyone wants to ensure the ported packages make it into bullseye, the
>> autopkgtest failures on ppc64el need to be fixed (probably affects other arches):
>>
>> https://qa.debian.org/excuses.php?package=android-platform-frameworks-base
>> https://qa.debian.org/excuses.php?package=android-platform-art
>>
>> My fix would be this:
>> Architecture: amd64 i386 armhf arm64
>
> for android-platform-art, I checked the autopkgtest result:
> - https://ci.debian.net/data/autopkgtest/testing/ppc64el/a/android-platform-art/9680334/log.gz
>
> so it fails when trying to install dexdump and dexlist, which do not
> exist on ppc64el.
> So the fix should limit autopkgtest in specific ARCHs:
>
> --- a/debian/tests/control
> +++ b/debian/tests/control
> @@ -4,3 +4,4 @@ Depends: dmtracedump
> # <!stage1>
> Tests: dexdump-dexlist
> Depends: dexdump, dexlist
> +Architecture: amd64 i386 armhf arm64
>
> For android-platform-frameworks-base, I haven't checked the details yet.
> But guessing it should be similar.
Right now, updating these packages is death by 1000 papercuts on top of
rewriting upstream's build system each release. This is the kind of additional
papercut that the Android Tools Team needs to avoid. We cannot afford more to
add any more complexity. Porting fixes need to maintain or reduce complexity.
With that specific bug, Jochen and I worked through it with the britney
maintainers in #debian-devel, which took 1-2 hours, and resulted in two
exceptions being given to us and this bug report:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980087
.hc
More information about the Android-tools-devel
mailing list