[yocto] [meta-security][PATCH 1/3] upload-error-report: add script to upload errors

[akuster]

Signed-off-by: Armin Kuster 
---
 scripts/upload-error-report | 26 ++
 1 file changed, 26 insertions(+)
 create mode 100755 scripts/upload-error-report

diff --git a/scripts/upload-error-report b/scripts/upload-error-report
new file mode 100755
index 000..56bd24e
--- /dev/null
+++ b/scripts/upload-error-report
@@ -0,0 +1,26 @@
+#!/bin/bash
+
+ERR_REPORT_USERNAME=$1
+ERR_REPORT_EMAIL=$2
+BUILDDIR=$3
+
+shift
+shift
+shift
+
+if [ ! -e $BUILDDIR ]; then
+exit 0
+fi
+
+cd $BUILDDIR/../poky
+
+if [ -d $BUILDDIR/tmp/log/error-report/ ]; then
+echo "$ERR_REPORT_USERNAME" > ~/.oe-send-error
+echo "$ERR_REPORT_EMAIL" >> ~/.oe-send-error
+
+. ./oe-init-build-env $BUILDDIR
+
+for x in `ls $BUILDDIR/tmp/log/error-report/ | grep error_report_`; do
+send-error-report -y tmp/log/error-report/$x
+done
+fi
-- 
2.17.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#50405): https://lists.yoctoproject.org/g/yocto/message/50405
Mute This Topic: https://lists.yoctoproject.org/mt/76488548/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] [meta-security][PATCH 3/3] .gitlab: send error reports

[akuster]

Signed-off-by: Armin Kuster 
---
 .gitlab-ci.yml | 11 ++-
 1 file changed, 6 insertions(+), 5 deletions(-)

diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 132eb78..37db49c 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -5,17 +5,18 @@ stages:
   stage: build
   image: crops/poky
   before_script:
+- echo "$ERR_REPORT_USERNAME" > ~/.oe-send-error
+- echo "$ERR_REPORT_EMAIL" >> ~/.oe-send-error
 - export PATH=~/.local/bin:$PATH
 - wget https://bootstrap.pypa.io/get-pip.py
 - python3 get-pip.py
 - python3 -m pip install kas
-- wget -q 'https://downloads.rclone.org/rclone-current-linux-amd64.zip'
-- unzip -q rclone-current-linux-amd64.zip
-- mv rclone-*-linux-amd64/rclone ~/.local/bin/
-- rm -rf rclone-*-linux-amd64*
   after_script:
+- for x in `ls $CI_PROJECT_DIR/build/tmp/log/error-report/ | grep 
error_report_`; do
+- send-error-report -y tmp/log/error-report/$x
+- done
 - rm -rf build
-- ./scripts/ci-cleanup.sh
+- $CI_PROJECT_DIR/scripts/ci-cleanup.sh
   cache:
 paths:
   - layers
-- 
2.17.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#50407): https://lists.yoctoproject.org/g/yocto/message/50407
Mute This Topic: https://lists.yoctoproject.org/mt/76488550/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] [meta-security][PATCH 2/3] kas/kas-security-base.yml: lets enable error reporting

[akuster]

Signed-off-by: Armin Kuster 
---
 kas/kas-security-base.yml | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/kas/kas-security-base.yml b/kas/kas-security-base.yml
index 768390e..2cf056f 100644
--- a/kas/kas-security-base.yml
+++ b/kas/kas-security-base.yml
@@ -37,6 +37,8 @@ local_conf_header:
 DL_DIR = "/home/srv/downloads/master"
 BB_HASHSERVE = "auto"
 BB_SIGNATURE_HANDLER = "OEEquivHash"
+INHERIT += "buildstats buildstats-summary buildhistory"
+INHERIT += "report-error"
 
   diskmon: |
 BB_DISKMON_DIRS = "\
-- 
2.17.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#50406): https://lists.yoctoproject.org/g/yocto/message/50406
Mute This Topic: https://lists.yoctoproject.org/mt/76488549/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] npmsw fetching error: package from npm-shrinkwrap is not downloaded so "Could not install from.../SONStream" as it does not contain a package.json file.

[Sandra Tobajas]

Hi Jose, 

I have tested your npm-shrinkwrap.json file with this patch 
(https://patchwork.openembedded.org/patch/175755/) and it worked.
Can you test it on your machine ?

Regards,
Sandra

Sandra Tobajas
Consultant en logiciel libre | Montréal, Qc
Savoir-Faire Linux
Bureau: (+1) 514-276-5468 # 329

- Original Message -
From: "joseantonio cardenas" 
To: "Sandra Tobajas" 
Cc: "yocto" 
Sent: Friday, August 28, 2020 9:44:59 AM
Subject: RE: [yocto] npmsw fetching error: package from npm-shrinkwrap is not 
downloaded so "Could not install from.../SONStream" as it does not contain a 
package.json file.

Hi Sandra, thank you by your info. It was very useful to fetch development 
modules from shrinkwrap file. 

I attach you the shrinkwrap file with no dependencies that I were trying to 
fetch. 

Regards.

Jose.

-Original Message-
From: Sandra Tobajas  
Sent: jueves, 27 de agosto de 2020 15:16
To: Cardenas Jose Antonio (JCARDENA) 
Cc: yo...@yoctoproject.org
Subject: Re: [yocto] npmsw fetching error: package from npm-shrinkwrap is not 
downloaded so "Could not install from.../SONStream" as it does not contain a 
package.json file.

CAUTION: This email originated from outside the organization. Do not click on 
links or open attachments unless you recognize the sender and know the content 
is safe.

Hi Jose,

It seems that all your dependencies are development dependencies tagged with 
"dev":true in the npm-shrinkwrap.json file.

If all dependencies are for development purpose and if you want to install the 
package as a development package, you can add:

npmsw://${THISDIR}/${PN}/npm-shrinkwrap.json;dev=true

It seems that "npmsw.py" fetching code fails if you are trying to install a npm 
package with a npm-shrinkwrap.json file with no dependencies (as reported by 
Jean-Marie and Randy).
I am currently preparing a patch to solve the problem reported here: 
https://bugzilla.yoctoproject.org/show_bug.cgi?id=13901.

If not, maybe you could send the full npm-shrinkwrap.json file to reproduce 
exactly the problem.

Regards,

Sandra

Sandra Tobajas
Consultant en logiciel libre | Montréal, Qc Savoir-Faire Linux
Bureau: (+1) 514-276-5468 # 329
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#50404): https://lists.yoctoproject.org/g/yocto/message/50404
Mute This Topic: https://lists.yoctoproject.org/mt/76335911/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] dist folder missing in npm build.

[Cardenas Jose Antonio (JCARDENA)]

Hi Jean-Marie, thank you for the info.

Do you know how we could do this extra build step? We are not sure about how to 
do it.

Regards.
Jose

Obtener Outlook para Android


From: Jean-Marie Lemetayer 
Sent: Friday, August 28, 2020 2:22:32 PM
To: Cardenas Jose Antonio (JCARDENA) 
Cc: yocto@lists.yoctoproject.org 
Subject: Re: [yocto] dist folder missing in npm build.

CAUTION: This email originated from outside the organization. Do not click on 
links or open attachments unless you recognize the sender and know the content 
is safe.

Hi Jose,

Seeing your other email in the list, it seems that you are trying to
build an angular or react application.

Right now the build of these applications is not handled by Yocto yet.

For an angular application you will need to pack the ng native tool
and call it to generate the dist directory.

For a react application you have to run the npm build script but the
output files will be in a build directory.

Best regards,
Jean-Marie

On Fri, Aug 28, 2020 at 11:54 AM Cardenas Jose Antonio (JCARDENA)
 wrote:
>
> Hi all,
>
>
>
> i’m trying to reproduce an older recipe that was built with npm. It seems 
> that the older recipe copied server files from a “dist” folder that now is 
> missing.
>
>
>
> I show the install part of the recipe:
>
> do_install() {
>
> install -d ${D}/usr/httpd/zigbee-ui
>
> cp -r ${S}/dist/* ${D}/usr/httpd/zigbee-ui
>
> }
>
>
>
> Someone knows what happened with this folder?
>
>
>
> Regards
>
>
>
> 
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#50403): https://lists.yoctoproject.org/g/yocto/message/50403
Mute This Topic: https://lists.yoctoproject.org/mt/76470414/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[linux-yocto] v5.2.x - stable updates comprising v5.2.58

[Paul Gortmaker]

Bruce, Yocto kernel folks:

Here is the next 5.2.x stable update "extension" primarily created for
the Yocto project, as the next v5.2.x post-EOL release.

This maintenance is going to wind down in less than two weeks, so folks
really should have their own maintenance or migration path off of this
v5.2.x update stream in place and tested by now, if they haven't done so
already.  Those couple of weeks translate into just a handful more
v5.2.x releases remaining.

The 5.2.58 content here is from an audit of what went into the v5.4.58
release plus any additional commits listed as "Fixes:" of the chosen
commits (and past backported commits).

The same is true for v5.2.57 - but since 5.4.57 was such a small
release, and 1/2 of its content was for the recent net-random fix we
already added in a previous v5.2.x release, I didn't send out a separate
e-mail for it.

There are about 55 commits here, as I continue to maintain a 1:1
mapping between the 5.2.x releases here and the 5.4.x releases that
serve as a content reference.  Hence v5.2.59 will mirror what is found
in the v5.4.59-stable release and so on.

I've put this release through my normal testing, with build tests
on x86-64/32, ARM-64/32, PPC and MIPS, plus some static analysis and
finally some sanity runtime tests on x86-64 (raw + qemu/KVM).

Please find tag v5.2.58 (1927e44fb3051f3cc379d8ea42cc0dbde3926933) as
the current head of linux-5.2.y branch in the repo in the kernel.org
directory here:

  
https://git.kernel.org/pub/scm/linux/kernel/git/paulg/linux-5.2.y.git/?h=linux-5.2.y
  git://git.kernel.org/pub/scm/linux/kernel/git/paulg/linux-5.2.y.git

for merge to standard/base in linux-yocto-5.2 and then out from there
into the other base and BSP branches.

For those who are interested, the evolution of the commits is here:

  https://git.kernel.org/cgit/linux/kernel/git/paulg/longterm-queue-5.2.git/

This repo isn't needed for anything; it just exists for transparency and
so people can see the evolution of the raw commits that were originally
selected to create this 5.2.x release.

Paul.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#9003): 
https://lists.yoctoproject.org/g/linux-yocto/message/9003
Mute This Topic: https://lists.yoctoproject.org/mt/76472386/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] dist folder missing in npm build.

[Jean-Marie Lemetayer]

Hi Jose,

Seeing your other email in the list, it seems that you are trying to
build an angular or react application.

Right now the build of these applications is not handled by Yocto yet.

For an angular application you will need to pack the ng native tool
and call it to generate the dist directory.

For a react application you have to run the npm build script but the
output files will be in a build directory.

Best regards,
Jean-Marie

On Fri, Aug 28, 2020 at 11:54 AM Cardenas Jose Antonio (JCARDENA)
 wrote:
>
> Hi all,
>
>
>
> i’m trying to reproduce an older recipe that was built with npm. It seems 
> that the older recipe copied server files from a “dist” folder that now is 
> missing.
>
>
>
> I show the install part of the recipe:
>
> do_install() {
>
> install -d ${D}/usr/httpd/zigbee-ui
>
> cp -r ${S}/dist/* ${D}/usr/httpd/zigbee-ui
>
> }
>
>
>
> Someone knows what happened with this folder?
>
>
>
> Regards
>
>
>
> 
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#50402): https://lists.yoctoproject.org/g/yocto/message/50402
Mute This Topic: https://lists.yoctoproject.org/mt/76470414/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Removing Python2 Completely

[Aashik Aswin]

Thanks,

Now I am able to see only python-core remaining in the RootFS Manifest and
Image size has decreased by nearly 10 MB.

Thanks,
Aashik

On Fri, Aug 28, 2020 at 12:44 PM Maciej Pijanowski <
maciej.pijanow...@3mdeb.com> wrote:

>
> On 28.08.2020 09:10, Aashik Aswin wrote:
>
> Hi,
>
> I am currently using Yocto Zeus. So is it safe to say that if we remove
> all the Python2 calls from image, that itself will remove Python2 overall ?
>
>
> If you want to remove python2 from the image, you need to make sure that
> no other package installed
> to the image RDEPENDS (runtime dependency) on it. I would start with
> checking what still pulls the
> python2 to your image.
>
>
> https://www.yoctoproject.org/docs/1.8/ref-manual/ref-manual.html#usingpoky-debugging-dependencies
>
> Also, please reply to the list, not directly to just me.
>
>
> Thanks,
> Aashik
>
> On Fri 28 Aug, 2020, 12:37 PM Maciej Pijanowski, <
> maciej.pijanow...@3mdeb.com> wrote:
>
>>
>> On 28.08.2020 09:04, Aashik Aswin wrote:
>>
>> Hi,
>>
>> I am trying to remove Python2 and it's supporting modules completely from
>> my Image, as I have moved all my code to Python3 and hence no longer
>> require Python2. I tried the IMAGE_INSTALL_remove variable but seems to
>> have no effect. Is there a way I can remove Python2 without much changes to
>> the layers and through configuration variables only ?
>>
>> You can see what is pulling the python2 to the image (using the bitbake
>> -g for example).
>>
>> Which Yocto release are you using? I believe the latest one (Dunfell) is
>> already python3 only.
>>
>>
>>
>> Please point me to the correct mailer if  I am wrong.
>>
>> Thanks,
>> Aashik
>>
>> --
>> Maciej Pijanowski
>> Embedded Systems Engineer
>> GPG: 9963C36AAC3B2B46https://3mdeb.com | @3mdeb_com
>>
>> 
>>
> --
> Maciej Pijanowski
> Embedded Systems Engineer
> GPG: 9963C36AAC3B2B46https://3mdeb.com | @3mdeb_com
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#50401): https://lists.yoctoproject.org/g/yocto/message/50401
Mute This Topic: https://lists.yoctoproject.org/mt/76468916/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] dist folder missing in npm build.

[Cardenas Jose Antonio (JCARDENA)]

Hi all,

i'm trying to reproduce an older recipe that was built with npm. It seems that 
the older recipe copied server files from a "dist" folder that now is missing.

I show the install part of the recipe:

do_install() {
install -d ${D}/usr/httpd/zigbee-ui
cp -r ${S}/dist/* ${D}/usr/httpd/zigbee-ui
}

Someone knows what happened with this folder?

Regards

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#50400): https://lists.yoctoproject.org/g/yocto/message/50400
Mute This Topic: https://lists.yoctoproject.org/mt/76470414/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] devtool add ignores "devDependencies" from package.json when generates npm-shrinkwrap.json file

[Cardenas Jose Antonio (JCARDENA)]

Yes, it worked! Thank you very much!

From: Jean-Marie Lemetayer 
Sent: jueves, 27 de agosto de 2020 14:41
To: Cardenas Jose Antonio (JCARDENA) 
Cc: yocto@lists.yoctoproject.org
Subject: Re: [yocto] devtool add  ignores "devDependencies" from 
package.json when generates npm-shrinkwrap.json file


CAUTION: This email originated from outside the organization. Do not click on 
links or open attachments unless you recognize the sender and know the content 
is safe.
Hi Jose,

You have to use devtool with the --npm-dev option.

Best regards,
Jean-Marie

On Thu, Aug 27, 2020 at 12:47 PM Cardenas Jose Antonio (JCARDENA) 
mailto:joseantonio.carde...@niko.eu>> wrote:
Hi all,

Trying to create a recipe from scratch with “devtool add” tool, a 
npm-shrinkwrap.json file is created from reading of package.json from the 
module that is going to be installed.

The building goes fine but I can’t run the application in the target because 
nodejs misses the modules placed in “devDependencies” from package.json.
I have tried to include NPM_INSTALL_DEV = "1" in the recipe but I get an error 
because the modules that appears in “devDependencies” from package.json are not 
included in npm-shrinkwrap.json.

There is any way to regenerate npm-shrinkwrap.json with devtool taking in 
account devdependencies or a way to create npm-shrinkwrap.json with “devtool 
add” in a way that takes in account devDependencies?

Regards
Jose

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#50398): https://lists.yoctoproject.org/g/yocto/message/50398
Mute This Topic: https://lists.yoctoproject.org/mt/76448481/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] How to generate opensource licenses credits web page

[Damien LEFEVRE]

Hi,

I have a distro which is not using any package manager in the image. Images
are deployed atomically.

I'd like to make a script to generate the credits / acknowledgement web
page for all the open source components to ease the task and make sure I
don't forget anyone.

In the actual image I have the list of the licenses in /usr/share/licenses/
which is good, but I'm missing the SUMMARY, DESCRIPTION, and HOMEPAGE
fields we declare in the recipes which would be nice to display

Is there any built-in way to bring that information in the image?

I noticed that in the image's build directory there is
/image-name/1.0-r0/oe-rootfs-repo/aarch64/Packages which if I understand
correctly has the ipk package list with the missing information.

Is there a way to copy that file in the image after do_rootfs completes?

Thanks,
-Damien
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#50397): https://lists.yoctoproject.org/g/yocto/message/50397
Mute This Topic: https://lists.yoctoproject.org/mt/76469697/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[linux-yocto][linux-yocto-dev standard/cn96xx] marvell-cn96xx for linux-yocto-dev v5.8

[Ruiqiang Hao]

Hi Bruce,

Would you please help to merge follow kernel code into our linux-yocto-dev 
kernel?

The branch is
standard/cn96xx

Thanks,
Ruiqiang

The following changes since commit 9c5bf62190150de3ad55df4f5b3f44acc9628acf:

  octeontx2-pf: Avoid null pointer dereference (2020-08-18 13:13:24 +0800)

are available in the Git repository at:

  https://github.com/cythe/linux.git marvell-cn96xx_v5.8

for you to fetch changes up to bb186d234065264326b3e750b1b434c6dbe05d3d:

  pci: octeontx2: Adjust match table data due to kernel change (2020-08-28 
15:34:23 +0800)


Ruiqiang Hao (1):
  pci: octeontx2: Adjust match table data due to kernel change

 drivers/pci/controller/pci-octeontx2-pem.c | 5 -
 1 file changed, 4 insertions(+), 1 deletion(-)

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#9002): 
https://lists.yoctoproject.org/g/linux-yocto/message/9002
Mute This Topic: https://lists.yoctoproject.org/mt/76469398/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Removing Python2 Completely

[Maciej Pijanowski]

On 28.08.2020 09:10, Aashik Aswin wrote:

Hi,
I am currently using Yocto Zeus. So is it safe to say that if we 
remove all the Python2 calls from image, that itself will remove 
Python2 overall ?


If you want to remove python2 from the image, you need to make sure that 
no other package installed
to the image RDEPENDS (runtime dependency) on it. I would start with 
checking what still pulls the

python2 to your image.

https://www.yoctoproject.org/docs/1.8/ref-manual/ref-manual.html#usingpoky-debugging-dependencies

Also, please reply to the list, not directly to just me.



Thanks,
Aashik

On Fri 28 Aug, 2020, 12:37 PM Maciej Pijanowski, 
mailto:maciej.pijanow...@3mdeb.com>> wrote:



On 28.08.2020 09:04, Aashik Aswin wrote:

Hi,

I am trying to remove Python2 and it's supporting modules
completely from my Image, as I have moved all my code to Python3
and hence no longer require Python2. I tried the
IMAGE_INSTALL_remove variable but seems to have no effect. Is
there a way I can remove Python2 without much changes to the
layers and through configuration variables only ?


You can see what is pulling the python2 to the image (using the
bitbake -g for example).

Which Yocto release are you using? I believe the latest one
(Dunfell) is already python3 only.




Please point me to the correct mailer if  I am wrong.

Thanks,
Aashik

-- 
Maciej Pijanowski

Embedded Systems Engineer
GPG: 9963C36AAC3B2B46
https://3mdeb.com  | @3mdeb_com




--
Maciej Pijanowski
Embedded Systems Engineer
GPG: 9963C36AAC3B2B46
https://3mdeb.com | @3mdeb_com

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#50396): https://lists.yoctoproject.org/g/yocto/message/50396
Mute This Topic: https://lists.yoctoproject.org/mt/76468916/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Removing Python2 Completely

[Maciej Pijanowski]

On 28.08.2020 09:04, Aashik Aswin wrote:

Hi,

I am trying to remove Python2 and it's supporting modules completely 
from my Image, as I have moved all my code to Python3 and hence no 
longer require Python2. I tried the IMAGE_INSTALL_remove variable but 
seems to have no effect. Is there a way I can remove Python2 without 
much changes to the layers and through configuration variables only ?


You can see what is pulling the python2 to the image (using the bitbake 
-g for example).


Which Yocto release are you using? I believe the latest one (Dunfell) is 
already python3 only.





Please point me to the correct mailer if  I am wrong.

Thanks,
Aashik




--
Maciej Pijanowski
Embedded Systems Engineer
GPG: 9963C36AAC3B2B46
https://3mdeb.com | @3mdeb_com

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#50395): https://lists.yoctoproject.org/g/yocto/message/50395
Mute This Topic: https://lists.yoctoproject.org/mt/76468916/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Removing Python2 Completely

[Aashik Aswin]

Hi,

I am trying to remove Python2 and it's supporting modules completely from
my Image, as I have moved all my code to Python3 and hence no longer
require Python2. I tried the IMAGE_INSTALL_remove variable but seems to
have no effect. Is there a way I can remove Python2 without much changes to
the layers and through configuration variables only ?

Please point me to the correct mailer if  I am wrong.

Thanks,
Aashik
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#50394): https://lists.yoctoproject.org/g/yocto/message/50394
Mute This Topic: https://lists.yoctoproject.org/mt/76468916/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-