[Dev] weekeyboard local build error issue

Adam Malinowski a.malinowsk2 at partner.samsung.com
Fri Feb 7 12:12:53 GMT 2014


Hi,

 

You can get rid of this error by specifying -no-patch-export option  to gbs
build command.

 

Adam

 

From: dev-bounces at lists.tizen.org [mailto:dev-bounces at lists.tizen.org] On
Behalf Of VanCutsem, Geoffroy
Sent: Friday, February 07, 2014 10:52 AM
To: Zhao, Juan J; dev at lists.tizen.org
Subject: Re: [Dev] weekeyboard local build error issue

 

It looks like upstream/0.0.2 is a tag and not a branch.  I suspect this is
what's causing the issue. I guess the proper way of fixing this would be to
have a real branch called 'upstream' with a 0.0.2 tag. Or in the meantime,
you can probably mimick what was done in the sandbox/pcoval/tizen branch and
use a different tag in your local .gbs.conf file.

 

Geoffroy

 

From: dev-bounces at lists.tizen.org [mailto:dev-bounces at lists.tizen.org] On
Behalf Of Zhao, Juan J
Sent: Friday, February 07, 2014 7:16 AM
To: dev at lists.tizen.org
Subject: [Dev] weekeyboard local build error issue

 

Hi there,

              In the latest code for
weekeyboard(platoform/upstream/weekeyboard), there is a
sandbox/pcoval/upstream, it causes weekeyboard not local-buildable with this
error in tizen branch:

              error: Invalid upstream treeish upstream/0.0.2

error: Generating upstream tarball and/or generating patches failed. GBS
tried this as you have upstream branch in you git tree. Fix the problem by
either:

  1. Update your upstream branch and/or fix the spec file. Also, check the
upstream tag format.

  2. Remove or rename the upstream branch (change the package to native)

See
https://source.tizen.org/documentation/reference/git-build-system/upstream-p
ackage for more details.

error: <gbs>Failed to export packaging files from git tree

error: no spec files to build.

              

              Why would this "sandbox/pcoval/upstream" branch influence the
local build for weekeyboard? 

What's the decent fix for this issue? Deleting this sandbox branch may work,
is there any better way to keep the branch and still get things fixed?

 

Best Regards,

Juan

Intel Corporation NV/SA
Kings Square, Veldkant 31
2550 Kontich
RPM (Bruxelles) 0415.497.718. 
Citibank, Brussels, account 570/1031255/09

This e-mail and any attachments may contain confidential material for the
sole use of the intended recipient(s). Any review or distribution by others
is strictly prohibited. If you are not the intended recipient, please
contact the sender and delete all copies.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tizen.org/pipermail/dev/attachments/20140207/b4e92d3a/attachment.html>


More information about the Dev mailing list