[Android-tools-devel] updating packages to 6.0.1_r43 (or any update of upstream sources)

Wed Jul 20 06:42:20 UTC 2016

On Wed, Jul 20, 2016 at 2:25 AM, Hans-Christoph Steiner <hans at at.or.at> wrote:
>
> Scripting or otherwise automating the update process would be very good
> to do.  Ideally, it would be trivial to include an r* version update so
> that we can closely track upstream's security releases without much work.
I'll get started on that then.
>
> The big question is how best to do that.  The upload order thing is a
> real bummer because of the circular dependencies.  We should revisit the
> upload order and see whether its still so complicated.  And if so,
> perhaps we need to change the structure of the packaging to simplify
> uploading updates.
I'll see if I can think of anything about it.
I think this could be better discussed in a meeting, Kai-Chung
probably has more to say given he did a lot of work on this before.
>
> In the short term, we should choose the most recent version that we
> think we can get fully uploaded by the end of GSoC and go with that
> version.  If that's 7.0.0, that would be great to have.
It can't be 7.0.0, as source code isn't available yet, and probably
won't be before the end of GSoC. We already have 6.0.1 available, in
the form of source code and also multiple Debian packages built from
that, so I would say getting that ready would be doable.
7.0.0 could be a nice after GSoC / after 6.0.1 / after Google releases
source code goal.
>
> .hc
>
> Chirayu Desai:
>> One more thing which I forgot to add above, is that we can have two scripts.
>>
>> 1. Update all repos to latest android release. The monthly security
>> releases would be good for this.
>> 2. Build all the repos in order (stage1 first, some repos before
>> others, etc) - i.e. what is listed on the wiki.
>>
>> On Tue, Jul 19, 2016 at 4:12 PM, Chirayu Desai <chirayudesai1 at gmail.com> wrote:
>>> I was thinking of scripting the updates.
>>> We have so many versions only because they have multiple tags for each
>>> release (different devices), and they're doing monthly security
>>> releases. While most of that would not affect the code we build, some
>>> of it would, so it would be better to get those in.
>>>
>>> Since we don't modify upstream much at all, the patches aren't too big
>>> - it won't be hard to script the updates, and/or deal with any minor
>>> conflicts.
>>> I had that on my mind before I left for DebConf, and even had this
>>> saved as a draft, but I hadn't got around to doing this yet as right
>>> now I'm working on the google-android-*-installer packages.
>>>
>>> On Tue, Jul 19, 2016 at 3:33 PM, 殷啟聰 <seamlikok at gmail.com> wrote:
>>>> Hi Hans,
>>>>
>>>> Google keeps releasing new revision frequently, now they have
>>>> 6.0.1_r55. I think we can focus on 7.0.0_r1 on the next update.
>>>> Importing a new revision for all packages requires lots of work but
>>>> sometimes gains little, as most of the packages evolved in version
>>>> strings but not in codes.
>>>>
>>>> Cheers,
>>>> Kai-Chung Yan
>>>>
>>>> 2016-06-16 22:04 GMT+08:00 Hans-Christoph Steiner <hans at at.or.at>:
>>>>>
>>>>> Hey all,
>>>>>
>>>>> I see that the first 6.0.1_r43 update has gone into unstable with
>>>>> android-platform-frameworks-base.  Its great to see progress on that.
>>>>> There is one key detail to that process that we have to follow: the
>>>>> order of uploading the updates.
>>>>>
>>>>> It is important that all updates are built only against upstream
>>>>> versions that are an exact match. All of the Bulid-Depends of
>>>>> android-platform-frameworks-base 6.0.1_r43 should also be from
>>>>> 6.0.1_r43.  This is important to prevent obscure bugs causing by
>>>>> building against older libraries.  Google handles this by checking out
>>>>> and building the whole SDK at once.
>>>>>
>>>>> More on this topic here, including the order used for 6.0.1_r16 here:
>>>>> https://wiki.debian.org/AndroidTools#Updating_the_source_packages
>>>>>
>>>>> .hc
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>>> * 一生只向真理與妻子低頭
>>>> * Undergraduate student in National Taichung University of Education
>>>> * LinkedIn: <https://linkedin.com/in/seamlik>
>>>> * Blog: <http://seamlik.logdown.com>
>>>> */
>>>>
>>>> _______________________________________________
>>>> 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
>>>
>>>
>>> On Tue, Jul 19, 2016 at 3:33 PM, 殷啟聰 <seamlikok at gmail.com> wrote:
>>>> Hi Hans,
>>>>
>>>> Google keeps releasing new revision frequently, now they have
>>>> 6.0.1_r55. I think we can focus on 7.0.0_r1 on the next update.
>>>> Importing a new revision for all packages requires lots of work but
>>>> sometimes gains little, as most of the packages evolved in version
>>>> strings but not in codes.
>>>>
>>>> Cheers,
>>>> Kai-Chung Yan
>>>>
>>>> 2016-06-16 22:04 GMT+08:00 Hans-Christoph Steiner <hans at at.or.at>:
>>>>>
>>>>> Hey all,
>>>>>
>>>>> I see that the first 6.0.1_r43 update has gone into unstable with
>>>>> android-platform-frameworks-base.  Its great to see progress on that.
>>>>> There is one key detail to that process that we have to follow: the
>>>>> order of uploading the updates.
>>>>>
>>>>> It is important that all updates are built only against upstream
>>>>> versions that are an exact match. All of the Bulid-Depends of
>>>>> android-platform-frameworks-base 6.0.1_r43 should also be from
>>>>> 6.0.1_r43.  This is important to prevent obscure bugs causing by
>>>>> building against older libraries.  Google handles this by checking out
>>>>> and building the whole SDK at once.
>>>>>
>>>>> More on this topic here, including the order used for 6.0.1_r16 here:
>>>>> https://wiki.debian.org/AndroidTools#Updating_the_source_packages
>>>>>
>>>>> .hc
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>>> * 一生只向真理與妻子低頭
>>>> * Undergraduate student in National Taichung University of Education
>>>> * LinkedIn: <https://linkedin.com/in/seamlik>
>>>> * Blog: <http://seamlik.logdown.com>
>>>> */
>>>>
>>>> _______________________________________________
>>>> 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
>>
>> _______________________________________________
>> 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
>>
>
> _______________________________________________
> 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