[Dev] orphan-packaging model

Patrick Ohly patrick.ohly at intel.com
Thu Sep 4 13:20:02 GMT 2014


On Thu, 2014-09-04 at 14:53 +0300, Markus Lehtonen wrote:
> Hi,
> 
> On Thu, 2014-09-04 at 13:08 +0200, Patrick Ohly wrote:
> > On Thu, 2014-09-04 at 12:52 +0300, Markus Lehtonen wrote:
> > > 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:
> 
> [...snip...] 

> > $ 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
>
> > Without --include-all I get the same failure as on the packaging branch:
> > 
> > $ schroot -c trusty-amd64 -- gbs build --profile common -A i586
> > 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
> > info: prepare sources...
> > info: start export source from: /tmp/libphonenumber ...
> > info: It seems you're building a development/patch-queue branch. Export
> > target changed to 'accepted/tizen_common-orphan' and patch-export
> > enabled!
> > info: Creating (native) source archive libphonenumber-5.3.2.tgz from
> > 'accepted/tizen_common-orphan'
> > info: package files have been exported to:
> >      /work/tizen/GBS-ROOT-profile.common/local/sources/common/libphonenumber-5.3.2-1
> > ...
> > [    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-unsigned-int-cons.patch
> > [    2s] + /bin/patch -p1 --fuzz=2
> > [    2s] can't find file to patch at input line 13
> 
> which is caused by the missing upstream branch...
> 
> 
> > --with-all needs to work, because otherwise the development cycle gets
> > even longer: commit, compile, edit, commit amend, etc.
> 
> Yes, it needs to work. Strange that gbs export with --include-all seems
> to work fine but build fails.

According to the output above, --include-all already causes the "gbs
export" to fail or get skipped (my interpretation of "No source package
found at /tmp/libphonenumber").

> Looking at the .gbs.conf in libphonenumber:
> upstream_branch = origin
> 
> So gbs looks for branch "origin" instead of "upstream"

Tracy added that. I'm not sure why she picked "origin". Anyway, now I
know what to look out for should I attempt to use the orphan-packaging
model again. For now I am going to stick to the traditional model.

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.





More information about the Dev mailing list