[Android-tools-devel] google-android-installers:

[Roger Shimizu]

Dear Fab,

Thanks for working on the patches/MR!

I found the autopkgtest (d/tests/control) is disabled for i386, and
when I enable it by applying the patch below, the test fails on i386.
I think the test can help to improve the quality of the package. Can
you kindly help to fix the test for i386?

--- a/debian/scripts/build_tests_control_file.sh
+++ b/debian/scripts/build_tests_control_file.sh
@@ -107,7 +107,7 @@ if [ $TEST_ONLY_GOOGLE_AUTO -ne 1 ]; then

         echo "Test-Command: emulator -help" >> ../tests/control
         echo "Depends: google-android-emulator-installer" >> ../tests/control
-        echo "Architecture: amd64" >> ../tests/control
+        echo "Architecture: amd64 i386" >> ../tests/control
         echo "" >> ../tests/control
     done
 fi
--- a/debian/tests/control
+++ b/debian/tests/control
@@ -1,5 +1,5 @@
 # -- This file was generated automatically by the
debian/scripts/build_tests_control_file.sh script --
 Test-Command: /usr/lib/android-sdk/extras/google/auto/desktop-head-unit
--version
 Depends: google-android-extras-google-auto-installer
-Architecture: amd64
+Architecture: amd64 i386

> It doesn't add any new binary package, so source only upload might be sufficient.

Since this package was moved to non-free.
So buildd will NOT build the package anymore. We have to use binary upload.
And that's why I had to upload i386 separately for the last upload.

Of course we can raise a ticket to ask for ftp-master to enable buildd
for this specific package, but it will take some time ...

Cheers,
Roger

On Fri, Jul 29, 2022 at 3:33 PM <fabstz-it at yahoo.fr> wrote:
>
> Hello Roger,
>
> Thanks for the upload.
>
> I created a new MR that fixes a few things and to fix the blocker for testing migration.
> It doesn't add any new binary package, so source only upload might be sufficient.
>
> Regards
> Fab
>
>
>
> Le 28 juillet 2022 12:34:02 GMT+02:00, Roger Shimizu <rosh at debian.org> a écrit :
>>
>> Dear Fab,
>>
>> Seems autopkgtest no failures anymore:
>> - https://qa.debian.org/excuses.php?package=google-android-installers
>>
>> For i386, I just uploaded as porter.
>> So it didn't include any source changes, nor version bump up.
>>
>> I guess it will be migrated to testing soon.
>>
>> Cheers,
>> Roger
>>
>> On Sun, Jul 24, 2022 at 7:14 PM Fab Stz <fabstz-it at yahoo.fr> wrote:
>>>
>>>
>>>  Hi Roger,
>>>
>>>  Thanks for the update.
>>>
>>>  Le dimanche 24 juillet 2022, 11:51:50 CEST Roger Shimizu a écrit :
>>>>
>>>>  Dear Fab,
>>>>
>>>>  Thanks for your work lately!
>>>>
>>>>  Sorry, I'm in last a few days for Debconf, so don't have much time checking
>>>>  it. (and I probably will be busy for some private stuffs as well after
>>>>  Debconf trip, in August.)
>>>>  But I guess it's because of the reverse dependency of
>>>>  google-android-installers.
>>>
>>>
>>>  I haven't found any reverse dependency or I didn't understand where to look.
>>>  Maybe removal of the now old src:google-android-emulator-installer will fix
>>>  it.
>>>
>>>> You can check the log of autopkgtest, and found the reason of the
>>>> failure, and try to fix it.
>>>> Maybe you need to fix google-android-installers, maybe to fix
>>>> google-android-emulator-installer, or even both.
>>>
>>>
>>>  The autopkgtest failure log doesn't help.
>>>  https://ci.debian.net/data/autopkgtest/testing/amd64/g/google-android-emulator-installer/24000185/log.gz
>>>
>>>  It reports:
>>>
>>>  blame: google-android-emulator-installer
>>>  badpkg: rules extract failed with exit code 1
>>>  autopkgtest [08:13:51]: ERROR: erroneous package: rules extract failed with
>>>  exit code 1
>>>
>>>
>>>  BTW, is it normal the package is not rebuilt on buildd servers?
>>>
>>>  https://buildd.debian.org/status/package.php?p=google-android-installers
>>>
>>>  britney is also complaining that arch:i386 is not built
>>>  and says "missing build on i386"
>>>
>>>  Rgds
>>>  Fab