Hmm when I visit the git repository, I think that the way the code is base
is placed is not the best.
I see develop branch to have 11commits ahead and 9commits behind master.
using git is that :
there are always at least two branches
1) Master.
It is the default and every time -t the code here is stable . The code here
is always the last release of the project. So the develop branch is merge
with the master during release.
Developers do not commit or create pull request against this branch.
2) the Develop Branch
It is the current working branch. All pull request by developers are
against this branch.
This pull request are reviewed then merge into this branch. it can be
broken at times but that can just be temporal.
SO I do not understand whether this is the same flow we use here or it is
different.
Thanks
"A Goal is a Dream with a Plan and a Dateline"
Do On to Others what you will like them to do on to you.'The Golden Rule'
The CEO of ABEBOH
Computer Software Engineering Student
Music DJ . Artiste at Casky Black's Record
Regional Coordinator and CAC Member at Mozilla Campus Club Program.
On Thu, Jun 22, 2017 at 5:21 PM, Ilario Gelmetti <iochesonome(a)gmail.com>
wrote:
Ok, so you're using lime-sdk develop which points
to lede-17.01 which is
2 months old.
https://github.com/libremesh/lime-sdk/compare/develop#diff-
f2fe3255fb192223dd3dbef288fe215f
Better using lime-sdk master which points to lede v17.01.2 just 12 days
old.
Can you try to change to lime-sdk master using "git checkout master" and
see if there still the error? Maybe changing to lime-sdk via git
checkout is not enough and you will need to delete the full lime-sdk
directory and start again (maybe there's a faster way to clean and start
again but I don't know).
Let us know!
Ilario
On 06/22/2017 05:57 PM, Nges B wrote:
feed/packages.git;lede-17.01
src-git luci
https://git.lede-project.org/project/luci.git
src-git routing
https://git.lede-project.org/feed/routing.git
src-git telephony
https://git.lede-project.org/feed/telephony.git
src-git libremesh
https://github.com/libremesh/lime-packages.git;develop
src-git libremap
https://github.com/libremap/libremap-agent-openwrt.git;master
src-git limeui
https://github.com/libremesh/lime-ui-ng.git;master
Yes normally , when working on a developing project, using git, it is
always good to work with the develop branch since the master branch is
the release code. Fortunately, when I clone the code and added the
develop branch, I discovered that it was even with the master branch, so
both branches will have the same error.
Thanks and waiting to hear from you.
"A Goal is a Dream with a Plan and a Dateline"
Do On to Others what you will like them to do on to you.'The Golden Rule'
The CEO of ABEBOH
Computer Software Engineering Student
Music DJ . Artiste at Casky Black's Record
Regional Coordinator and CAC Member at Mozilla Campus Club Program.
On Thu, Jun 22, 2017 at 4:07 PM, Ilario Gelmetti <iochesonome(a)gmail.com
<mailto:iochesonome@gmail.com>> wrote:
On 06/22/2017 04:57 PM, Nges B wrote:
> Hello , I do not know about LEDE trunk for now. I simply forked
the the
> lime-sdk , then clone it and started
working on it. I dont know
whether
it is
LEDE trunk or not.
Here is the contain of my Config.default
Ok, can you post feeds.conf.default? Just:
cat /home/nges/lime-sdk/feeds.conf.default
I suspected that somehow (no idea of how this could have happened)
you're using LEDE trunk (development version of what we're using as a
base for LibreMesh) 'cause I saw a similar error from a Pau's comment
where he said he was using trunk:
https://github.com/libremesh/lime-sdk/issues/2# issuecomment-304510970
<https://github.com/libremesh/lime-sdk/issues/2#
issuecomment-304510970>
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users