[Android-tools-devel] RFS: First Wave of Android Marshmallow SDK Uploading

[殷啟聰]

Hi Hans,

I noticed that you uploaded all these packages into experimental,
which I would not recommend. Since the other upcoming Android packages
need them to build, how can the future Android packages download them
in buildd if they are in experimental?

Apart from this, let's see android-libselinux which I changed the
SONAME back to "libselinux.so.0" in 6.0.0+r26 while in 5.1.1+r8 it is
"libselinux.so.5". If we upload 6.0.0+r26 to unstable one day, we will
need to upload a rebuild to packages that uses android-libselinux.

For the lintian warnings, well actually they are not warnings and may
be false positives. First, I think "dh-exec-subst-unknown-variable" is
actually reminding the maintainer of typos of "DEB_MULTIARCH_HOST" or
something. Because Android SDK Build-tools resides in a directory with
the name being the version string, I want to substitute the install
path automatically using dh-exec. Besides, in the detect_arch.mk it
exports the variable CPU which enables us to install AndroidConfig.h
into corresponding location. As I am installing AndroidConfig.h into
/usr/include/{DEB_MULTIARCH_HOST}, we don't need to detect the
architecture before including it.

Second, maybe Lintian does not recognize the fields for Build-Profiles
so it gave "unknown-field-in-control". "built-for-profiles" field is
generated if the package is specified any build-profiles during the
build, which is "stage1" for this package. After we upload
android-platform-system-core and android-platform-frameworks-base we
will upload a full version of android-platform-build again, which
won't have this unrecognized field. I think we should file a wishlist
bug to Lintian for this field?

Cheers,
Kai-Chung Yan

2016-01-15 4:47 GMT+08:00 Hans-Christoph Steiner <hans at at.or.at>:
>
>> * android-platform-external-libunwind_6.0.0+r26-2
>> * android-platform-external-libselinux_6.0.0+r26-2
>> * android-platform-frameworks-native_1:6.0.0+r26-1
>
> I uploaded these.
>
>
>> * android-platform-build_1:6.0.0+r26-1~stage1
>
> This one has some lintian warnings that might be important:
>
>
> I: android-platform-build source: dh-exec-subst-unknown-variable
> debian/android-platform-build-headers.install CPU
> I: android-platform-build source: dh-exec-subst-unknown-variable
> debian/zipalign.install BUILD_TOOLS_VERSION
> I: android-platform-build source: dh-exec-subst-unknown-variable
> debian/zipalign.links BUILD_TOOLS_VERSION
> N:
> N:    The package uses a variable in one of its debhelper config files, but
> N:    the variable is not one known to dpkg-architecture.
> N:
> N:    It is recommended to use a known subset of variables. If the package
> N:    needs more than that, and makes sure the variable is exported through
> N:    the build one way or the other, then this tag can be safely ignored or
> N:    overridden.
> N:
> N:    Severity: minor, Certainty: wild-guess
> N:
> N:    Check: debhelper, Type: source
> N:
> I: android-platform-build-headers: unknown-field-in-control
> built-for-profiles
> N:
> N:    See the Policy Manual for a list of the possible fields in a binary
> N:    package control file.
> N:
> N:    In udeb packages the fields pre-depends, conflicts, essential and
> N:    suggests are disallowed, but they can contain the new fields
> N:    subarchitecture and installer-menu-item.
> N:
> N:    Refer to Debian Policy Manual section 5.3 (Binary package control
> files
> N:    -- DEBIAN/control) for details.
> N:
> N:    Severity: minor, Certainty: possible
> N:
> N:    Check: fields, Type: binary, udeb, source
>
>
> .hc
>
>
> 殷啟聰:
>> Hi all,
>>
>> I have prepared the first wave of Android Marshmallow SDK package
>> uploading. These packages include:
>>
>> * android-platform-build_1:6.0.0+r26-1~stage1
>> * android-platform-frameworks-native_1:6.0.0+r26-1
>> * android-platform-external-libunwind_6.0.0+r26-2
>> * android-platform-external-libselinux_6.0.0+r26-2
>>
>> All of them can be cloned via our Alioth Git server
>> <https://anonscm.debian.org/cgit/android-tools>.
>>
>> These packages are independent from each other so they can be reviewed
>> and uploaded simultaneously. Note that android-platform-build is being
>> uploaded a stage1 version. After this upload we will be ready to
>> upload the next wave of packages.
>>
>> Sorry to keep everybody waiting for so long, we can't achieve the goal
>> without the help of the maintainers of f2fs-tools and zopfli. Thank
>> you so much!
>>
>> Cheers,
>> Kai-Chung Yan
>>
>
> _______________________________________________
> Android-tools-devel mailing list
> Android-tools-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/android-tools-devel



-- 
/*
* 殷啟聰 | Kai-Chung Yan
* 一生只向真理與妻子低頭
* Full-time student of National Taichung University of Education
* LinkedIn: <https://linkedin.com/in/seamlik>
* Blog: <seamlik.logdown.com>
*/