Date   

Re: Query on building applications and catch exceptions across different shared libraries

SIMON BABY
 

No I am not using -fexceptions compiler flag .

Rgds
Simon


On Wednesday, September 2, 2020, Khem Raj <raj.khem@...> wrote:
On Wed, Sep 2, 2020 at 5:18 PM SIMON BABY <simonkbaby@...> wrote:
>
> Hello,
>
> I have an issue with my throw , catch code in c++.  If i throw an error after the openssl library call, my application crashes.  If my application wishes to throw and catch exceptions across different shared libraries do we have any specific settings I can add in my bitbake recipe?
>

are you using -fexceptions to compile your application ?

> regards
> Simon
>


Re: Query on building applications and catch exceptions across different shared libraries

Khem Raj
 

On Wed, Sep 2, 2020 at 5:18 PM SIMON BABY <simonkbaby@gmail.com> wrote:

Hello,

I have an issue with my throw , catch code in c++. If i throw an error after the openssl library call, my application crashes. If my application wishes to throw and catch exceptions across different shared libraries do we have any specific settings I can add in my bitbake recipe?
are you using -fexceptions to compile your application ?

regards
Simon


Query on building applications and catch exceptions across different shared libraries

SIMON BABY
 

Hello,

I have an issue with my throw , catch code in c++.  If i throw an error after the openssl library call, my application crashes.  If my application wishes to throw and catch exceptions across different shared libraries do we have any specific settings I can add in my bitbake recipe?

regards
Simon


Re: How to integrate kernel-module in yocto-dunfell? #yocto #dunfell #apt #tx2 #kernel

Khem Raj
 

On Wed, Sep 2, 2020 at 4:32 AM Marek Belisko <marek.belisko@gmail.com> wrote:

On Wed, Sep 2, 2020 at 1:13 PM <kilian.brandt@tu-dresden.de> wrote:

Hey community,

I'm trying to use this library [can-isotp][1] on a Jetson TX2 Board. The version of the running OS is: 0.0.8 (dunfell).

From the docs of the library I get the following instructions:

```

DOWNLOAD and BUILD

1. Download repository and enter the repositories root directory

git clone https://github.com/hartkopp/can-isotp.git

cd can-isotp

2. Build ISO-TP kernel module

Ensure build dependencies are installed. E.g. for Debian (or Ubuntu):

sudo apt-get install build-essential linux-headers-$(uname -r)

To build:

(you need to be in the repositories root path)

make

To install (optional):

sudo make modules_install


3. When the PF_CAN core module is loaded ('modprobe can') the ISO-TP module
can be loaded into the kernel with

insmod ./net/can/can-isotp.ko

When the can-isotp.ko module has been installed into the Linux Kernels
modules directory (e.g. with 'make modules_install') the module should
load automatically when opening a CAN_ISOTP socket.

```

I have some questions about that procedure. Can anybody give me an hint on how to install this module? Do I have to create a completly new yocto image or is there any way to install kernel modules afterwards? I tried to copy the folder onto the TX2 and install it by hand, but (as to be expected) the make command is not found.
PLease take a look at :
https://www.yoctoproject.org/docs/2.6/kernel-dev/kernel-dev.html#working-with-out-of-tree-modules
where it is described how to compile out of tree modules.
in this case you might be lucky we already have recipe
http://cgit.openembedded.org/meta-openembedded/tree/meta-oe/recipes-extended/socketcan/can-isotp_git.bb?h=master
its blacklisted because it needs work to fix build on 5.2+ kernel

I would really appreciate any help ! Best regards,


[1]: https://github.com/hartkopp/can-isotp
marek


Re: How to integrate kernel-module in yocto-dunfell? #yocto #dunfell #apt #tx2 #kernel

Marek Belisko
 

On Wed, Sep 2, 2020 at 1:13 PM <kilian.brandt@tu-dresden.de> wrote:

Hey community,

I'm trying to use this library [can-isotp][1] on a Jetson TX2 Board. The version of the running OS is: 0.0.8 (dunfell).

From the docs of the library I get the following instructions:

```

DOWNLOAD and BUILD

1. Download repository and enter the repositories root directory

git clone https://github.com/hartkopp/can-isotp.git

cd can-isotp

2. Build ISO-TP kernel module

Ensure build dependencies are installed. E.g. for Debian (or Ubuntu):

sudo apt-get install build-essential linux-headers-$(uname -r)

To build:

(you need to be in the repositories root path)

make

To install (optional):

sudo make modules_install


3. When the PF_CAN core module is loaded ('modprobe can') the ISO-TP module
can be loaded into the kernel with

insmod ./net/can/can-isotp.ko

When the can-isotp.ko module has been installed into the Linux Kernels
modules directory (e.g. with 'make modules_install') the module should
load automatically when opening a CAN_ISOTP socket.

```

I have some questions about that procedure. Can anybody give me an hint on how to install this module? Do I have to create a completly new yocto image or is there any way to install kernel modules afterwards? I tried to copy the folder onto the TX2 and install it by hand, but (as to be expected) the make command is not found.
PLease take a look at :
https://www.yoctoproject.org/docs/2.6/kernel-dev/kernel-dev.html#working-with-out-of-tree-modules
where it is described how to compile out of tree modules.

I would really appreciate any help ! Best regards,


[1]: https://github.com/hartkopp/can-isotp
marek


How to integrate kernel-module in yocto-dunfell? #yocto #dunfell #apt #tx2 #kernel

kilian.brandt@...
 

Hey community, 

I'm trying to use this library [can-isotp][1] on a Jetson TX2 Board. The version of the running OS is: 0.0.8 (dunfell). 
 
From the docs of the library I get the following instructions:
 
```
DOWNLOAD and BUILD

1. Download repository and enter the repositories root directory

      git clone https://github.com/hartkopp/can-isotp.git

      cd can-isotp

2. Build ISO-TP kernel module

   Ensure build dependencies are installed. E.g. for Debian (or Ubuntu):

      sudo apt-get install build-essential linux-headers-$(uname -r)

   To build:

      (you need to be in the repositories root path)

      make

   To install (optional):

      sudo make modules_install


3. When the PF_CAN core module is loaded ('modprobe can') the ISO-TP module
   can be loaded into the kernel with

       insmod ./net/can/can-isotp.ko

   When the can-isotp.ko module has been installed into the Linux Kernels
   modules directory (e.g. with 'make modules_install') the module should
   load automatically when opening a CAN_ISOTP socket.
```

I have some questions about that procedure. Can anybody give me an hint on how to install this module? Do I have to create a completly new yocto image or is there any way to install kernel modules afterwards? I tried to copy the folder onto the TX2 and install it by hand, but (as to be expected) the make command is not found. 

I would really appreciate any help ! Best regards, 
 
 
  [1]: https://github.com/hartkopp/can-isotp


[PATCH yocto-autobuilder-helper] scripts/send-qa-email: Update to dedicated push capable domain

Michael Halstead
 

Signed-off-by: Michael Halstead <mhalstead@linuxfoundation.org>
---
scripts/send-qa-email | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/scripts/send-qa-email b/scripts/send-qa-email
index abc17e2..f38c876 100755
--- a/scripts/send-qa-email
+++ b/scripts/send-qa-email
@@ -70,10 +70,10 @@ if 'poky' in repos and os.path.exists(resulttool) and args.results_dir:
elif basebranch:
cloneopts = ["--branch", basebranch]
try:
- subprocess.check_call(["git", "clone", "git@git.yoctoproject.org:yocto-testresults", tempdir, "--depth", "5"] + cloneopts)
+ subprocess.check_call(["git", "clone", "git@push.yoctoproject.org:yocto-testresults", tempdir, "--depth", "5"] + cloneopts)
except subprocess.CalledProcessError:
print("No comparision branch found, falling back to master")
- subprocess.check_call(["git", "clone", "git@git.yoctoproject.org:yocto-testresults", tempdir, "--depth", "5"])
+ subprocess.check_call(["git", "clone", "git@push.yoctoproject.org:yocto-testresults", tempdir, "--depth", "5"])

# If the base comparision branch isn't present regression comparision won't work
# at least until we can tell the tool to ignore internal branch information
--
2.26.2


Yocto Project Status WW35'20

Stephen Jolley
 

Current Dev Position: YP 3.2 M3

Next Deadline: YP 3.2 M3 Feature Freeze - Now

 

Next Team Meetings:

 

Key Status/Updates:

  • M3 has now closed and we’re at feature freeze for 3.2.
  • There are a number of patches we need for 3.2 which are still being sorted out and M3 will build once that has happened.
  • Bitbake server startup has been changed to avoid the issues previously discovered. There are some issues with traceback handling/reporting during early init which are being resolved as a result of that and those have open bugs.
  • The server changes have improved memory resident bitbake but some issues with state tracking still remain so memory resident bitbake will not be the default until 3.3, assuming we can debug those remaining problems by early in 3.3.
  • There has been work in enabling PRServ to work well with hash equivalence, thanks to Mark for sorting out this long standing work item. We aim to have this in 3.2 but some tests need fixing before it can completely merge.
  • We will process one last round of recipe upgrades before we build M3.
  • We were finally able to change the fcommon gcc defaults back to standard, thanks to all who helped make that happen.
  • The number of autobuilder intermittent bugs has continued to rise unfortunately.

You can see the list of failures we’re continuing to see by searching for the “AB-INT” tag in bugzilla: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT

Help with any of these would be much appreciated, unfortunately it is proving hard to find anyone interested in helping figure these out and they significantly hamper our testing.

 

YP 3.2 Milestone Dates:

  • YP 3.2 M3 build date 2020/8/31
  • YP 3.2 M3 Release date 2020/9/11
  • YP 3.2 M4 build date 2020/10/5
  • YP 3.2 M4 Release date 2020/10/30

 

Planned upcoming dot releases:

  • YP 3.1.3 build date 2020/9/14
  • YP 3.1.3 release date 2020/9/25

 

Tracking Metrics:

 

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:

https://wiki.yoctoproject.org/wiki/TSC

 

The Status reports are now stored on the wiki at: https://wiki.yoctoproject.org/wiki/Weekly_Status

 

[If anyone has suggestions for other information you’d like to see on this weekly status update, let us know!]

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Re: Recipies version of incoming October Gatesgarth release.

 

On Tue, 1 Sep 2020 at 13:16, Yocto_user <avinashyadav94it@gmail.com> wrote:

Hi,
Is there any way to know all the recipes version detail that will come with Yocto 3.2 Gatesgarth
I don't think any of us have crystal balls to predict the exact
package versions we'll be using in October for the next release. We're
close to the feature freeze point but high priority recipe updates
could still be taken after that time.

Why do you think you need this information? If you explain your
concerns hopefully we can find a different way to provide the answers
you need.

--
Paul Barker
Konsulko Group


Recipies version of incoming October Gatesgarth release.

Yocto_user
 

Hi,
Is there any way to know all the recipes version detail that will come with Yocto 3.2 Gatesgarth ??


Re: Information about Yocto Dunfell components version #dunfell

 

On Tue, 1 Sep 2020 at 11:25, Josef Holzmayr-Khosh Amoz
<jester@theyoctojester.info> wrote:

Insert the package names into http://layers.openembedded.org/layerindex/branch/dunfell/recipes and see for yourself :)

Greetz

Am Di., 1. Sept. 2020 um 12:22 Uhr schrieb Yocto_user <avinashyadav94it@gmail.com>:

Hi All,

I read the Dunfell release notes but couldn't find the version detail of following components:
bzip2
cairo
faad2
fontconfig
freetype
gdkpixbuf
libav
libffi
libjpeg
libogg
libpng
libtiff
libvorbis
libxcursor
openexr
openssl
pango
pixman
stb-image
swscale
theora
x264
zlib

Please give me the version detail of these components, we are planning to use dunfell but before that we needed the version detail of all these components in Yocto.
Also worth noting: The exact versions used will depend on which commit
from the dunfell branch you choose. You should follow updates to the
stable branch to get the latest security fixes for your packages so
the versions should not be perfectly static anyway.

--
Paul Barker
Konsulko Group


Re: Private: Re: [yocto] Information about Yocto Dunfell components version #dunfell

Josef Holzmayr
 

Well if it's not there, then it's not there. If something is not provided by a recipe, then it obviously has no defined version. Please note though that package/recipe names are not directly comparable between distributions like Ubuntu and the Yocto project ecosystem, as the names might differ slightly. Example: libtiff seems to be just "tiff".


Am Di., 1. Sept. 2020 um 12:55 Uhr schrieb Yocto_user <avinashyadav94it@...>:

Thanks Josef Holzmayr-Khosh Amoz for the link, but still few components version is missing i.e.
gdkpixbuf
libjpeg
libtiff
openexr
stb-image
swscale
 all these are missing.


Re: Information about Yocto Dunfell components version #dunfell

Josef Holzmayr
 

Insert the package names into http://layers.openembedded.org/layerindex/branch/dunfell/recipes and see for yourself :)

Greetz

Am Di., 1. Sept. 2020 um 12:22 Uhr schrieb Yocto_user <avinashyadav94it@...>:

Hi All,

I read the Dunfell release notes but couldn't find the version detail of following components:
bzip2
cairo
faad2
fontconfig
freetype
gdkpixbuf
libav
libffi
libjpeg
libogg
libpng
libtiff
libvorbis
libxcursor
openexr
openssl
pango
pixman
stb-image
swscale
theora
x264
zlib

Please give me the version detail of these components,  we are planning to use dunfell but before that we needed the version detail of all these components in Yocto.


Information about Yocto Dunfell components version #dunfell

Yocto_user
 

Hi All,

I read the Dunfell release notes but couldn't find the version detail of following components:
bzip2
cairo
faad2
fontconfig
freetype
gdkpixbuf
libav
libffi
libjpeg
libogg
libpng
libtiff
libvorbis
libxcursor
openexr
openssl
pango
pixman
stb-image
swscale
theora
x264
zlib

Please give me the version detail of these components,  we are planning to use dunfell but before that we needed the version detail of all these components in Yocto.


[meta-gplv2] [PATCH] gnupg: Make it build with GCC 10 (which uses -fno-common by default)

Peter Kjellerstedt
 

Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
---
...th-GCC-10-which-uses-fno-common-by-d.patch | 93 +++++++++++++++++++
recipes-support/gnupg/gnupg_1.4.7.bb | 3 +-
2 files changed, 95 insertions(+), 1 deletion(-)
create mode 100644 recipes-support/gnupg/gnupg-1.4.7/0001-Make-it-build-with-GCC-10-which-uses-fno-common-by-d.patch

diff --git a/recipes-support/gnupg/gnupg-1.4.7/0001-Make-it-build-with-GCC-10-which-uses-fno-common-by-d.patch b/recipes-support/gnupg/gnupg-1.4.7/0001-Make-it-build-with-GCC-10-which-uses-fno-common-by-d.patch
new file mode 100644
index 0000000..2f84155
--- /dev/null
+++ b/recipes-support/gnupg/gnupg-1.4.7/0001-Make-it-build-with-GCC-10-which-uses-fno-common-by-d.patch
@@ -0,0 +1,93 @@
+From 1d0141d77d4f81cfa3213370fb7eeddbf53fc085 Mon Sep 17 00:00:00 2001
+From: Peter Kjellerstedt <pkj@axis.com>
+Date: Tue, 1 Sep 2020 00:29:22 +0200
+Subject: [PATCH] Make it build with GCC 10 (which uses -fno-common by default)
+
+Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
+---
+ g10/options.h | 3 +--
+ include/cipher.h | 2 +-
+ include/iobuf.h | 2 +-
+ include/memory.h | 2 +-
+ include/mpi.h | 2 +-
+ tools/mpicalc.c | 1 +
+ 6 files changed, 6 insertions(+), 6 deletions(-)
+
+diff --git a/g10/options.h b/g10/options.h
+index c5f0f22..33ed333 100644
+--- a/g10/options.h
++++ b/g10/options.h
+@@ -28,8 +28,7 @@
+ #include "packet.h"
+
+ #ifndef EXTERN_UNLESS_MAIN_MODULE
+-/* Norcraft can't cope with common symbols */
+-#if defined (__riscos__) && !defined (INCLUDED_BY_MAIN_MODULE)
++#if !defined (INCLUDED_BY_MAIN_MODULE)
+ #define EXTERN_UNLESS_MAIN_MODULE extern
+ #else
+ #define EXTERN_UNLESS_MAIN_MODULE
+diff --git a/include/cipher.h b/include/cipher.h
+index 168ab41..794c12b 100644
+--- a/include/cipher.h
++++ b/include/cipher.h
+@@ -109,7 +109,7 @@ struct gcry_md_context {
+ typedef struct gcry_md_context *MD_HANDLE;
+
+ #ifndef EXTERN_UNLESS_MAIN_MODULE
+-#if defined (__riscos__) && !defined (INCLUDED_BY_MAIN_MODULE)
++#if !defined (INCLUDED_BY_MAIN_MODULE)
+ #define EXTERN_UNLESS_MAIN_MODULE extern
+ #else
+ #define EXTERN_UNLESS_MAIN_MODULE
+diff --git a/include/iobuf.h b/include/iobuf.h
+index a1d58c9..25f682b 100644
+--- a/include/iobuf.h
++++ b/include/iobuf.h
+@@ -73,7 +73,7 @@ struct iobuf_struct {
+ };
+
+ #ifndef EXTERN_UNLESS_MAIN_MODULE
+-#if defined (__riscos__) && !defined (INCLUDED_BY_MAIN_MODULE)
++#if !defined (INCLUDED_BY_MAIN_MODULE)
+ #define EXTERN_UNLESS_MAIN_MODULE extern
+ #else
+ #define EXTERN_UNLESS_MAIN_MODULE
+diff --git a/include/memory.h b/include/memory.h
+index 895d8a7..217d316 100644
+--- a/include/memory.h
++++ b/include/memory.h
+@@ -87,7 +87,7 @@ unsigned secmem_get_flags(void);
+ #define DBG_MEMSTAT memory_stat_debug_mode
+
+ #ifndef EXTERN_UNLESS_MAIN_MODULE
+-#if defined (__riscos__) && !defined (INCLUDED_BY_MAIN_MODULE)
++#if !defined (INCLUDED_BY_MAIN_MODULE)
+ #define EXTERN_UNLESS_MAIN_MODULE extern
+ #else
+ #define EXTERN_UNLESS_MAIN_MODULE
+diff --git a/include/mpi.h b/include/mpi.h
+index 81061d3..d529bda 100644
+--- a/include/mpi.h
++++ b/include/mpi.h
+@@ -38,7 +38,7 @@
+ #include "memory.h"
+
+ #ifndef EXTERN_UNLESS_MAIN_MODULE
+-#if defined (__riscos__) && !defined (INCLUDED_BY_MAIN_MODULE)
++#if !defined (INCLUDED_BY_MAIN_MODULE)
+ #define EXTERN_UNLESS_MAIN_MODULE extern
+ #else
+ #define EXTERN_UNLESS_MAIN_MODULE
+diff --git a/tools/mpicalc.c b/tools/mpicalc.c
+index 1df27d9..647dfbd 100644
+--- a/tools/mpicalc.c
++++ b/tools/mpicalc.c
+@@ -30,6 +30,7 @@
+ #include <stdlib.h>
+ #include <ctype.h>
+
++#define INCLUDED_BY_MAIN_MODULE 1
+ #include "util.h"
+ #include "mpi.h"
+ #include "i18n.h"
diff --git a/recipes-support/gnupg/gnupg_1.4.7.bb b/recipes-support/gnupg/gnupg_1.4.7.bb
index 6a950fd..6258809 100644
--- a/recipes-support/gnupg/gnupg_1.4.7.bb
+++ b/recipes-support/gnupg/gnupg_1.4.7.bb
@@ -20,7 +20,8 @@ SRC_URI = "${GNUPG_MIRROR}/gnupg/gnupg-${PV}.tar.bz2 \
file://CVE-2013-4242.patch \
file://fix-ustar-check-issue.patch \
file://0001-Make-it-build-with-gettext-0.20.patch \
- "
+ file://0001-Make-it-build-with-GCC-10-which-uses-fno-common-by-d.patch \
+ "

SRC_URI[md5sum] = "b06a141cca5cd1a55bbdd25ab833303c"
SRC_URI[sha256sum] = "69d18b7d193f62ca27ed4febcb4c9044aa0c95305d3258fe902e2fae5fc6468d"


M+ & H bugs with Milestone Movements WW35

Stephen Jolley
 

All,

 

YP M+ or high bugs which moved to a new milestone in WW35 are listed below:

Priority

Bug ID

Short Description

Changer

Owner

Was

Became

High

13802

ltp tests fail with ssh connection lost  error intermittently

randy.macleod@...

sakib.sajal@...

3.2 M3

3.2 M4

Medium+

10096

Allow PREFERRED_VERSION miss to be fatal

randy.macleod@...

unassigned@...

3.2 M3

3.3 M1

 

13004

Automate yocto-check-layer -m option

randy.macleod@...

unassigned@...

3.2 M3

3.2 M4

 

13233

fetch2: try_premirror(): improve on updating repo from mirror

randy.macleod@...

unassigned@...

3.2 M3

3.3 M1

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Enhancements/Bugs closed WW35!

Stephen Jolley
 

All,

 

The below were the owners of enhancements or bugs closed during the last week!

Who

Count

bruce.ashfield@...

4

richard.purdie@...

3

randy.macleod@...

2

joe.slater@...

1

Grand Total

10

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Current high bug count owners for Yocto Project 3.2

Stephen Jolley
 

All,

 

Below is the list as of top 47 bug owners as of the end of WW35 of who have open medium or higher bugs and enhancements against YP 3.2.   There are 42 possible work days left until the final release candidates for YP 3.2 needs to be released.

Who

Count

richard.purdie@...

30

david.reyna@...

22

akuster808@...

17

bluelightning@...

17

bruce.ashfield@...

16

ross@...

11

JPEWhacker@...

10

mark.morton@...

10

timothy.t.orling@...

9

Qi.Chen@...

9

kai.kang@...

9

randy.macleod@...

8

trevor.gamblin@...

7

sakib.sajal@...

6

hongxu.jia@...

5

raj.khem@...

5

rpjday@...

4

mingli.yu@...

4

ydirson@...

3

yi.zhao@...

3

mostthingsweb@...

3

jon.mason@...

3

alejandro@...

2

jpuhlman@...

2

matthewzmd@...

2

akuster@...

2

mark.hatle@...

2

michael@...

2

jeanmarie.lemetayer@...

2

kergoth@...

2

chee.yang.lee@...

2

jaewon@...

2

joe.slater@...

1

matt.ranostay@...

1

steve@...

1

changqing.li@...

1

liu.ming50@...

1

liezhi.yang@...

1

anuj.mittal@...

1

ankur.tyagi85@...

1

jason.wessel@...

1

dl9pf@...

1

khairul.rohaizzat.jamaluddin@...

1

kai.ruhnau@...

1

aehs29@...

1

maxime.roussinbelanger@...

1

amber.n.elliot@...

1

Grand Total

246

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Yocto Project Newcomer & Unassigned Bugs - Help Needed

Stephen Jolley
 

All,

 

The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on the triage page under the appropriate heading:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs  Also please review: https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded

The idea is these bugs should be straight forward for a person to help work on who doesn't have deep experience with the project.  If anyone can help, please take ownership of the bug and send patches!  If anyone needs help/advice there are people on irc who can likely do so, or some of the more experienced contributors will likely be happy to help too.

 

Also, the triage team meets weekly and does its best to handle the bugs reported into the Bugzilla. The number of people attending that meeting has fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the triage team) are therefore going to start reporting out the currently 339 unassigned or newcomer bugs.

 

We're hoping people may be able to spare some time now and again to help out with these.  Bugs are split into two types, "true bugs" where things don't work as they should and "enhancements" which are features we'd want to add to the system.  There are also roughly four different "priority" classes right now, “3.2”, “3.3, "3.99" and "Future", the more pressing/urgent issues being in "3.2" and then “3.3”.

 

Please review this link and if a bug is something you would be able to help with either take ownership of the bug, or send me (sjolley.yp.pm@...) an e-mail with the bug number you would like and I will assign it to you (please make sure you have a Bugzilla account).  The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage_Archive#Unassigned_or_Newcomer_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Re: Backport some packages

Mikko Rapeli
 

Hi,

On Mon, Aug 31, 2020 at 11:32:56AM +0200, Alexander Kanavin wrote:
The best is to ask your BSP supplier to provide a new version of the BSP
that is compatible with recent Yocto versions.

Backporting userspace stuff is difficult or impossible.
For those who aren't afraid to digging deeper, it is possible to limit
the impact of BSP layers by e.g. restricting which recipes and bbappends
get applied in your product via BBMASK in distro config for example.
This enables much, much faster updates cycles since fixing one or two BSP recipes
for new yocto version is easier than waiting and possibly paying for a full
update with all bells and whistles.

In many cases users don't need all patches and changes provided in BSP SW layers.
In some cases they are even undesirable.

But yes, talking to BSP supplier(s) is a good start.

Cheers,

-Mikko

Alex

On Mon, 31 Aug 2020 at 10:52, <majid.nasiry65@gmail.com> wrote:

Hi
How can I backport some package (e.g php, cmake). My BSP only work in Krogoth
version and I want to use some new package (e.g from Sumo version).
I'm new in this stuffs. I don't know mybe the best way is I rewrite BSPs
and update whole project, anyway I don't know how can I do this too!

Please help

3041 - 3060 of 53454