[Android-tools-devel] Android Tools and GNU/Hurd

[Hans-Christoph Steiner]

Hey Roger,

If you want to understand the complexity that I'm talking about, update the 
package suite to the latest upstream version (e.g. something like 11.0.0+r10). 
This complexity is largely due to upstream's build system requiring lots of 
non-free binaries, aka "prebuilts".  They also make large changes to the build 
system with every major release.

.hc

Hans-Christoph Steiner:
> Hey Roger,
> 
> We need to use experimental in the regular maintenance of the supported archs, 
> so the porting work slows down the regular maintenance.  We already cannot keep 
> up with the regular maintenance, so more porting work in the Android Tools git 
> repos and experimental/sid releases will make than even worse.
> 
> I'm not a porter, so I don't know the limitations of the porterboxes.  Like I've 
> said before, before these packages can be ported here to other arches, there 
> needs to be a lot more contributions to the regular maintenance of the archs 
> that upstream supports (amd64 and aarch64).  Otherwise, we'll end up with these 
> packages being removed from all arches in Debian.  You are free to do whatever 
> you want outside of the team (forks, porterboxes, etc).
> 
> .hc
> 
> Roger Shimizu:
>> Dear Hans,
>>
>> I think there must be something misunderstanding.
>> I just want to port android tools to platforms as many as possible.
>> Uploading to experimental is just to confirm it can build on buildd,
>> and won't cause any regression to other architectures, and it won't
>> affect testing migration on pending.
>> I need to upload, instead of working in private salsa repo, because
>> only uploading to debian can check build on  buildd and auotopkgtest
>> on multiple architectures.
>> Porterbox has many restrictions, such as cannot install local built
>> packages, and can only install from uploaded packages.
>>
>>> https://salsa.debian.org/android-tools-team/admin/-/issues/22
>>
>> Thanks for this info!
>> I'll look at it.
>>
>> BTW. Currently seems testing migration is done, so we can continue the
>> next upload.
>> I'm going to upload android-platform-system-core again, since previous
>> experimental upload confirmed working well [1].
>>
>> [1] 
>> https://buildd.debian.org/status/package.php?p=android-platform-system-core&suite=experimental 
>>
>>
>> Of course, if you still don't agree with above, I will stop the upload.
>> Thanks for your understanding!
>>
>> Cheers,
>> Roger
>>
>> On Mon, Jan 11, 2021 at 6:29 PM Hans-Christoph Steiner
>> <hans at guardianproject.info> wrote:
>>>
>>>
>>> Hey Roger,
>>>
>>> I see you're trying out a GNU/Hurd port.  I think GNU/Hurd is a great
>>> project, so I'm not saying anything about that.  Right now, the Android
>>> Tool packages require tons of work even to support the platforms that
>>> upstream support.  I just did weeks of work on this update.  I won't
>>> have that kind of time going forward.  So we cannot afford to add any
>>> more work to these packages, like trying to support GNU/Hurd, unless
>>> someone commits to providing weeks of dedicated work per year only on
>>> the android-platform-*.
>>>
>>> Additionally, there first would need to be work to reducing the work
>>> required to update these packages.  Chirayu has sketched out a new
>>> approach to the "platform-tools" source package which should reduce the
>>> amount of work required to do an update.  We really need contributions
>>> there:
>>>
>>> https://salsa.debian.org/android-tools-team/admin/-/issues/22
>>>
>>> So I kindly ask you to stop using the Android Tool Team setup to do
>>> further porting work, like uploads to experimental, the main git repos,
>>> etc.  You can do whatever you like in forks.  At risk is the total
>>> collapse and removal of the android-platform-* packages from Debian.
>>>
>>> .hc
>>>
>>> -- 
>>> PGP fingerprint: EE66 20C7 136B 0D2C 456C  0A4D E9E2 8DEA 00AA 5556
>>> https://pgp.mit.edu/pks/lookup?op=vindex&search=0xE9E28DEA00AA5556
>