[Dev] orphan-packaging model

Markus Lehtonen markus.lehtonen at linux.intel.com
Fri Sep 5 04:29:44 GMT 2014


Hello,

On 04/09/14 14:08, "Patrick Ohly" <patrick.ohly at intel.com> wrote:
>On Thu, 2014-09-04 at 12:52 +0300, Markus Lehtonen wrote:
>> Hi,
>> 
>> On 04/09/14 12:23, "Patrick Ohly" <patrick.ohly at intel.com> wrote:
>> 
>> >On Thu, 2014-09-04 at 03:12 +0000, Lv, RuiX wrote:
>> >> Hi Patrick,
>> >> 
>> >> The convert action only create the orphan packaging branch which only
>> >>contains packaging info.
>> >> Thus, you need to create the corresponding development branch that
>> >> contains libphonenumber source code with `gbs devel start`.
>> >> 
>> >> Please follow the following procedure, I've verified it on my side.
>> >> 
>> >> 1. Clone the package and switch to it.
>> >> 
>> >> $ git clone tizen: platform/upstream/libphonenumber
>> >> $ cd libphonenumber
>> >> $ git br
>> >> * accepted/tizen_common
>> >> 
>> >> 2. Convert to orphan-packaging model
>> >> 1) Create packaging branch.
>> >> $ gbs devel convert
>> >> $ git br 
>> >>   accepted/tizen_common
>> >> * accepted/tizen_common-orphan
>> >> 2) Create development branch
>> >> $ gbs devel start
>> >> $ git br
>> >>   accepted/tizen_common
>> >>   accepted/tizen_common-orphan
>> >> * development/accepted/tizen_common-orphan/5.3.2
>> >> 
>> >> 3. Do development on development branch and export patches to
>>packaging
>> >>branch.
>> >> # Do local development.
>> >
>> >I did exactly that, and then I got stuck because of one key issue: how
>> >is one supposed to do local development now?
>> >
>> >"gbs build" fails:
>> >
>> >info: generate repositories ...
>> >info: build conf has been downloaded at:
>> >      /work/tizen/tmp/gbs/pohly-gbs/common.conf
>> >info: start building packages from: /tmp/libphonenumber (git)
>> >2014-09-04 06:06 +0000
>> >gbs 0.22.2
>> >error: No source package found at /tmp/libphonenumber
>> >error: <gbs>some packages failed to be built
>> >
>> >Patches are applied, but without "gbs build", one is limited to
>> >compiling on the host system, which is not the same as compiling for
>> >Tizen and not possible for many Tizen specific packages.
>> 
>> GBS build is supposed to work. What do you have in your ~/gbs.conf and
>> what command line are you using to build the package (plain "gbs build"
>> should be enough)?
>
>It's the --include-all which is causing the failure above. With
>--include-all:
>
>$ gbs build --profile common -A i586 --include-all
>info: generate repositories ...
>info: build conf has been downloaded at:
>      /work/tizen/tmp/gbs/pohly-gbs/common.conf
>info: start building packages from: /tmp/libphonenumber (git)
>2014-09-04 10:26 +0000
>gbs 0.22.2
>error: No source package found at /tmp/libphonenumber
>error: <gbs>some packages failed to be built

This bug is tracked here:
https://bugs.tizen.org/jira/browse/DEVT-199

Thanks,
  Markus




More information about the Dev mailing list