parse: warn on trailing whitespace after line continuation backslash
PATCH 1/1 parse: warn on trailing whitespace after line continuation backslash
rstrip() is called before checking for backslash, so trailing spaces or tabs after "\" go unnoticed. For example:
file://foo.patch \<TAB>
file://bar.patch \The first line has a trailing tab after the backslash that is invisible but ends up in patch context, causing patches to fail to apply on trees where it was cleaned up.
Emit a warning when this is detected so developers can fix it early.
Tested with bitbake-selftest:
$ python3 -m unittest lib.bb.tests.parse.ParseTest.test_parse_trailing_whitespace_continuation -v $ python3 -m unittest lib.bb.tests.parse.ParseTest.test_parse_clean_continuation_no_warning -v
2 tests OK
---
Problem:
Ran into this while submitting libssh2 CVE patches to both master and wrynose. The libssh2_1.11.1.bb on master has a stray tab after the backslash on the CVE-2025-15661-3.patch line. Patches adding new file:// lines below it applied fine on master but git-am refused them on wrynose because that branch doesn't have the trailing tab — context mismatch.
Other recipes in oe-core with the same issue:
autoconf_2.73.bb:2
perl_5.44.0.bb:313,314
mc_4.8.33.bb:50,51
libxml-sax-perl_1.02.bb:4
A separate series will follow to fix the trailing whitespace in the affected recipes.
lib/bb/parse/parse_py/BBHandler.py | 6 +++++- lib/bb/parse/parse_py/ConfHandler.py | 10 ++++++++-- lib/bb/tests/parse.py | 19 +++++++++++++++++++ 3 files changed, 32 insertions(+), 3 deletions(-)
lib/bb/parse/parse_py/BBHandler.py +5 -1
@@ -104,7 +104,11 @@ def get_statements(filename, absolute_filename, base_name): lineno = lineno + 1 s = f.readline() if not s: break - s = s.rstrip() + # Warn if trailing whitespace exists after a continuation backslash + raw = s.rstrip('\n').rstrip('\r') + s = raw.rstrip() + if s and s[-1] == '\\' and raw != s: + bb.warn("Trailing whitespace after line continuation backslash in %s, line %s" % (filename, lineno)) feeder(lineno, s, filename, base_name, statements) if __inpython__:
lib/bb/parse/parse_py/ConfHandler.py +8 -2
@@ -134,12 +134,18 @@ def handle(fn, data, include, baseconfig=False): # skip empty lines if not w: continue - s = s.rstrip() + raw = s.rstrip('\n').rstrip('\r') + s = raw.rstrip() + if s and s[-1] == '\\' and raw != s: + bb.warn("Trailing whitespace after line continuation backslash in %s, line %s" % (fn, lineno)) while s[-1] == '\\': line = f.readline() origline += line - s2 = line.rstrip() + raw2 = line.rstrip('\n').rstrip('\r') + s2 = raw2.rstrip() lineno = lineno + 1 + if s2 and s2[-1] == '\\' and raw2 != s2: + bb.warn("Trailing whitespace after line continuation backslash in %s, line %s" % (fn, lineno)) if (not s2 or s2 and s2[0] != "#") and s[0] == "#" : bb.fatal("There is a confusing multiline, partially commented expression starting on line %s of file %s:\n%s\nPlease clarify whether this is all a comment or should be parsed." % (origlineno, fn, origline))
lib/bb/tests/parse.py +19 -0
@@ -638,3 +638,22 @@ EXTRA_OECONF:append = " foobar" output = run_bitbake(["bitbake", "-e", "recipe-file1"], builddir, extraenv).splitlines() self.assertIn('BBCLASS_FILE="recipe-file.inc"', output) self.assertIn(f'BBCLASS_RECIPE_FILE="recipe-file1.bb"', output) + + trailing_whitespace_continuation = "A = \"1 \\\t \n2\"\n" + + def test_parse_trailing_whitespace_continuation(self): + """Test that trailing whitespace after backslash continuation emits a warning""" + with self.parsehelper(self.trailing_whitespace_continuation) as f: + with self.assertLogs('BitBake', level='WARNING') as cm: + d = bb.parse.handle(f.name, self.d)[''] + self.assertTrue(any("Trailing whitespace after line continuation backslash" in msg for msg in cm.output)) + # Verify it still parses correctly despite the warning + self.assertEqual(d.getVar("A"), "1 2") + + clean_continuation = "A = \"1 \\\n2\"\n" + + def test_parse_clean_continuation_no_warning(self): + """Test that clean backslash continuation does not warn""" + with self.parsehelper(self.clean_continuation) as f: + d = bb.parse.handle(f.name, self.d)[''] + self.assertEqual(d.getVar("A"), "1 2")
Quoted 18 lines · Jaipaul Cheernam via lists.openembedded.org
rstrip()is called before checking for backslash, so trailing spaces or tabs after "\" go unnoticed. For example:file://foo.patch \<TAB>
file://bar.patch \The first line has a trailing tab after the backslash that is invisible but ends up in patch context, causing patches to fail to apply on trees where it was cleaned up.
Emit a warning when this is detected so developers can fix it early.
Tested with bitbake-selftest:
$ python3 -m unittest lib.bb.tests.parse.ParseTest.test_parse_trailing_whitespace_continuation -v $ python3 -m unittest lib.bb.tests.parse.ParseTest.test_parse_clean_continuation_no_warning -v2 tests OK
Quoted 8 lines
Signed-off-by Jaipaul Cheernam <[email protected]>---
Problem:
Ran into this while submitting libssh2 CVE patches to both master and wrynose. The libssh2_1.11.1.bb on master has a stray tab after the backslash on the CVE-2025-15661-3.patch line. Patches adding new file:// lines below it applied fine on master but git-am refused them on wrynose because that branch doesn't have the trailing tab — context mismatch.
This seems like a lot of code and complexity for what is in reality quite a minor issue which whilst annoying, doesn't actually break anything?
Cheers,
Richard
Quoted 27 lines · Richard Purdie
Quoted 18 lines · Jaipaul Cheernam via lists.openembedded.org
rstrip()is called before checking for backslash, so trailing spaces or tabs after "\" go unnoticed. For example:file://foo.patch \<TAB>
file://bar.patch \The first line has a trailing tab after the backslash that is invisible but ends up in patch context, causing patches to fail to apply on trees where it was cleaned up.
Emit a warning when this is detected so developers can fix it early.
Tested with bitbake-selftest:
$ python3 -m unittest lib.bb.tests.parse.ParseTest.test_parse_trailing_whitespace_continuation -v $ python3 -m unittest lib.bb.tests.parse.ParseTest.test_parse_clean_continuation_no_warning -v2 tests OK
Quoted 8 lines
Signed-off-by Jaipaul Cheernam <[email protected]>---
Problem:
Ran into this while submitting libssh2 CVE patches to both master and wrynose. The libssh2_1.11.1.bb on master has a stray tab after the backslash on the CVE-2025-15661-3.patch line. Patches adding new file:// lines below it applied fine on master but git-am refused them on wrynose because that branch doesn't have the trailing tab — context mismatch.
Quoted 6 lines
This seems like a lot of code and complexity for what is in reality quite a minor issue which whilst annoying, doesn't actually break anything?
Cheers,
Richard
Hi Richard,
Fair point — it doesn't break parsing itself and the code churn is larger than ideal for a warning.
Would you prefer if I just submitted the oe-core fixes to clean up the affected recipes instead and dropped this bitbake change? That solves the immediate problem without adding complexity to the parser.
Alternatively, I could reduce this to a bb.note() (debug-level) so it's only visible with -v, keeping it minimal.
Happy to go either way.
Thanks
Quoted 8 lines · Jaipaul Cheernam
Hi Richard,
Fair point — it doesn't break parsing itself and the code churn is larger than ideal for a warning.
Would you prefer if I just submitted the oe-core fixes to clean up the affected recipes instead and dropped this bitbake change? That solves the immediate problem without adding complexity to the parser.
You should definitely send that clean up for oe-core.
I was toying with the idea we just make whitespace after a line break character a fatal parsing error. Most of the fatal errors are inside feeder() rather than where you changed the code.
I then looked at the code further and it isn't just trailing whitespace after "\" that is an issue. For example, after "}" closing a function could also be an issue in the same way. I didn't look in detail beyond that, there will be further similar issues though and that does mean your patch is incomplete :/.
Quoted 2 lines
Alternatively, I could reduce this to a
bb.note()(debug-level) so it's only visible with -v, keeping it minimal.
I think this needs further thought and some wider testing of how widespread trailing whitespace is.
We might just want to make any trailing spaces a warning since we currently just swallow and hide it unconditionally?
Cheers,
Richard
Quoted 10 lines · Richard Purdie
Quoted 8 lines · Jaipaul Cheernam
Hi Richard,
Fair point — it doesn't break parsing itself and the code churn is
larger than ideal for a warning.Would you prefer if I just submitted the oe-core fixes to clean up
the affected recipes instead and dropped this bitbake change? That solves the immediate problem without adding complexity to the parser.You should definitely send that clean up for oe-core.
Hi Richard,
Thanks for the detailed feedback.
I will send a clean-up patch.
Quoted 3 lines
I was toying with the idea we just make whitespace after a line break character a fatal parsing error. Most of the fatal errors are inside
feeder()rather than where you changed the code.
That would be the cleanest long-term. A fatal error for whitespace after \ makes sense since the backslash must be the last character — anything after it is always wrong.
Quoted 5 lines
I then looked at the code further and it isn't just trailing whitespace after "\" that is an issue. For example, after "}" closing a function could also be an issue in the same way. I didn't look in detail beyond that, there will be further similar issues though and that does mean your patch is incomplete :/.
Good point, I hadn't considered that.
Quoted 7 lines
Quoted 2 lines
Alternatively, I could reduce this to a
bb.note()(debug-level) so
it's only visible with -v, keeping it minimal.I think this needs further thought and some wider testing of how widespread trailing whitespace is.
We might just want to make any trailing spaces a warning since we currently just swallow and hide it unconditionally?
I tried this — warned on any trailing whitespace in all parsed lines (comparing raw line minus newline against rstrip'd version). Running core-image-minimal:
- 1665 total warnings (due to repeated re-parse of same files)
- 59 unique (distinct file:line)
- 31 files affected (.bbclass, .bb, .inc, .conf)
Most are in bbclass files like sanity.bbclass, buildstats.bbclass, useradd.bbclass, kernel-yocto.bbclass, libc-package.bbclass etc. The duplication from re-parsing makes it noisy without some form of dedup.
A few options for v2:
1. Keep it narrow — only warn after \ and } (the cases that actually cause patch conflicts). Around 10 unique warnings.
2. Warn on everything but with dedup (a module-level set). Cleaner output but adds state to the parser.
3. Warn on everything and send a cleanup series fixing all 59 instances in oe-core. Then the warning stays as a guard for future submissions.
What would you prefer?
Thanks,
Jaipaul
Quoted 5 lines
Cheers,
Richard
PATCH v2 1/1 parse: warn on trailing whitespace in parsed lines
In reply to Jaipaul Cheernamrstrip() silently strips trailing whitespace before processing. This hides invisible spaces or tabs that end up in patch context and cause patches to fail to apply across branches.
Warn on any line with trailing whitespace so developers can fix it early.
---
Changes since v1:
- Broadened from just backslash continuation to any trailing whitespace, as suggested by Richard.
Real example from oe-core master (libssh2_1.11.1.bb, line 18):
file://CVE-2025-15661-3.patch \<TAB>
This caused CVE patches to fail to apply on wrynose where the trailing tab was absent — invisible context mismatch.
Full parse (bitbake -p) across oe-core + meta-openembedded (2970 recipes):
- 228 unique trailing whitespace instances (verified, 0 false positives)
- 82 files affected (53 .bb, 19 .bbclass, 8 .inc, 2 .conf)
- 92 in oe-core, 136 in meta-openembedded
bbclass files like useradd.bbclass, sanity.bbclass, buildstats.bbclass account for most of the warning noise since they are re-parsed for every recipe that inherits them.
Tested with bitbake-selftest:
$ PYTHONPATH=lib python3 -m unittest lib.bb.tests.parse.ParseTest -v 3 new tests pass, no regressions.
A separate cleanup series will follow to fix the affected files.
lib/bb/parse/parse_py/BBHandler.py | 5 ++++- lib/bb/parse/parse_py/ConfHandler.py | 10 ++++++++-- lib/bb/tests/parse.py | 28 ++++++++++++++++++++++++++++ 3 files changed, 40 insertions(+), 3 deletions(-)
lib/bb/parse/parse_py/BBHandler.py +4 -1
@@ -104,7 +104,10 @@ def get_statements(filename, absolute_filename, base_name): lineno = lineno + 1 s = f.readline() if not s: break - s = s.rstrip() + raw = s.rstrip('\n').rstrip('\r') + s = raw.rstrip() + if s and raw != s: + bb.warn("Trailing whitespace in %s, line %s" % (filename, lineno)) feeder(lineno, s, filename, base_name, statements) if __inpython__:
lib/bb/parse/parse_py/ConfHandler.py +8 -2
@@ -134,12 +134,18 @@ def handle(fn, data, include, baseconfig=False): # skip empty lines if not w: continue - s = s.rstrip() + raw = s.rstrip('\n').rstrip('\r') + s = raw.rstrip() + if s and raw != s: + bb.warn("Trailing whitespace in %s, line %s" % (fn, lineno)) while s[-1] == '\\': line = f.readline() origline += line - s2 = line.rstrip() + raw2 = line.rstrip('\n').rstrip('\r') + s2 = raw2.rstrip() lineno = lineno + 1 + if s2 and raw2 != s2: + bb.warn("Trailing whitespace in %s, line %s" % (fn, lineno)) if (not s2 or s2 and s2[0] != "#") and s[0] == "#" : bb.fatal("There is a confusing multiline, partially commented expression starting on line %s of file %s:\n%s\nPlease clarify whether this is all a comment or should be parsed." % (origlineno, fn, origline))
lib/bb/tests/parse.py +28 -0
@@ -638,3 +638,31 @@ EXTRA_OECONF:append = " foobar" output = run_bitbake(["bitbake", "-e", "recipe-file1"], builddir, extraenv).splitlines() self.assertIn('BBCLASS_FILE="recipe-file.inc"', output) self.assertIn(f'BBCLASS_RECIPE_FILE="recipe-file1.bb"', output) + + trailing_whitespace_continuation = "A = \"1 \\\t \n2\"\n" + + def test_parse_trailing_whitespace_continuation(self): + """Test that trailing whitespace after backslash continuation emits a warning""" + with self.parsehelper(self.trailing_whitespace_continuation) as f: + with self.assertLogs('BitBake', level='WARNING') as cm: + d = bb.parse.handle(f.name, self.d)[''] + self.assertTrue(any("Trailing whitespace" in msg for msg in cm.output)) + self.assertEqual(d.getVar("A"), "1 2") + + trailing_whitespace_after_value = 'A = "1" \n' + + def test_parse_trailing_whitespace_after_value(self): + """Test that trailing whitespace after a normal value emits a warning""" + with self.parsehelper(self.trailing_whitespace_after_value) as f: + with self.assertLogs('BitBake', level='WARNING') as cm: + d = bb.parse.handle(f.name, self.d)[''] + self.assertTrue(any("Trailing whitespace" in msg for msg in cm.output)) + self.assertEqual(d.getVar("A"), "1") + + clean_continuation = "A = \"1 \\\n2\"\n" + + def test_parse_clean_continuation_no_warning(self): + """Test that clean backslash continuation does not warn""" + with self.parsehelper(self.clean_continuation) as f: + d = bb.parse.handle(f.name, self.d)[''] + self.assertEqual(d.getVar("A"), "1 2")
PATCH v2 1/1 parse: warn on trailing whitespace in parsed lines
In reply to Jaipaul Cheernamrstrip() silently strips trailing whitespace before processing. This hides invisible spaces or tabs that end up in patch context and cause patches to fail to apply across branches.
Warn on any line with trailing whitespace so developers can fix it early.
---
Changes since v1:
- Broadened from just backslash continuation to any trailing whitespace, as suggested by Richard.
Real example from oe-core master (libssh2_1.11.1.bb, line 18):
file://CVE-2025-15661-3.patch \<TAB>
This caused CVE patches to fail to apply on wrynose where the trailing tab was absent — invisible context mismatch.
Full parse (bitbake -p) across oe-core + meta-openembedded (2970 recipes):
- 228 unique trailing whitespace instances (verified, 0 false positives)
- 82 files affected (53 .bb, 19 .bbclass, 8 .inc, 2 .conf)
- 92 in oe-core, 136 in meta-openembedded
bbclass files like useradd.bbclass, sanity.bbclass, buildstats.bbclass account for most of the warning noise since they are re-parsed for every recipe that inherits them.
Tested with bitbake-selftest:
$ PYTHONPATH=lib python3 -m unittest lib.bb.tests.parse.ParseTest -v 3 new tests pass, no regressions.
A separate cleanup series will follow to fix the affected files.
lib/bb/parse/parse_py/BBHandler.py | 5 ++++- lib/bb/parse/parse_py/ConfHandler.py | 10 ++++++++-- lib/bb/tests/parse.py | 28 ++++++++++++++++++++++++++++ 3 files changed, 40 insertions(+), 3 deletions(-)
lib/bb/parse/parse_py/BBHandler.py +4 -1
@@ -104,7 +104,10 @@ def get_statements(filename, absolute_filename, base_name): lineno = lineno + 1 s = f.readline() if not s: break - s = s.rstrip() + raw = s.rstrip('\n').rstrip('\r') + s = raw.rstrip() + if s and raw != s: + bb.warn("Trailing whitespace in %s, line %s" % (filename, lineno)) feeder(lineno, s, filename, base_name, statements) if __inpython__:
lib/bb/parse/parse_py/ConfHandler.py +8 -2
@@ -134,12 +134,18 @@ def handle(fn, data, include, baseconfig=False): # skip empty lines if not w: continue - s = s.rstrip() + raw = s.rstrip('\n').rstrip('\r') + s = raw.rstrip() + if s and raw != s: + bb.warn("Trailing whitespace in %s, line %s" % (fn, lineno)) while s[-1] == '\\': line = f.readline() origline += line - s2 = line.rstrip() + raw2 = line.rstrip('\n').rstrip('\r') + s2 = raw2.rstrip() lineno = lineno + 1 + if s2 and raw2 != s2: + bb.warn("Trailing whitespace in %s, line %s" % (fn, lineno)) if (not s2 or s2 and s2[0] != "#") and s[0] == "#" : bb.fatal("There is a confusing multiline, partially commented expression starting on line %s of file %s:\n%s\nPlease clarify whether this is all a comment or should be parsed." % (origlineno, fn, origline))
lib/bb/tests/parse.py +28 -0
@@ -638,3 +638,31 @@ EXTRA_OECONF:append = " foobar" output = run_bitbake(["bitbake", "-e", "recipe-file1"], builddir, extraenv).splitlines() self.assertIn('BBCLASS_FILE="recipe-file.inc"', output) self.assertIn(f'BBCLASS_RECIPE_FILE="recipe-file1.bb"', output) + + trailing_whitespace_continuation = "A = \"1 \\\t \n2\"\n" + + def test_parse_trailing_whitespace_continuation(self): + """Test that trailing whitespace after backslash continuation emits a warning""" + with self.parsehelper(self.trailing_whitespace_continuation) as f: + with self.assertLogs('BitBake', level='WARNING') as cm: + d = bb.parse.handle(f.name, self.d)[''] + self.assertTrue(any("Trailing whitespace" in msg for msg in cm.output)) + self.assertEqual(d.getVar("A"), "1 2") + + trailing_whitespace_after_value = 'A = "1" \n' + + def test_parse_trailing_whitespace_after_value(self): + """Test that trailing whitespace after a normal value emits a warning""" + with self.parsehelper(self.trailing_whitespace_after_value) as f: + with self.assertLogs('BitBake', level='WARNING') as cm: + d = bb.parse.handle(f.name, self.d)[''] + self.assertTrue(any("Trailing whitespace" in msg for msg in cm.output)) + self.assertEqual(d.getVar("A"), "1") + + clean_continuation = "A = \"1 \\\n2\"\n" + + def test_parse_clean_continuation_no_warning(self): + """Test that clean backslash continuation does not warn""" + with self.parsehelper(self.clean_continuation) as f: + d = bb.parse.handle(f.name, self.d)[''] + self.assertEqual(d.getVar("A"), "1 2")
Re: [bitbake-devel] [PATCH v2] parse: warn on trailing whitespace in parsed lines
Quoted 8 lines · Jaipaul Cheernam
rstrip()silently strips trailing whitespace before processing. This hides invisible spaces or tabs that end up in patch context and cause patches to fail to apply across branches.Warn on any line with trailing whitespace so developers can fix it early.
Signed-off-by Jaipaul Cheernam <[email protected]>---
Hi Jaipaul,
Thanks for the v2. I forgot to ask: do you plan to provide an oe-core patch fixing all whitespace issues? As so far, this is adding a lot of warnings during the build:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/4/builds/4405
Thanks,
Mathieu
Signature · 3 lines
Mathieu Dubois-Briand, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
Re: [bitbake-devel] [PATCH v2] parse: warn on trailing whitespace in parsed lines
Hi Mathieu,
Yes , if we agree on solution, I will send patch series to oe-core and metaopenembedded as well .
I will prepare and send them tomorrow .
Regards,
Jaipaul
________________________________
From: Mathieu Dubois-Briand <[email protected]>
Sent: Thursday, August 13, 2026 5:07 PM
To: Jaipaul Cheernam <[email protected]>; [email protected] <[email protected]>
Subject: Re: [bitbake-devel] [PATCH v2] parse: warn on trailing whitespace in parsed lines
Quoted 8 lines · Jaipaul Cheernam
rstrip()silently strips trailing whitespace before processing. This hides invisible spaces or tabs that end up in patch context and cause patches to fail to apply across branches.Warn on any line with trailing whitespace so developers can fix it early.
Signed-off-by Jaipaul Cheernam <[email protected]>---
Hi Jaipaul,
Thanks for the v2. I forgot to ask: do you plan to provide an oe-core patch fixing all whitespace issues? As so far, this is adding a lot of warnings during the build:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/4/builds/4405
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
Re: [PATCH v2] parse: warn on trailing whitespace in parsed lines
Hi Mathieu,
Both oe-core and metaopenembedded serires are accepted.
https://patchwork.yoctoproject.org/project/oe-core/list/?series=49858&archive=both&state=*
https://patchwork.yoctoproject.org/project/oe/list/?series=49954&archive=both&state=*
Can you check on bitbake patch.
Regards,
Jaipaul
Re: [bitbake-devel] [PATCH v2] parse: warn on trailing whitespace in parsed lines
Quoted 11 lines · Jaipaul Cheernam
Hi Mathieu,
Both oe-core and metaopenembedded serires are accepted.
https://patchwork.yoctoproject.org/project/oe-core/list/?series=49858&archive=both&state=*
https://patchwork.yoctoproject.org/project/oe/list/?series=49954&archive=both&state=*Can you check on bitbake patch.
Regards,
Jaipaul
Hi Jaipaul,
I sent a patch to fix the last few things, but we should be good.
I note we have warnings on a few other layers tested on the autobuilder. I can ask the maintainers to fix them once the patch is merged, but I'm sure they would appreciate a patch to fix these.
https://autobuilder.yoctoproject.org/valkyrie/#/builders/75/builds/4317/steps/16/logs/warnings
https://autobuilder.yoctoproject.org/valkyrie/#/builders/89/builds/4284/steps/15/logs/warnings
https://autobuilder.yoctoproject.org/valkyrie/#/builders/14/builds/4270/steps/13/logs/warnings
Thanks,
Mathieu
Signature · 3 lines
Mathieu Dubois-Briand, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
Re: [bitbake-devel] [PATCH v2] parse: warn on trailing whitespace in parsed lines
Quoted 7 lines · Mathieu Dubois-Briand via lists.openembedded.org
Hi Jaipaul,
I sent a patch to fix the last few things, but we should be good.
I note we have warnings on a few other layers tested on the autobuilder. I can ask the maintainers to fix them once the patch is merged, but I'm sure they would appreciate a patch to fix these.
Thanks for testing with my patch, I have sent patches to below warnings in respective upstreams.
Quoted 2 lines
https://autobuilder.yoctoproject.org/valkyrie/#/builders/75/builds/4317/steps/16/logs/warnings
https://lists.yoctoproject.org/g/meta-arm/message/7142
Quoted 1 line
https://autobuilder.yoctoproject.org/valkyrie/#/builders/89/builds/4284/steps/15/logs/warnings
https://lists.openembedded.org/g/openembedded-devel/message/129471
https://lists.yoctoproject.org/g/meta-virtualization/topic/120921550 --> This shows empty to me and dont know the reason ?
are you able to see my patch in mailing list?
Quoted 1 line
https://autobuilder.yoctoproject.org/valkyrie/#/builders/14/builds/4270/steps/13/logs/warnings
MR: https://github.com/aws4embeddedlinux/meta-aws/pull/16872
Regards,
Jaipaul
Re: [bitbake-devel] [PATCH v2] parse: warn on trailing whitespace in parsed lines
In reply to Jaipaul CheernamHi Jaipaul,
Quoted 6 lines · Jaipaul Cheernam via lists.openembedded.org
Both oe-core and metaopenembedded serires are accepted.
https://patchwork.yoctoproject.org/project/oe-core/list/?series=49858&archive=both&state=*
https://patchwork.yoctoproject.org/project/oe/list/?series=49954&archive=both&state=*
Can you check on bitbake patch.
I've given this one a lot of thought and also asked around the community. The general consensus is we don't want to make the parser this pedantic. I think it is fine to fix the whitespace issues and we have done, but the extra complexity in the parser doesn't seem to be in line with where people want to focus their time/energy right now. I'm therefore probably not going to take the bitbake change.
Cheers,
Richard