From: Frederic Martinsons
Remove backported commit.
Signed-off-by: Frederic Martinsons
---
...8.0.2.bb => crash-cross-canadian_8.0.4.bb} | 0
meta-oe/recipes-kernel/crash/crash.inc| 3 +-
...001-make-src-string-const-in-strlcpy.patch | 69 ---
.../crash/{crash_8.0.2.b
From: Frederic Martinsons
Signed-off-by: Frederic Martinsons
---
.../crash/crash-cross-canadian_8.0.2.bb | 53 +++
1 file changed, 53 insertions(+)
create mode 100644 meta-oe/recipes-kernel/crash/crash-cross-canadian_8.0.2.bb
diff --git a/meta-oe/recipes-kernel/crash/cra
From: Frederic Martinsons
Suppress unused config-site.crash-7.0.9
Signed-off-by: Frederic Martinsons
---
meta-oe/recipes-kernel/crash/crash.inc| 92 +++
.../crash/crash/config-site.crash-7.0.9 | 1 -
meta-oe/recipes-kernel/crash/crash_8.0.2.bb | 89 +---
From: Frederic Martinsons
This series brings a cross canadian recipe for crash utility.
This is particularly usefull for using crash in an sdk to analyze
a vmcore file generated on target.
The following changes since commit 0a0ea87b8dda01a2887a525cef78eb6c3f4c2c32:
pgpool2: use autotools-brok
From: Alexandre Belloni
The current SRCREV is not on any branch anymore, switch to the 1.12.4
branch HEAD which is similar and the only change is irrelevant.
The SRCREV is still referenced from the tag so we could use nobranch here:
github/poco $ git tag --contains f1aefe34a46891b09230422bbc3746
From: Alexandre Belloni
The current SRCREV is not on any branch anymore, switch to the 1.12.4
branch HEAD which is similar and the only change is irrelevant.
Signed-off-by: Alexandre Belloni
---
meta-oe/recipes-support/poco/poco_1.12.4.bb | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(
From: Alexandre Belloni
The current SRCREV is not on any branch anymore, switch to the 1.12.4
branch HEAD which is similar and the only change is irrelevant.
Signed-off-by: Alexandre Belloni
Signed-off-by: Martin Jansa
---
meta-oe/recipes-support/poco/poco_1.12.4.bb | 4 ++--
1 file changed,
On Wed, Dec 13, 2023 at 7:47 PM Khem Raj wrote:
> Hi Alex,
>
> Thanks for the patch. I did not take it since there already was
> another upgrade patch [1] proposed which fixed this issue as well.
> Please report if this issue still persists
1211613642269b7d53bea58b02de7fcd25ece3b9 is still bein