[Dev] orphan-packaging model

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


Hi,

Below, comments to some points/questions that I somehow missed yesterday...

On 04/09/14 12:23, "Patrick Ohly" <patrick.ohly at intel.com> wrote:

[...snip...]

>> $ gbs devel export
>> $ git br
>>   accepted/tizen_common
>> * accepted/tizen_common-orphan
>>   development/accepted/tizen_common-orphan/5.3.2
>> 
>> 4. Commit patches and perform building.
>> $ git add * 
>> $ git commit -s 
>> $ gbs build -A i586
>
>Did this work for you? It fails here:
>
>$ schroot -c trusty-amd64 -- 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 06:33 +0000
>gbs 0.22.2
>info: prepare sources...
>info: start export source from: /tmp/libphonenumber ...
>info: Creating (native) source archive libphonenumber-5.3.2.tgz from
>'2206e257dd44f1e1d4640bb906ed98bbe2f69ef3'
>info: package files have been exported to:
>     `
>...
>[    2s] -----------------------------------------------------------------
>[    2s] ----- building libphonenumber.spec (user abuild)
>[    2s] -----------------------------------------------------------------
>[    2s] -----------------------------------------------------------------
>[    2s] + exec rpmbuild --define '_srcdefattr (-,root,root)'
>--nosignature --target=i686-tizen-linux --define '_build_create_debug 1'
>-ba /home/abuild/rpmbuild/SOURCES/libphonenumber.spec
>[    2s] Building target platforms: i686-tizen-linux
>[    2s] Building for target i686-tizen-linux
>[    2s] Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.PpF7ss
>...
>[    2s] + echo 'Patch #0
>(0001-fix-compiler-warnings-about-signed-unsigned-int-cons.patch):'
>[    2s] Patch #0 
>(0001-fix-compiler-warnings-about-signed-unsigned-int-cons.patch):
>[    2s] + /bin/cat
>/home/abuild/rpmbuild/SOURCES/0001-fix-compiler-warnings-about-signed-unsi
>gned-int-cons.patch
>[    2s] + /bin/patch -p1 --fuzz=2
>[    2s] can't find file to patch at input line 13
>[    2s] Perhaps you used the wrong -p or --strip option?
>[    2s] The text leading up to this was:
>[    2s] --------------------------
>[    2s] |From: Patrick Ohly <patrick.ohly at intel.com>
>[    2s] |Date: Tue, 9 Jul 2013 15:26:54 +0200
>[    2s] |Subject: fix compiler warnings about signed/unsigned int
>constants
>[    2s] |
>[    2s] |---
>[    2s] | 
>cpp/test/phonenumbers/geocoding/phonenumber_offline_geocoder_test.cc | 4
>++--
>...
>
>The problem is that the generated libphonenumber-5.3.2.tgz only has the
>packaging meta data, but not the source.
>
>In a private reply Markus mentioned that it also failed for him and gave
>an explanation (something about gbs treating the package as
>"native" and how the branches are set up), but that went a bit over my
>head, so I am not sure how to fix it.

Oh, I had accidentally pressed reply. This page tries to explain the
difference between native and non-native packages:
https://source.tizen.org/documentation/reference/git-build-system/maintenan
ce-models-supported-gbs

The basic difference is that in non-native packages we have a upstream
source tarball and tizen-specific source code changes as patches on top of
that. In native packages we don't have patches - just create a tarball
from the tip of the git branch.



>So suppose you are still reading this ;-) and then new -orphan branch
>works. How do I push that back into the tizen repo? The -orphan branch
>needs to replace the "tizen" branch, right?

Basically yes. The tizen branch would to be replaced with the new "orphan"
branch.


Thanks,
  Markus




More information about the Dev mailing list