canonical-ci-engineering team mailing list archive

[Celso Providelo <celso.providelo@xxxxxxxxxxxxx>]

Andy,

You are right, we can specify "lp:ubuntu/trusty/python-gnupg revno:1234" on
the recipe [1]

By doing that we can eliminate the "branch the package branch" step when we
don't actually need local changes.

This is the case for python-gnupg, I will convert its recipe and drop the
branch as an experiment. Although I foresee problems with the current
versioning schema (since it's already published from our branch, the
versions will conflict), but I will sort it out.


[1] https://help.launchpad.net/Packaging/SourceBuilds/Recipes




On Tue, May 13, 2014 at 1:49 PM, Andy Doan <andy.doan@xxxxxxxxxxxxx> wrote:

> On 05/13/2014 09:55 AM, Celso Providelo wrote:
>
>> For adding python-gnupg, I have branched lp:ubuntu/trusty/python-gnupg
>> [2] and a created a branch recipe [3] for backporting it to precise.
>>
>
> Do we really need our own branch? Can't we just tell the recipe to build
> from a specific revno off the original?
>
>  Other *new* dependencies can follow the same workflow.
>>
>> [1]
>> https://launchpad.net/~canonical-ci-engineering/+archive/mthood-phase-0
>> <https://launchpad.net/%7Ecanonical-ci-engineering/+
>> archive/mthood-phase-0>
>> [2]
>> https://code.launchpad.net/~canonical-ci-engineering/
>> ubuntu-ci-services-itself/python-gnupg
>> <https://code.launchpad.net/%7Ecanonical-ci-engineering/
>> ubuntu-ci-services-itself/python-gnupg>
>> [3]
>> https://code.launchpad.net/~canonical-ci-engineering/+
>> recipe/python-gnupg-phase-0
>> <https://code.launchpad.net/%7Ecanonical-ci-engineering/+
>> recipe/python-gnupg-phase-0>
>>
>
>


-- 
Celso Providelo
celso.providelo@xxxxxxxxxxxxx