yocto@lists.yoctoproject.org

Re: chpasswd not working in yocto-2019

Raghu Icecraft Software Trainings

#51839

Paul,

Thanks for the reply.

I am using Xilinx-SDK based : Linux version 4.19.0-rt1-xilinx-v2019.1

Can you please let me know how to verify the yocto version running on target.

Thanks,

Raghu

Show quoted text

On Mon, Dec 28, 2020 at 5:31 PM Paul Barker <pbarker@...> wrote:

On Mon, 28 Dec 2020 at 09:44, Raghu Icecraft Software Trainings
<raghu.icecraft@...> wrote:
>
> Hello,
> I have upgraded my kernel poky to 2019.1 version, here i am unable to find chpasswd utility because of which i am unable to set password to my root-user.
> Can you please let me know if the chpasswd utility has been changed or modified please.

Yocto Project doesn't have a version "2019.1", see
https://wiki.yoctoproject.org/wiki/Releases.

I guess you're using a vendor supplied BSP or SDK with that version
number. Could you provide the Yocto Project version number and the
layers in use, or at least give some more info on where your "2019.1"
release is from.

Thanks,

--
Paul Barker
Konsulko Group

Re: chpasswd not working in yocto-2019

Paul Barker

#51838

On Mon, 28 Dec 2020 at 09:44, Raghu Icecraft Software Trainings
<raghu.icecraft@...> wrote:

Hello,
I have upgraded my kernel poky to 2019.1 version, here i am unable to find chpasswd utility because of which i am unable to set password to my root-user.
Can you please let me know if the chpasswd utility has been changed or modified please.Yocto Project doesn't have a version "2019.1", see
https://wiki.yoctoproject.org/wiki/Releases.

I guess you're using a vendor supplied BSP or SDK with that version
number. Could you provide the Yocto Project version number and the
layers in use, or at least give some more info on where your "2019.1"
release is from.

Thanks,

-- 
Paul Barker
Konsulko Group

chpasswd not working in yocto-2019

Raghu Icecraft Software Trainings

#51837

Hello,

I have upgraded my kernel poky to 2019.1 version, here i am unable to find chpasswd utility because of which i am unable to set password to my root-user.

Can you please let me know if the chpasswd utility has been changed or modified please.

Re: Error during do_install for linux-libc-headers_5.8 recipe during 'bitbake core-image-minimal'

Matthias Rampke

#51836

Bisect points at the commit that introduced the hard pseudo abort:

84e0642ed6aba422583871fc153bbd94380074de is the first bad commit
commit 84e0642ed6aba422583871fc153bbd94380074de
Author: Richard Purdie <richard.purdie@...>
Date: Tue Sep 29 17:57:38 2020 +0100

pseudo: Abort on mismatch patch

Rather than doing what turns out to be a rather dangerous "fixup" if
we see a file with a different path but the same inode as another file
we've previously seen, throw and abort. Direct the user to a wiki page
where we can maintain information about what this error means.

(From OE-Core rev: 2db491d97da08d44ebd257f98489550a82a7935c)

Signed-off-by: Richard Purdie <richard.purdie@...>

:040000 040000 265627b814038c0cc19248bbb885ab7536202e1c acfc4fbeb04a887f2ceeaa029a63a4dd82f7767d M meta
bisect run success

/MR

On Sun, Dec 27, 2020 at 8:43 PM matthias.rampke via lists.yoctoproject.org <matthias.rampke=googlemail.com@...> wrote:

One more thing: I tried reverting the linux-libc-headers version change (57d5f4ad410d4e9d55bdd9734bf5ab8fa6667a53) and that fails in the same way, so it's not that.

I also realized that the yocto-3.2 tag does not include the 3.2.1 updates; however the same issue happens on 3.2.1 as well.

I will try to bisect this but it seems like it will take a long time since I need to wipe the tmp directory at every step.

/MR

Re: Error during do_install for linux-libc-headers_5.8 recipe during 'bitbake core-image-minimal'

Matthias Rampke

#51835

One more thing: I tried reverting the linux-libc-headers version change (57d5f4ad410d4e9d55bdd9734bf5ab8fa6667a53) and that fails in the same way, so it's not that.

I also realized that the yocto-3.2 tag does not include the 3.2.1 updates; however the same issue happens on 3.2.1 as well.

I will try to bisect this but it seems like it will take a long time since I need to wipe the tmp directory at every step.

/MR

Re: Error during do_install for linux-libc-headers_5.8 recipe during 'bitbake core-image-minimal'

Matthias Rampke

#51834

Hi,

I hit the same issue, also while trying things out on WSL2 (not committed enough to build a dedicated workstation/VM). I found a few more things:

This seems to be a pseudo abort with:

path mismatch [2 links]: ino 409763 db '/run/shm/sem.mp-bzdlrxrj' req '/run/shm/tGpqeT'.

I tried to follow the instructions to collect as many logs as possible. Logs are attached as far as I could find them; the strace is too big and you can find it here.

This is a regression: poky-3.1 (which uses linux-libc-headers 5.4) works. It seems we are not the only ones with this issue, and others have already given up on Yocto-on-WSL2.

Hope this is useful,
Matthias

linux-libc-headers.log-no-strace.tar.xz

obvious(?) ruby error: adding erroneous second ".gemspec" suffix

Robert P. J. Day

#51833

i'm not fluent enough in ruby to want to submit a patch for this, so
i'll let someone higher up the food chain handle it.

  trying to build a number of "native" ruby recipes from
meta-openstack, and getting precisely the same error for various
recipes:

| ERROR:  Gemspec file not found: XXXXX-native.gemspec.gemspec

the clear bug here is that something is adding a ".gemspec" suffix to
a string that *already* has that suffix. that error is acknowledged
here ("Append '.gemspec' extension only when it is not present"):

https://github.com/voxik/rubygems/commit/6c3f0dc798966a6474f6d694da05a15d620760d6

so someone who is more comfortable with ruby is invited to deal with
that.

rday

is there a focused place to ask about ruby/gems WRT yocto building?

Robert P. J. Day

#51832

to prepare for trying to build a number of ruby gems for WR LTS19
(effectively zeus, as always), i thought i'd start simple and begin
with building for qemux86-64 with gatesgarth so i could plausibly
claim that i have a working basis for comparison, whereupon if that
worked for what i was after, i could work backwards.

  i just now started a build for qemux86-64/gatesgarth with "bitbake
ruby", and i'll take it from there. knowing little about ruby, is
there a smaller community that would help with issues i run into, or
should i keep the discussion here?

  i want to start by trying to build absolutely stock puppet and chef,
and if that turns out to need fixing, i will of course submit patches.
if anyone has already gone through this exercise, that would be just
ducky.

  i should have the result of the first build in an hour or two --
given that i'm not trying to do anything out of the ordinary, i would
*hope* that a totally generic build would work out of the box, but
we'll see.

rday

p.s. the above recipes involve the layers meta-cloud-services and
sub-layer meta-openstack.

[meta-selinux][PATCH] audit: enable arm/aarch64 processor support by default

Yi Zhao

#51831

We encountered a runtime error for auditctl on lib32 image for aarch64:

root@qemuarm64:~# auditctl -a always,exit -F arch=b32 -S adjtimex -S settimeofday -k time_change
arch elf mapping not found

The root cause is the aarch64 processor support is not enabled for arm
build. Refer to Debian[1] and Fedora[2], actually we can enable
arm/aarch64 processor support unconditionally.

[1] https://salsa.debian.org/debian/audit/-/commit/8c6b2049bafb52712ca981e73d5b79d5bd97e08e
[2] https://src.fedoraproject.org/rpms/audit/blob/master/f/audit.spec

Signed-off-by: Yi Zhao <yi.zhao@...>
---
 recipes-security/audit/audit_2.8.5.bb | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/recipes-security/audit/audit_2.8.5.bb b/recipes-security/audit/audit_2.8.5.bb
index e3e5ddd..e2e0352 100644
--- a/recipes-security/audit/audit_2.8.5.bb
+++ b/recipes-security/audit/audit_2.8.5.bb
@@ -41,9 +41,9 @@ EXTRA_OECONF += "--without-prelude \
         --without-python \
         --without-golang \
         --disable-zos-remote \
+        --with-arm=yes \
+        --with-aarch64=yes \
         "
-EXTRA_OECONF_append_arm = " --with-arm=yes"
-EXTRA_OECONF_append_aarch64 = " --with-aarch64=yes"
 
 EXTRA_OEMAKE += "PYLIBVER='python${PYTHON_BASEVERSION}' \
 	PYINC='${STAGING_INCDIR}/$(PYLIBVER)' \
-- 
2.25.1

Need to disable IPV6 completely from the yocto image for Raspberrypi

@prashant2314

#51830

Dear Team,

I'm using yocto dunfell version 3.1.3 . in my image ipv6 configuration is coming, which I don't need. I need to disable it completely.

Please assist me the correct way to do the same.

Thanks.

Re: [ANNOUNCEMENT] Yocto Project 3.2.1 (gatesgarth-24.0.1) is Released

Peter Kjellerstedt

#51829

Show quoted text

-----Original Message-----
From: Mittal, Anuj <anuj.mittal@...>
Sent: den 22 december 2020 17:55
To: Tummalapalli, Vineela <vineela.tummalapalli@...>; Peter
Kjellerstedt <peter.kjellerstedt@...>
Cc: yocto@...
Subject: Re: [yocto] [ANNOUNCEMENT] Yocto Project 3.2.1 (gatesgarth-
24.0.1) is Released

On Tue, 2020-12-15 at 23:07 +0000, Peter Kjellerstedt wrote:
Repository Name: meta-gplv2
Repository Location: https://git.yoctoproject.org/git/meta-gplv2
Branch: gatesgarth
Tag: yocto-3.2.1The yocto-3.2.1 and gatesgarth-24.0.1 tags for meta-gplv2 have been
incorrectly
set on the dunfell branch rather than the gatesgarth branch. The Git
revision
and tar balls below are correct though. Since the tags are signed I
do now want
to modify them myself, so please correct them as soon as possible.Vineela isn't working this week I think so she might not be able to
help but it looks like the commit tagged is on gatesgarth ...

https://git.yoctoproject.org/clean/cgit.cgi/meta-gplv2/log/?h=gatesgarth

$ git branch -a --contains yocto-3.2.1
* master
  remotes/origin/HEAD -> origin/master
  remotes/origin/gatesgarth
  remotes/origin/master
  remotes/origin/master-next

Thanks,

AnujYou are absolutely correct. It seems the tags were incorrect for an hour 
when first created, and apparently our local Git mirror does not handle 
tags being updated so it still provides the original (incorrect) tags. 
Thank you for pointing out what was a problem on our side. I will take 
it up with our SCM team.

//Peter

Re: [ANNOUNCEMENT] Yocto Project 3.2.1 (gatesgarth-24.0.1) is Released

Anuj Mittal

#51828

On Tue, 2020-12-15 at 23:07 +0000, Peter Kjellerstedt wrote:
Repository Name: meta-gplv2
Repository Location: https://git.yoctoproject.org/git/meta-gplv2
Branch: gatesgarth
Tag: yocto-3.2.1The yocto-3.2.1 and gatesgarth-24.0.1 tags for meta-gplv2 have been
incorrectly 
set on the dunfell branch rather than the gatesgarth branch. The Git
revision 
and tar balls below are correct though. Since the tags are signed I
do now want 
to modify them myself, so please correct them as soon as possible.Vineela isn't working this week I think so she might not be able to
help but it looks like the commit tagged is on gatesgarth ...

https://git.yoctoproject.org/clean/cgit.cgi/meta-gplv2/log/?h=gatesgarth

$ git branch -a --contains yocto-3.2.1
* master
  remotes/origin/HEAD -> origin/master
  remotes/origin/gatesgarth
  remotes/origin/master
  remotes/origin/master-next

Thanks,

Anuj

Re: [ANNOUNCEMENT] Yocto Project 3.2.1 (gatesgarth-24.0.1) is Released

Peter Kjellerstedt

#51827

Show quoted text

-----Original Message-----
From: yocto@... <yocto@...> On
Behalf Of Peter Kjellerstedt
Sent: den 16 december 2020 00:08
To: Vineela <vineela.tummalapalli@...>
Cc: 'yocto@...' <yocto@...>
Subject: Re: [yocto] [ANNOUNCEMENT] Yocto Project 3.2.1 (gatesgarth-
24.0.1) is Released

-----Original Message-----
From: yocto@... <yocto@...> On
Behalf Of Vineela
Sent: den 15 december 2020 22:13
To: 'yocto-announce@...' <yocto-
announce@...>; 'yocto@...'
<yocto@...>; 'yocto-request@...'<yocto-
request@...>
Subject: [yocto] [ANNOUNCEMENT] Yocto Project 3.2.1 (gatesgarth-24.0.1)
is Released

Hello,

We are pleased to announce the Yocto Project 3.2.1 (gatesgarth-24.0.1)
Release is now available for download.

http://downloads.yoctoproject.org/releases/yocto/yocto-3.2.1/poky-gatesgarth-24.0.1.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-3.2.1/poky-gatesgarth-24.0.1.tar.bz2

A gpg signed version of these release notes is available at:

http://downloads.yoctoproject.org/releases/yocto/yocto-3.2.1/RELEASENOTES

Full Test Report:

http://downloads.yoctoproject.org/releases/yocto/yocto-
3.2.1/testreport.txt

Thank you for everyone's contributions to this release.

Vineela Tummalapalli
Yocto Project Build and Release
vineela.tummalapalli@...

--------------------------
yocto-3.2.1 Release Notes
--------------------------

--------------------------
 Repositories/Downloads
--------------------------[cut]

Repository Name: meta-gplv2
Repository Location: https://git.yoctoproject.org/git/meta-gplv2
Branch: gatesgarth
Tag: yocto-3.2.1The yocto-3.2.1 and gatesgarth-24.0.1 tags for meta-gplv2 have been
incorrectly set on the dunfell branch rather than the gatesgarth 
branch. The Git revision and tar balls below are correct though. 
Since the tags are signed I do not want to modify them myself, so 
please correct them as soon as possible.

Git Revision: 6e8e969590a22a729db1ff342de57f2fd5d02d43
Release Artefact: meta-gplv2-gatesgarth-24.0.1
sha: f43941fee62bccb5dee55809ab8c65d60eae82cf06cd05f3b150e93efaff86b6
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-3.2.1/meta-gplv2-gatesgarth-24.0.1.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-3.2.1/meta-gplv2-gatesgarth-24.0.1.tar.bz2//Peter*ping* The tags in meta-gplv2 are still incorrect.

//Peter

Automatic addition of trailing slashes on layers.openembedded.org

Paul Barker

#51826

Hi folks,

Working on the docs recently we noticed that there is no automatic
addition of a trailing slash on layers.openembedded.org when it's
needed:

https://layers.openembedded.org/layerindex/branch/master/layer/openembedded-core
- shows "Page not found".

https://layers.openembedded.org/layerindex/branch/master/layer/openembedded-core/
- shows the layer correctly.

Is this something that can easily be fixed?

-- 
Paul Barker
Konsulko Group

M+ & H bugs with Milestone Movements WW51

Stephen Jolley

#51825

All,

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

Priority	Bug ID	Short Description	Changer	Owner	Was	Became
Medium+	5322	Global DNS fallback mechanism not present in poky distro	kai.kang@...	kai.kang@...	3.3 M1	3.3 M2
	11385	poky-container: clarify that meta-data should be checked out using native tools that run the host and not with tools in container	timothy.t.orling@...	timothy.t.orling@...	3.3 M1	3.3 M2
	12060	It is possible to specify a PACKAGE and a PKG_ rename that conflict	kai.kang@...	kai.kang@...	3.3 M1	3.3 M2
	12342	lib32-core-image-sato -ctestimage failed due to wrong package names	kai.kang@...	kai.kang@...	3.3 M1	3.3 M2
	12917	Warnings from nightly-multilib builds (build-deps)	kai.kang@...	kai.kang@...	3.3 M1	3.3 M2
	13008	toaster testing	david.reyna@...	david.reyna@...	3.3 M1	3.3 M3
	13109	Implement CPE to package to Release mapping	david.reyna@...	david.reyna@...	3.3 M1	3.3 M3
	13103	[Bug][QA 2.7 M1 rc1][Toaster] "Recipes" table┬á and ┬á"machines" table are not getting populated after clicking┬áon imported layer as well as after clicking Machines Tab on project page	david.reyna@...	david.reyna@...	3.3 M1	3.3 M2
	13182	Inconsistency detected by ld.so: dl-open.c: 274: dl_open_worker: Assertion xxx failed	Qi.Chen@...	Qi.Chen@...	3.3 M1	3.3 M3
	13311	xargs: fdleak.c:396: complain_about_leaky_fds: Assertion `no_leaks' failed.	randy.macleod@...	mingli.yu@...	3.4	3.3 M3
	13411	ptest-perl.bbclass run-ptest is too greedy for SKIP	timothy.t.orling@...	timothy.t.orling@...	3.3 M1	3.3 M2
	13425	Add bblock and bbunlock helper tools	randy.macleod@...	newcomer@...	3.3 M1	3.3 M2
	13674	master dnf failures on qemumips	randy.macleod@...	mingli.yu@...	3.4	3.3 M3
	13690	runqemu with slirp, forwarded host ports are not available on host	timothy.t.orling@...	timothy.t.orling@...	3.3 M1	3.3 M2
	13722	Debugging With the GNU Project Debugger enhancements	randy.macleod@...	newcomer@...	3.3 M1	3.3 M2
	13768	base-files do_package fatal error in subprocess	randy.macleod@...	mingli.yu@...	3.4	3.3 M2
	13930	Port the CROPS toaster-container selenium tests to the Autobuilder	timothy.t.orling@...	timothy.t.orling@...	3.3 M1	3.3 M2
	13934	Apparent duplication of libtirpc package causes failure in "bitbake linux-yocto -c menuconfig"	hongxu.jia@...	hongxu.jia@...	3.1.5	3.3 M4
	13938	devtool modify virtual/kernel fails when EXTRAVERSION field is empty in Makefile	timothy.t.orling@...	timothy.t.orling@...	3.3 M1	3.3 M2
	14020	environment-setup script in multilib eSDK doesn't work for multilib variant	liezhi.yang@...	liezhi.yang@...	3.3 M1	3.3 M2
	14026	documentation how to use systemd is inconsistent	randy.macleod@...	mark.morton@...	3.3 M1	3.3 M2
	14051	[QA 3.2 M3 RC1] failure in ptest : valgrind.drd and valgrind.helgrind	randy.macleod@...	anuj.mittal@...	3.3 M1	3.3 M2
	14085	Toaster UI should know when bitbake crashed	david.reyna@...	david.reyna@...	3.3 M1	3.3 M2
	14098	absolute path in TEMPLATECONF should be rejected or warned, makes ext-sdk uninstallable	timothy.t.orling@...	timothy.t.orling@...	3.3 M1	3.3 M2
	14093	master] a-quick python warning	timothy.t.orling@...	timothy.t.orling@...	3.3 M1	3.3 M2
	14118	systemd services not enabled when using package feed	kai.kang@...	kai.kang@...	3.3 M1	3.3 M2
	14126	resolvconf incompatible with busybox flock	randy.macleod@...	newcomer@...	3.3 M1	3.3 M2
	14150	devtool: modify: fails for gstreamer1.0-plugins-good	timothy.t.orling@...	unassigned@...	3.3 M2	0.0.0
	14151	devtool build fails for python3	timothy.t.orling@...	unassigned@...	3.3 M2	0.0.0

Thanks,

Stephen K. Jolley

Yocto Project Program Manager

( Cell: (208) 244-4460

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

Enhancements/Bugs closed WW51!

Stephen Jolley

#51824

All,

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

Who	Count
mhalstead@...	3
richard.purdie@...	1
jay.shen.teoh@...	1
Grand Total	5

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.3

Stephen Jolley

#51823

All,

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

Who	Count
richard.purdie@...	36
ross@...	27
david.reyna@...	21
bluelightning@...	19
bruce.ashfield@...	14
timothy.t.orling@...	12
mark.morton@...	11
JPEWhacker@...	11
kai.kang@...	10
sakib.sajal@...	10
akuster808@...	10
trevor.gamblin@...	9
Qi.Chen@...	6
hongxu.jia@...	4
raj.khem@...	4
idadelm@...	4
randy.macleod@...	4
yi.zhao@...	4
mingli.yu@...	4
mostthingsweb@...	3
chee.yang.lee@...	3
alejandro@...	3
jon.mason@...	2
matthewzmd@...	2
jeanmarie.lemetayer@...	2
pokylinux@...	2
saul.wold@...	2
anuj.mittal@...	2
ydirson@...	2
jaewon@...	2
matt.ranostay@...	1
apoorvsangal@...	1
joe.slater@...	1
akuster@...	1
mhalstead@...	1
kexin.hao@...	1
aehs29@...	1
dl9pf@...	1
kergoth@...	1
liezhi.yang@...	1
mark.hatle@...	1
maxime.roussinbelanger@...	1
shachar@...	1
Martin.Jansa@...	1
kamensky@...	1
Grand Total	260

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

#51822

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 and how to create a bugzilla account at: https://bugzilla.yoctoproject.org/createaccount.cgi

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 338 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@...

[auh][PATCH] upgrade-helper.py: handle unassigned recipes correctly

Alexander Kanavin

#51821

Attempting to send to unassigned@... bounces immediately,
which means the CC recipients (such as oe-core list) won't get the email
either.

Instead, send to cc directly.

Signed-off-by: Alexander Kanavin <alex.kanavin@...>
---
 upgrade-helper.py | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/upgrade-helper.py b/upgrade-helper.py
index 7ed7af4..eb3935e 100755
--- a/upgrade-helper.py
+++ b/upgrade-helper.py
@@ -320,7 +320,10 @@ class Updater(object):
=20
         cc_addr =3D None
         if "cc_recipients" in settings:
-            cc_addr =3D settings["cc_recipients"].split()
+            if 'unassigned' in to_addr:
+                to_addr =3D settings["cc_recipients"].split()
+            else:
+                cc_addr =3D settings["cc_recipients"].split()
=20
         newversion =3D pkg_ctx['NPV'] if not pkg_ctx['NPV'].endswith("ne=
w-commits-available") else pkg_ctx['NSRCREV']
         subject =3D "[AUH] " + pkg_ctx['PN'] + ": upgrading to " + newve=
rsion
--=20
2.29.2

Re: hostapd_free_hapd_data: Interface wlan0 wasn't started #linux #kernel #dunfell

Shamil Khan

#51820

Hi VR,

Please make sure that the interface name in hostapd.conf matches with the wireless interface name of your target.
By default it is set to wlan0, but it could be different in your target (for ex, wlp2s0...).

Best regards,
Shamil