The branch is not needed any more when it has been removed from the repo, so we
also need remove its layerbranch, otherwise it still can be got from the web,
which causes confusions.
Note, we have to move the location of tinfiol's code to make it can be shutdown
correctly.
Signed-off-by: Robert Y
-p, --prune
Before fetching, remove any remote-tracking references that no longer exist
on the remote.
Fixed:
$ git push origin :test_branch
$ ./update.py
The test_branch was still in fetched local repo which was incorrect, it should
be gone since it has been removed by upstream.
Signed-off
It doesn't need to be so ahead since we only need it when writing database, and
a following patch will remove layerbranch from database when the branch had
been removed from the repo, it's not easy to do the work in
transaction.atomic() block.
Signed-off-by: Robert Yang
---
layerindex/update_lay
Add an option "-a" to update actual branch for layer and bitbake, it is
useful when there are many layers and need update actual branches
frequantly. We only can update them via website without this patch,
which is not funny and easy to make mistakes.
* It works with "-l", and "-l bitbake" means u
It never works since it is in the middle of transaction.atomic() block, and
update.py doesn't need it any more, so remove it.
Signed-off-by: Robert Yang
---
layerindex/update.py | 4 +---
layerindex/update_layer.py | 27 ---
2 files changed, 1 insertion(+), 30 dele
Othewise it may cause troubles to the function who calls it.
Signed-off-by: Robert Yang
---
layerindex/recipeparse.py | 3 +++
1 file changed, 3 insertions(+)
diff --git a/layerindex/recipeparse.py b/layerindex/recipeparse.py
index dd85bc3..f2a5235 100644
--- a/layerindex/recipeparse.py
+++ b/l
* Problems
The update.py couldn't handle new (not only new branch, in fact, but also
existing branches, see below for more info) branch well, for example, there are
3 layers: layer_A, layer_B and layer_C, and create new branch "branch_1" for
them, and they have depends:
layer_A -> layer_B -> layer
Fixed:
$ ./update.py -l meta-oe,not_existed
It should report error that "not_existed" doesn't exist, but it didn't, this was
because __in matches any of them.
Signed-off-by: Robert Yang
---
layerindex/update.py | 11 +++
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a/laye
Fixed:
- set LAYERDEPENDS_openembedded-layer = "core"
- $ "update.py -l meta-oe -b master"
Check from web, its dependency is "openembedded-core"
- Change LAYERDEPENDS_openembedded-layer = "foo"
- Run "update.py -l meta-oe -b master"
Check from web, its dependency is "openembedded-co
The _add_dependency() uses:
if layerbranch.collection:
var_name = layerbranch.collection
The layerbranch.collection is none if it is newly created, thus it can't get
LAYERDEPENDS, because what defined in layer.conf is LAYERDEPENDS_,
but what it would get is LAYERDEPENDS_, this patch can fix th
* V3:
- Better error messages when required collections not found
- Delete layerbranch for non-existed branch
- update_layer.py: remove --update-dependencies
* V2:
- Remove "import bb" from update.py to avoid causing confusions when switch
branches.
* V1:
- The "-a ACTUAL_BRANCH" is a
The layerbranch is not used in parse_layer(), so remove it.
Signed-off-by: Robert Yang
---
layerindex/layerconfparse.py | 2 +-
layerindex/tools/import_layer.py | 2 +-
layerindex/update_layer.py | 4 ++--
3 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/layerindex/layerc
+ Joshua
On 06/01/2017 12:32 PM, Jose Lamego wrote:
> From: Anibal Limon
>
> A forced build fails if no options are passed through command
> line (using "-o OPTIONS").
>
> This change allows build to use default options if none are passed
> at the command line.
>
> Signed-off-by: Jose Lamego
From: Anibal Limon
A forced build fails if no options are passed through command
line (using "-o OPTIONS").
This change allows build to use default options if none are passed
at the command line.
Signed-off-by: Jose Lamego
---
bin/forcebuild.py | 6 +-
1 file changed, 5 insertions(+), 1 d
On 06/01/2017 09:09 AM, Ismo Puustinen wrote:
Add support for sets and IPv4 masquarade.
This should go to the linux-yocto mailing list (and preferably
cc' me), but I noticed this and it looks fine to me.
I've now queued it with some other config changes that will go
out shortly.
Bruce
Sign
How does one change the terminal font (size) used by matchbox-terminal
in the sato desktop? I tried the 'matchbox-appearance' app and it didn't
have any affect, nor could I see a way to change the font.
Thanks
--
Gary Thomas
Hi,
I'm updating the meta-mono layer with support to build the test
core-image-mono image under pyro (fine with morty).
It's getting to the point where it starts to create the root file-system
image then fails with a transaction check error:
...
Running transaction check
Transaction check
On 2017-06-01 15:46, Burton, Ross wrote:
On 1 June 2017 at 14:38, Gary Thomas mailto:g...@mlbassoc.com>> wrote:
Thanks for the suggestion. Sadly, still no go.
No idea then. CCing Alejandro...
Very interesting - I'm building two different system images for this
target and I tried to ap
On 1 June 2017 at 14:38, Gary Thomas wrote:
> Thanks for the suggestion. Sadly, still no go.
>
No idea then. CCing Alejandro...
Ross
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
On 2017-06-01 15:31, Burton, Ross wrote:
On 1 June 2017 at 08:43, Gary Thomas mailto:g...@mlbassoc.com>> wrote:
In my local.conf, I have this (to save space in my embedded image):
BAD_RECOMMENDATIONS = "udev-rules-imx eudev-hwdb"
Try installing just udev-hwdb, my RPROVIDES patch in
On 1 June 2017 at 08:43, Gary Thomas wrote:
> In my local.conf, I have this (to save space in my embedded image):
> BAD_RECOMMENDATIONS = "udev-rules-imx eudev-hwdb"
>
Try installing just udev-hwdb, my RPROVIDES patch in oe-core dea267 may be
been wrong.
Ross
--
_
Add support for sets and IPv4 masquarade.
Signed-off-by: Ismo Puustinen
---
features/nf_tables/nf_tables.cfg | 7 +++
1 file changed, 7 insertions(+)
diff --git a/features/nf_tables/nf_tables.cfg b/features/nf_tables/nf_tables.cfg
index 5e085ce..5f518f1 100644
--- a/features/nf_tables/nf_ta
Hey Steve,
That's great to hear, and thanks for the followup :-)
Otavio has since pushed everything to master, so hopefully the kludges
aren't required anymore.
Best regards,
Trevor
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yo
On Thu, Jun 1, 2017 at 12:23 PM, Paul Barker wrote:
> On Thu, Jun 1, 2017 at 8:10 AM, Martin Jansa
> wrote:
> > And it's not clear from the diff you send, but like linux-yocto-dev.bb
> > example above, the recipe needs to be renamed from
> linux-raspberrypi_dev.bb
> > to linux-raspberrypi-dev.bb
On Thu, Jun 1, 2017 at 8:10 AM, Martin Jansa wrote:
> And it's not clear from the diff you send, but like linux-yocto-dev.bb
> example above, the recipe needs to be renamed from linux-raspberrypi_dev.bb
> to linux-raspberrypi-dev.bb to make it different provider.
>
> On Thu, Jun 1, 2017 at 9:08 AM
In my local.conf, I have this (to save space in my embedded image):
BAD_RECOMMENDATIONS = "udev-rules-imx eudev-hwdb"
Is there a different way I can trim these packages, e.g. leave them in for some
images
and leave them out for others?
Also, today, I wanted to just test/try eudev-hwdb, so on
On 2017-06-01 06:32, Paul Eggleton wrote:
On Thursday, 1 June 2017 3:44:49 PM NZST Gary Thomas wrote:
On 2017-06-01 05:28, Paul Eggleton wrote:
It ought to be. At face value it should be finding the files in either
place - we'd need to debug the code to find out why it isn't. Is that
something
And it's not clear from the diff you send, but like linux-yocto-dev.bb
example above, the recipe needs to be renamed from linux-raspberrypi_dev.bb
to linux-raspberrypi-dev.bb to make it different provider.
On Thu, Jun 1, 2017 at 9:08 AM, Martin Jansa wrote:
> Yes, Paul approach looks good to me,
Yes, Paul approach looks good to me, I think it was what was suggested in
first replies to my SRCREV change and I agree with that, I just haven't had
time to send updated patch.
Paul if you have the patch ready please send it, thanks!.
On Thu, Jun 1, 2017 at 8:10 AM, Paul Barker wrote:
> On Thu
29 matches
Mail list logo
