Bug#1011110: unblock: android-platform-tools/29.0.6-14

[Roger Shimizu]

Package: release.debian.org
Severity: normal
User: release.d...@packages.debian.org
Usertags: unblock

Please unblock package android-platform-tools

(Please provide enough (but not too much) information to help
the release team to judge the request efficiently. E.g. by
filling in the sections below.)

[ Reason ]
Previous issue such as #1010231 was already resolved, and now
autopkgtest results are all fine:
- https://qa.debian.org/excuses.php?package=android-platform-tools
- https://qa.debian.org/excuses.php?package=android-platform-art
- https://qa.debian.org/excuses.php?package=android-platform-frameworks-base
Migration period already passed for a few days, but still cannot be
migrated automatically, so I filed this ticket for help.

[ Tests ]
All 3 packages' autopkgtest got passed, and they run well on my
enironment.

[ Risks ]
None so far.
If there's issue, I'll fix it.

[ Checklist ]
[*] all changes are documented in the d/changelog
[*] I reviewed all changes and I approve them
[*] attach debdiff against the package in testing

[ Other info ]
Package android-platform-art and android-platform-frameworks-base should be
migrated at the same time.

unblock android-platform-tools/29.0.6-14
unblock android-platform-art/11.0.0+r48-3
unblock android-platform-frameworks-base/1:10.0.0+r36-5

Cheers,
Roger

[Roger Shimizu]

Dear Paul,

Thanks for your kind help and check!

I created a new ticket to remove android-platform-system-core from
testing as you suggested.
- https://bugs.debian.org/1011210

And there're a few comments below if you're interested ...

On Wed, May 18, 2022 at 2:32 AM Paul Gevers <elb...@debian.org> wrote:
>
> Hi,

>
> On 17-05-2022 06:11, Roger Shimizu wrote:
> > [ Other info ]
> > Package android-platform-art and android-platform-frameworks-base should be
> > migrated at the same time.
> >
> > unblock android-platform-tools/29.0.6-14
> > unblock android-platform-art/11.0.0+r48-3
> > unblock android-platform-frameworks-base/1:10.0.0+r36-5
>

> Our migration software already figured that out [1]:
>
> Trying easy from autohinter: android-platform-art/11.0.0+r48-3
> android-platform-frameworks-base/1:10.0.0+r36-5
> android-platform-tools/29.0.6-14
> start: 24+0: a-1:a-22:a-0:a-0:i-0:m-0:m-0:p-0:s-1
> orig: 24+0: a-1:a-22:a-0:a-0:i-0:m-0:m-0:p-0:s-1
> Checking if changes enables cruft removal
> recur: []
> android-platform-art,android-platform-frameworks-base,android-platform-tools
> 41/0
>
> [...]
>
> finish:
> [android-platform-art,android-platform-frameworks-base,android-platform-tools]
> endloop: 24+0: a-1:a-22:a-0:a-0:i-0:m-0:m-0:p-0:s-1
> now: 37+0: a-6:a-27:a-1:a-1:i-1:m-0:m-0:p-0:s-1

Yes, I also saw this log before, but I cannot understand the meaning.
It's with too many abbv. words and expressions.
It's better if there's a doc to explain these all.

> * amd64: android-libadb, android-libadb-dev,
> android-libnativebridge-dev, android-libnativeloader-dev,
> android-tools-mkbootimg
> * arm64: android-libadb, android-libadb-dev,
> android-libnativebridge-dev, android-libnativeloader-dev,
> android-tools-mkbootimg
> * armel: android-libadb
> * armhf: android-libadb
> * i386: android-libadb
>
> So, upgrading those three source packages would make several packages
> uninstallable.
>
> Here you can see an example of why:
> https://qa.debian.org/dose/debcheck/unstable_main/1652763601/packages/android-libadb.html#720d4c2b1a6529f2af595048faf0e919

I think those uninstallable packages are simply obsoleted, since no
other package depends on them.
That's why I removed those packages from new d/control file of
android-platform-tools (the new source package).

> It took me a while, but the issue is that android-libbase is build by
> two source packages:
> android-platform-system-core/1:10.0.0+r36-10
> and
> android-platform-tools/29.0.6-14
>
> The rules file of android-platform-tools adds an extra epoch, so it wins
> and the version of android-libbase comes from android-platform-tools at
> version 1:29.0.6-14 as rmadison tells me.
>
> Which means that those packages in the update_output.txt can't be
> installed (in unstable) because they have a strict versioned relation
> that can't be fulfilled in unstable. Our migration software detects the
> problem and prevents it from migrating to testing.

I guess these issues should be resolved after bug#1011210
- https://bugs.debian.org/1011210

If not, just let me know, and I'll fix it.
Thanks again!

Cheers,
--
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1