On 2/13/2014 4:17 AM, Eduardo Lima (Etrunko) wrote:
On 02/07/2014 07:51 AM, VanCutsem, Geoffroy wrote:
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.
Yes, this can be adjusted by tagging your repository locally or even in
.gbs.conf. But what really confuses me is the existence of this
platform/upstream/weekeyboard repository. Do you know who is the
maintainer? I only knew about the existence of profile/ivi/weekeyboard,
not of the former.
Eduardo,
Since Tizen Mobile also can use Wayland now, we created the
platform/upstream/weekeyboard for sharing purpose last month according
to the 3.0 development guideline.
thanks,
Michael
Regards, Eduardo
Geoffroy
*From:*[email protected] [mailto:[email protected]]
*On Behalf Of *Zhao, Juan J
*Sent:* Friday, February 07, 2014 7:16 AM
*To:* [email protected]
*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-package
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.
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
