|
[PATCH 0/1] Bug #528 fixing
Hi Lianhao, These patches are just what we need, thanks. We do however need to go one step further and complete the change which is to remove the idea of "cross-canadian" packages from the packaging b
Hi Lianhao, These patches are just what we need, thanks. We do however need to go one step further and complete the change which is to remove the idea of "cross-canadian" packages from the packaging b
|
By
...
· #536
·
|
|
why cp in do_install() change file permission mode?
do_install and all tasks that work on the output of do_install run under pseduo which can mean the permissions on disk might not match the real permissions as seen within a pseduo session. To illustra
do_install and all tasks that work on the output of do_install run under pseduo which can mean the permissions on disk might not match the real permissions as seen within a pseduo session. To illustra
|
By
...
· #535
·
|
|
Add extra parameters for qemu script
My gut feeling is that having some simplified way to trigger possibly complex option combinations is still desirable but adding a way to pass additional custom commandline is equally good. This gives
My gut feeling is that having some simplified way to trigger possibly complex option combinations is still desirable but adding a way to pass additional custom commandline is equally good. This gives
|
By
...
· #530
·
|
|
PULL] ADT installer script implementation, Liping Ke
Hi Liping, Jessica and team, I had a quick look over this and have a few comments. I'm in critical review mode and don't have a lot of time so please don't take any of this feedback the wrong way, I j
Hi Liping, Jessica and team, I had a quick look over this and have a few comments. I'm in critical review mode and don't have a lot of time so please don't take any of this feedback the wrong way, I j
|
By
...
· #518
·
|
|
strange bitbake error
Is there a release tarball we can use? If not, we might end up hosting a release tarball for it somewhere given this piece of software's position in the build process. I'd like to axe our cvs dependen
Is there a release tarball we can use? If not, we might end up hosting a release tarball for it somewhere given this piece of software's position in the build process. I'd like to axe our cvs dependen
|
By
...
· #501
·
|
|
[poky] Adding extra metadata to Yocto/Poky
That is the intent but we don't currently have the tooling to make repos per external layer work nicely for the end user (not that I think its too hard to create). This repo give us a way to experimen
That is the intent but we don't currently have the tooling to make repos per external layer work nicely for the end user (not that I think its too hard to create). This repo give us a way to experimen
|
By
...
· #494
·
|
|
Adding extra metadata to Yocto/Poky
Hi, We're in a position where we have people wanting to extend Poky but wondering exactly how to add their own layer and make Poky useful for their specific use cases. This is a topic I want to work w
Hi, We're in a position where we have people wanting to extend Poky but wondering exactly how to add their own layer and make Poky useful for their specific use cases. This is a topic I want to work w
|
By
...
· #493
·
|
|
strange bitbake error
Hi Nitin, Its probably exactly this change the breaks things. git SRC_URIs have a dependency on git-native. git-native probably depends on gnu-config-native indirectly. The end result is a circular de
Hi Nitin, Its probably exactly this change the breaks things. git SRC_URIs have a dependency on git-native. git-native probably depends on gnu-config-native indirectly. The end result is a circular de
|
By
...
· #492
·
|
|
LIC_FILES_CHKSUM issue
Its not the complete solution but I thought the traceback you saw was very confusing. The same error now would give: | NOTE: Checking autotools environment for common misconfiguration | FATAL: Gettext
Its not the complete solution but I thought the traceback you saw was very confusing. The same error now would give: | NOTE: Checking autotools environment for common misconfiguration | FATAL: Gettext
|
By
...
· #458
·
|
|
LIC_FILES_CHKSUM issue
Let me just cut your error down to the above. Its saying you need to add gettext to DEPENDS. The rest of the python traceback looks corrupt and is just confusing the issue. We have some things in plan
Let me just cut your error down to the above. Its saying you need to add gettext to DEPENDS. The rest of the python traceback looks corrupt and is just confusing the issue. We have some things in plan
|
By
...
· #457
·
|
|
AUTOTOOLS_STAGE_PKGCONFIG still used?
No, it used to do something but hasn't for over a year in either OE or Poky. Its not needed and can be removed. I've pushed a patch to poky removing the references and acked your patch for OE. Cheers,
No, it used to do something but hasn't for over a year in either OE or Poky. Its not needed and can be removed. I've pushed a patch to poky removing the references and acked your patch for OE. Cheers,
|
By
...
· #456
·
|
|
Request for Reviews and future package updates
It would be nice to have a section in the wiki with the minimum recipe requirements documented. We certainly have some but I'm not sure everything is written down in one place? Cheers, Richard
It would be nice to have a section in the wiki with the minimum recipe requirements documented. We certainly have some but I'm not sure everything is written down in one place? Cheers, Richard
|
By
...
· #348
·
|
|
inc files in recipes
git mv does not preserve history. Some of git's tools can detect renames though (e.g. git diff -M). The .inc files are kept around as it mirrors what is in OpenEmbedded. We'll continue to do that unti
git mv does not preserve history. Some of git's tools can detect renames though (e.g. git diff -M). The .inc files are kept around as it mirrors what is in OpenEmbedded. We'll continue to do that unti
|
By
...
· #347
·
|
|
inc files in recipes
Git does not track renames. Some of its tools can however detect renames which is subtly different. See "git diff -M" which detects renames for example. Cheers, Richard
Git does not track renames. Some of its tools can however detect renames which is subtly different. See "git diff -M" which detects renames for example. Cheers, Richard
|
By
...
· #346
·
|
|
Yocto weekly bug trend charts -- WW46
For WW45, many more bugs look to have been fixed than submitted yet the overall count still rose? Cheers, Richard
For WW45, many more bugs look to have been fixed than submitted yet the overall count still rose? Cheers, Richard
|
By
...
· #312
·
|
|
Questions based on sysroot testing
Hi Jessica, This is desired behaviour, you should *never* be mixing host and target system headers or libraries. The current behaviour is plain wrong and if I'd known it was doing that, I'd have fixed
Hi Jessica, This is desired behaviour, you should *never* be mixing host and target system headers or libraries. The current behaviour is plain wrong and if I'd known it was doing that, I'd have fixed
|
By
...
· #309
·
|
|
problem with fetching?
I don't have any fix for the fetcher ready straight away but this sounds like a testcase we can reproduce. We actually have some plans to do a redesign of the fetcher code to address issues like this
I don't have any fix for the fetcher ready straight away but this sounds like a testcase we can reproduce. We actually have some plans to do a redesign of the fetcher code to address issues like this
|
By
...
· #244
·
|
|
Distro 1.0 Planning minutes
Yes, that is the plan. I'm hoping this allows us to rigorously check package dependencies and whilst we might not default to it all the time, it would allow us to test this periodically. This currentl
Yes, that is the plan. I'm hoping this allows us to rigorously check package dependencies and whilst we might not default to it all the time, it would allow us to test this periodically. This currentl
|
By
...
· #239
·
|
|
problem with fetching?
It defaults to "build/downloads" so in the build directory unless you changed it in local.conf. Cheers, Richard
It defaults to "build/downloads" so in the build directory unless you changed it in local.conf. Cheers, Richard
|
By
...
· #238
·
|
|
two layers: hardware and distro.
Hi, Yes, this sounds like a very reasonable approach. In general (this applies to anyone out there), we're interested to know what kinds of software people use so please let us know what you're puttin
Hi, Yes, this sounds like a very reasonable approach. In general (this applies to anyone out there), we're interested to know what kinds of software people use so please let us know what you're puttin
|
By
...
· #236
·
|