In poky with systemd enabled, vt102 is selected for getty
causing user to experience a very crappy terminal. Default
TERM to linux.
Signed-off-by: Joel Fernandes
---
v2: Dropped PR bump
.../systemd-serialgetty/serial-getty@.service |1 +
1 file changed, 1 insertion(+)
diff --git
a/me
On Sat, May 3, 2014 at 7:53 PM, Joel Fernandes wrote:
> On 05/03/2014 05:44 PM, Otavio Salvador wrote:
>> On Sat, May 3, 2014 at 7:39 PM, Joel Fernandes wrote:
>>> In poky with systemd enabled, vt102 is selected for getty
>>> causing user to experience a very crappy terminal. Default
>>> TERM to
On 05/03/2014 05:44 PM, Otavio Salvador wrote:
> On Sat, May 3, 2014 at 7:39 PM, Joel Fernandes wrote:
>> In poky with systemd enabled, vt102 is selected for getty
>> causing user to experience a very crappy terminal. Default
>> TERM to linux.
>>
>> Signed-off-by: Joel Fernandes
>
> Don't bump P
On Sat, May 3, 2014 at 7:39 PM, Joel Fernandes wrote:
> In poky with systemd enabled, vt102 is selected for getty
> causing user to experience a very crappy terminal. Default
> TERM to linux.
>
> Signed-off-by: Joel Fernandes
Don't bump PR, this is not needed in this case.
--
Otavio Salvador
In poky with systemd enabled, vt102 is selected for getty
causing user to experience a very crappy terminal. Default
TERM to linux.
Signed-off-by: Joel Fernandes
---
.../systemd-serialgetty/serial-getty@.service |1 +
meta/recipes-core/systemd/systemd_211.bb |1 +
2 files
On 3 May 2014 10:08, Richard Purdie wrote:
>> Could this be the root-cause of so many instances where we've had to
>> add explicit hints that variables should be added to the hash?
>
> Is there really "so many"?
>
> In each case we've seen its been due to the code being python that the
> parser ca
Signed-off-by: Martin Jansa
---
meta/conf/distro/defaultsetup.conf | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/meta/conf/distro/defaultsetup.conf
b/meta/conf/distro/defaultsetup.conf
index 5557350..4437267 100644
--- a/meta/conf/distro/defaultsetup.conf
+++ b/meta/conf/
Hello,
This sounds like a great addition!
On 23 April 2014 05:26, Stoicescu, CorneliuX
wrote:
> 1) Testing recipes updates or new recipes
> (any experience from common recipe build fails can be helpful here)
I recently stumbled on a situation where doing a clean on a recipe did
not remove its
On Sat, May 3, 2014 at 12:23 AM, Trevor Woerner
wrote:
> On 30 April 2014 13:57, Paul Barker wrote:
>> If you can't find
>> a good guide online on how to set this up, let me know and I'll write
>> up a blog post of how I did it.
>
> I'd be interested in reading this, if you wrote it up. Which con
Hello Tudor,
On Fri, May 2, 2014 at 7:21 PM, Tudor Florea wrote:
> mkhelp: generate code for --disable-manual as well
>
> This allows configure --disable-manual to run and build without having
> to regenerate the src/tool_hugehelp.c file which otherwise is necessary
> since we ship tarballs with
There is a fix about to go into bitbake to ensure that datastores
being accessed with a name other than "d" are correctly reflected
in checksums. This will cause this function to add in a number of
dependencies we don't want.
These do need to be properly unravelled in due course but would
only rea
On Sat, 2014-05-03 at 10:03 +0100, Burton, Ross wrote:
> On 2 May 2014 23:07, Richard Purdie
> wrote:
> > It may well do and I've realised the issue:
> >
> > codeparser.py:
> > class PythonParser():
> > getvars = ("d.getVar", "bb.data.getVar", "data.getVar", "d.appendVar",
> > "d.prependVar"
On 2 May 2014 23:07, Richard Purdie wrote:
> It may well do and I've realised the issue:
>
> codeparser.py:
> class PythonParser():
> getvars = ("d.getVar", "bb.data.getVar", "data.getVar", "d.appendVar",
> "d.prependVar")
>
> we probably need to change this to an .endswith(".getVar", ".appen
13 matches
Mail list logo
