Current Autobuilder Intermittent bugs by the WW created or closed.
Stephen Jolley
All,
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,
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 334 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: QA notification for completed autobuilder build (yocto-3.2_M3.rc1)
Sangeeta Jain
Hello all,
toggle quoted messageShow quoted text
This is the full report for yocto-3.2_M3.rc1: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults ======= Summary ======== Beaglebone can not boot up, hence all beaglebone test case are blocked in this release. No high milestone defects. 2 new defects and 3 ptest failures are found: 1. The beaglebone can not bootup (BUG id:14052) This bug blocked all beaglebone test cases. 2. failure in oe-core manual test: test_dependency_explorer_is_launched (BUG id:14055) 3. valgrind ptest failed (BUG id:14051) 4. parted ptest failed (BUG id:14050) 5. pango ptest failed (BUG id:14049) ======= Bugs ======== https://bugzilla.yoctoproject.org/show_bug.cgi?id=14052 https://bugzilla.yoctoproject.org/show_bug.cgi?id=14055 https://bugzilla.yoctoproject.org/show_bug.cgi?id=14051 https://bugzilla.yoctoproject.org/show_bug.cgi?id=14050 https://bugzilla.yoctoproject.org/show_bug.cgi?id=14049 This is the full report for yocto-3.2_M3.rc1: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults Thanks, Sangeeta
-----Original Message-----
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
[meta-zephyr][PATCH v3] zephyr-kernel: add Zephyr RTOS version 2.3.0 support
yock.gen.mah@...
From: "Mah, Yock Gen" <yock.gen.mah@intel.com>
Signed-off-by: Mah, Yock Gen <yock.gen.mah@intel.com> --- classes/zephyr-kernel-src.bbclass | 16 ++++++--- .../{qemu_4.2.%.bbappend => qemu_%.bbappend} | 0 .../zephyr-kernel/zephyr-kernel-common.inc | 3 +- .../zephyr-kernel/zephyr-kernel-src_2.2.bb | 33 ------------------- .../zephyr-kernel/zephyr-kernel-src_2.3.bb | 24 ++++++++++++++ .../zephyr-kernel/zephyr-kernel-test.inc | 5 ++- 6 files changed, 39 insertions(+), 42 deletions(-) rename recipes-devtools/qemu/{qemu_4.2.%.bbappend => qemu_%.bbappend} (100%) delete mode 100644 recipes-kernel/zephyr-kernel/zephyr-kernel-src_2.2.bb create mode 100644 recipes-kernel/zephyr-kernel/zephyr-kernel-src_2.3.bb diff --git a/classes/zephyr-kernel-src.bbclass b/classes/zephyr-kernel-src.bbclass index 653cb9b..50e46af 100644 --- a/classes/zephyr-kernel-src.bbclass +++ b/classes/zephyr-kernel-src.bbclass @@ -1,13 +1,19 @@ #Set relevant variables based on Zephyr kernel version -PREFERRED_VERSION_zephyr-kernel ??= "2.2.0" +PREFERRED_VERSION_zephyr-kernel ??= "2.3.0" -SRCREV = "d39cb42d0920d5658fad358ad5b91de75d747a20" +SRCREV_FORMAT = "default_cmsis" +SRCREV_default = "b8c78e254ff875680e99c9f131fbe285c4575927" +SRCREV_cmsis = "542b2296e6d515b265e25c6b7208e8fea3014f90" -SRC_URI = "git://github.com/zephyrproject-rtos/zephyr.git;protocol=https;branch=v2.2-branch \ + +SRC_URI = "git://github.com/zephyrproject-rtos/zephyr.git;protocol=https;branch=v2.3-branch;name=default \ + git://github.com/zephyrproject-rtos/cmsis.git;protocol=https;destsuffix=git/modules/cmsis;name=cmsis \ file://0001-cmake-add-yocto-toolchain.patch \ " -PV = "2.2.0" + +PV = "2.3.0+git${SRCPV}" + LICENSE = "Apache-2.0" LIC_FILES_CHKSUM = "file://LICENSE;md5=fa818a259cbed7ce8bc2a22d35a464fc" @@ -15,7 +21,7 @@ ZEPHYR_TEST_SRCDIR = "tests/legacy/kernel/" python () { src_pn = d.getVar('PREFERRED_VERSION_zephyr-kernel', True) - if src_pn == '2.2.0': + if src_pn == '2.3.0': return else: bb.error("Unsupported Zephyr kernel version requested") diff --git a/recipes-devtools/qemu/qemu_4.2.%.bbappend b/recipes-devtools/qemu/qemu_%.bbappend similarity index 100% rename from recipes-devtools/qemu/qemu_4.2.%.bbappend rename to recipes-devtools/qemu/qemu_%.bbappend diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc b/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc index 7e569ed..7fa4b25 100644 --- a/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc +++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc @@ -15,13 +15,14 @@ ZEPHYR_MAKE_OUTPUT = "zephyr.elf" EXTRA_OECMAKE = " -DZEPHYR_BASE=${S} -DZEPHYR_GCC_VARIANT=yocto -DBOARD=${BOARD} -DARCH=${ARCH} -DCROSS_COMPILE=${CROSS_COMPILE} -DZEPHYR_SYSROOT=${ZEPHYR_SYSROOT} -DZEPHYR_TOOLCHAIN_VARIANT=yocto" +EXTRA_OECMAKE_append_arm = " -DZEPHYR_MODULES=${S}/modules/cmsis" export ZEPHYR_BASE="${S}" # We always need a toolchain to cross-compile. INHIBIT_DEFAULT_DEPS = "1" DEPENDS += "gcc-cross-${TARGET_ARCH} libgcc ${TOOLCHAIN_TARGET_TASK} gperf-native" -DEPENDS += " python3-pyelftools-native python3-pyyaml-native" +DEPENDS += " python3-pyelftools-native python3-pyyaml-native python3-pykwalify-native" CROSS_COMPILE = "${STAGING_BINDIR_TOOLCHAIN}/${TARGET_PREFIX}" DEPENDS_append_qemuall = " qemu-native qemu-helper-native" diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-src_2.2.bb b/recipes-kernel/zephyr-kernel/zephyr-kernel-src_2.2.bb deleted file mode 100644 index a3e1c28..0000000 --- a/recipes-kernel/zephyr-kernel/zephyr-kernel-src_2.2.bb +++ /dev/null @@ -1,33 +0,0 @@ - -LICENSE = "Apache-2.0" -LIC_FILES_CHKSUM = "file://LICENSE;md5=fa818a259cbed7ce8bc2a22d35a464fc" - -# tag v2.2 -SRCREV="d39cb42d0920d5658fad358ad5b91de75d747a20" -SRC_URI = "git://github.com/zephyrproject-rtos/zephyr.git;protocol=https;branch=v2.2-branch \ - file://0001-cmake-add-yocto-toolchain.patch \ - " -inherit cmake -PV = "2.2.0" -S = "${WORKDIR}/git" - -IMAGE_NO_MANIFEST = "1" -INHIBIT_DEFAULT_DEPS = "1" - -do_configure[noexec] = "1" -do_compile[noexec] = "1" - -do_compile () { -} - -do_install () { - kerneldir=${D}/usr/src/zephyr - install -d $kerneldir - cp -r ${S}/* $kerneldir -} - -PACKAGES = "${PN}" -FILES_${PN} = "/usr/src/zephyr" - -SYSROOT_DIRS += "/usr/src/zephyr" - diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-src_2.3.bb b/recipes-kernel/zephyr-kernel/zephyr-kernel-src_2.3.bb new file mode 100644 index 0000000..8e8b5b8 --- /dev/null +++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-src_2.3.bb @@ -0,0 +1,24 @@ + +inherit zephyr-kernel-src +inherit cmake + +S = "${WORKDIR}/git" + +IMAGE_NO_MANIFEST = "1" +INHIBIT_DEFAULT_DEPS = "1" + +do_configure[noexec] = "1" +do_compile[noexec] = "1" + + +do_install () { + kerneldir=${D}/usr/src/zephyr + install -d $kerneldir + cp -r ${S}/* $kerneldir +} + +PACKAGES = "${PN}" +FILES_${PN} = "/usr/src/zephyr" + +SYSROOT_DIRS += "/usr/src/zephyr" + diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-test.inc b/recipes-kernel/zephyr-kernel/zephyr-kernel-test.inc index 65da7e8..faf28bd 100644 --- a/recipes-kernel/zephyr-kernel/zephyr-kernel-test.inc +++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-test.inc @@ -1,4 +1,4 @@ -ZEPHYRTESTS_remove = "fifo fp_sharing lifo mbox mem_heap mem_pool \ +ZEPHYRTESTS_remove = "fifo fpu_sharing lifo mbox mem_heap mem_pool \ mem_protect mem_slab msgq mutex pipe profiling sched semaphore \ stack threads tickless timer workq" @@ -23,12 +23,11 @@ ZEPHYRTESTS_remove = "gen_isr_table spinlock smp mp" ZEPHYRTESTS = " \ common \ context \ - critical \ device \ early_sleep \ fatal \ fifo \ - fp_sharing \ + fpu_sharing \ gen_isr_table \ interrupt \ lifo \ -- 2.25.1
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: RDEPENDS problem
Quentin Schulz
Hi Greg,
On Mon, Sep 21, 2020 at 09:46:51PM +0000, Greg Wilson-Lindberg wrote: .so files are installed in the -dev package even with the line above. Please have a look here: https://wiki.yoctoproject.org/wiki/TipsAndTricks/Packaging_Prebuilt_Libraries#Non-versioned_Libraries if there is really no way for you to avoid having a non-versioned library. You can check if .so files are part of a package by using `oe-pkgdata-util find-path /usr/lib/libcanfestival.so` Cheers, Quentin
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: #yocto systemd not able to start sshd after a reboot
#yocto
On 9/21/20 5:17 AM, srijan.nandi@gmail.com wrote:
/Seems that some leftovers from System V still reside in YOCTO...Yocto project supports sysvinit as init system option as well so no there are no leftovers. /Usually you use socket activation for sshd then you would enable sshd.socket and not sshd.service, socket will be listening on incoming connections on ssh port ( 22 by defaault ) and launch sshd.service whenever there is incoming ssh connection request. I suggest you should perhaps follow this approach as well, its also efficient due to its on-demand launch nature. Thanks and Regards,
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: preistall package when use a package manager
On 9/21/20 1:28 AM, Matteo Facchinetti wrote:
Hi,it seems you want to bundle unstalled packages ( rpms ) in your firmware, perhaps you can look at adding a ROOTFS_POSTPROCESS_COMMAND and copy the needed packages, but you need to be sure that all dependencies(rpms) are also made available as part of this bundle and you have to check this consistency everytime you update firmware Regards,
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: RDEPENDS problem
Maciej Pijanowski
On 21.09.2020 23:46, Greg
Wilson-Lindberg wrote:
You could try with PROVIDES: https://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#var-PROVIDESI have a custom recipe that copies a .so, that libMotors.so calls functions in another libcanfestival.so. When I first added in the copy of the .so I didn't have an RDEPENDS and Yocto printed out an warning listing the package that it wanted. I added an RDEPENDS_${PN} with all of the packages listed, but I'm still getting an error for the first libMotors.so: ERROR: userconfig-1.0-r0 do_package_qa: QA Issue: /home/sakura/lib/libMotors.so.1.0.0 contained in package userconfig requires libcanfestival.so, but no providers found in RDEPENDS_userconfig? [file-rdeps] In userdepends I added: RDEPENDS_${PN} += "canfestival libelf libgcrypt pcsc-lite-lib qtbase qtdeclarative qtserialport zint" Package canfestival_3-asc in has: FILES_${PN} = "/usr/lib/libcanfestival.so /usr/lib/libcanfestival_unix.so /usr/lib/libcanfestival_can_socket.so" which seems to me like it should satisfy the requirements of the RDEPENDS, but it is not. bitbake initially gave me a warning that listed canfestival as needing to be added to an RDEPENDS for userconfig. But now it is saying that it can't figure out what package supplies the libcanfestival.so file. Can someone help me to understand what is going on? How do I explicitly say that a package supplies a given file? -- Maciej Pijanowski Embedded Systems Engineer GPG: 9963C36AAC3B2B46 https://3mdeb.com | @3mdeb_com
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
[meta-zephyr][morty PATCH] zephyr-kernel: update URLs
Jon Mason
URLs no longer point to a valid location. Update to the current
location. Signed-off-by: Jon Mason <jon.mason@arm.com> --- classes/zephyr-kernel-src.bbclass | 2 +- recipes-kernel/zephyr-kernel/zephyr-kernel-src_1.6.bb | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/classes/zephyr-kernel-src.bbclass b/classes/zephyr-kernel-src.bbclass index d7aa81bfaa62..cd1503dc1299 100644 --- a/classes/zephyr-kernel-src.bbclass +++ b/classes/zephyr-kernel-src.bbclass @@ -3,7 +3,7 @@ PREFERRED_VERSION_zephyr-kernel ??= "1.6.0" SRCREV = "d4e799d77a36eaf6d678b357c207411ec32b2d62" -SRC_URI = "git://gerrit.zephyrproject.org/r/zephyr.git;protocol=https;branch=v1.6.0-branch \ +SRC_URI = "git://github.com/zephyrproject-rtos/zephyr.git;protocol=https;branch=v1.6-branch \ file://Makefile.toolchain.yocto " PV = "1.6.0" diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-src_1.6.bb b/recipes-kernel/zephyr-kernel/zephyr-kernel-src_1.6.bb index df373e850c94..b47e8ac1b7d0 100644 --- a/recipes-kernel/zephyr-kernel/zephyr-kernel-src_1.6.bb +++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-src_1.6.bb @@ -4,7 +4,7 @@ LIC_FILES_CHKSUM = "file://LICENSE;md5=fa818a259cbed7ce8bc2a22d35a464fc" # tag v1.6.0 SRCREV="d4e799d77a36eaf6d678b357c207411ec32b2d62" -SRC_URI = "git://gerrit.zephyrproject.org/r/zephyr.git;protocol=https;branch=v1.6.0-branch" +SRC_URI = "git://github.com/zephyrproject-rtos/zephyr.git;protocol=https;branch=v1.6-branch" SRC_URI += "file://Makefile.toolchain.yocto" PV = "1.6.0" -- 2.20.1
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
[meta-zephyr][PATCH] zephyr-kernel: Add python dependencies
Jon Mason
Zephyr refuses to compile due to missing python dependencies.
Signed-off-by: Jon Mason <jon.mason@arm.com> Signed-off-by: Ross Burton <ross.burton@arm.com> --- recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc b/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc index d7147d5b7b86..7e569edb694c 100644 --- a/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc +++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc @@ -2,6 +2,7 @@ ZEPHYR_INHERIT_CLASSES += "zephyr cmake" inherit ${ZEPHYR_INHERIT_CLASSES} +inherit python3native # There shouldn't be a manifest for zephyr kernels since there is no root # filesystem. @@ -20,6 +21,7 @@ export ZEPHYR_BASE="${S}" # We always need a toolchain to cross-compile. INHIBIT_DEFAULT_DEPS = "1" DEPENDS += "gcc-cross-${TARGET_ARCH} libgcc ${TOOLCHAIN_TARGET_TASK} gperf-native" +DEPENDS += " python3-pyelftools-native python3-pyyaml-native" CROSS_COMPILE = "${STAGING_BINDIR_TOOLCHAIN}/${TARGET_PREFIX}" DEPENDS_append_qemuall = " qemu-native qemu-helper-native" -- 2.20.1
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
RDEPENDS problem
Greg Wilson-Lindberg
I have a custom recipe that copies a .so, that libMotors.so calls functions in another libcanfestival.so.
When I first added in the copy of the .so I didn't have an RDEPENDS and Yocto printed out an warning listing the package that it wanted. I added an RDEPENDS_${PN} with all of the packages listed, but I'm still getting an error for the first libMotors.so: ERROR: userconfig-1.0-r0 do_package_qa: QA Issue: /home/sakura/lib/libMotors.so.1.0.0 contained in package userconfig requires libcanfestival.so, but no providers found in RDEPENDS_userconfig? [file-rdeps] In userdepends I added: RDEPENDS_${PN} += "canfestival libelf libgcrypt pcsc-lite-lib qtbase qtdeclarative qtserialport zint" Package canfestival_3-asc in has: FILES_${PN} = "/usr/lib/libcanfestival.so /usr/lib/libcanfestival_unix.so /usr/lib/libcanfestival_can_socket.so" which seems to me like it should satisfy the requirements of the RDEPENDS, but it is not. bitbake initially gave me a warning that listed canfestival as needing to be added to an RDEPENDS for userconfig. But now it is saying that it can't figure out what package supplies the libcanfestival.so file. Can someone help me to understand what is going on? How do I explicitly say that a package supplies a given file?
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Add
toggle quoted messageShow quoted text
DEPENDS += "libzip" in failing recipe ( .bb) file. On Mon, Sep 21, 2020 at 12:40 AM Jaymin Dabhi via lists.yoctoproject.org <jaymin.dabhi=vivaldi.net@lists.yoctoproject.org> wrote:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
On 2020-09-19 4:58 p.m., Mike Thompson
via lists.yoctoproject.org wrote:
Hi Mike, Could you send your tailscale recipe to
meta-openembedded/meta-networking? It looks like all the work is done aside from an email! ../Randy
-- # Randy MacLeod # Wind River Linux
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: #yocto systemd not able to start sshd after a reboot
#yocto
srijan.nandi@...
Seems strange to me too...I had been troubleshooting the sshd.service issue for two days. There was no logs, nothing. I was just hitting the wall. I tried a lot of combinations to get it to work but all failed.
The sshd.service was starting, if I manually did a systemctl start sshd.service. But always failed at startup. At times it would start and then get a signal 15 terminating and would close the daemon. After not able to resolve the issue, I started checking all the other services. Every other service was starting at bootup just fine except sshd. Not finding anything else to troubleshoot. I happened to stumble upon the sshd.socket and the Conflicts part of it. Did a hit and trial and it worked. Technically I still am not sure as to why.. -=Srijan Nandi
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: #yocto systemd not able to start sshd after a reboot
#yocto
Zoran
There was a sshd.socket file in /lib/systemd/system which had the following line in it.Interesting... Pushed/forced me to think. There is no formal dependency between sshd.service and sshd.socket! [vuser@fedora32-ssd systemd]$ systemctl list-dependencies sshd.service | grep ssh sshd.service ● ├─sshd-keygen.target ● │ ├─sshd-keygen@ecdsa.service ● │ ├─sshd-keygen@ed25519.service ● │ └─sshd-keygen@rsa.service [vuser@fedora32-ssd systemd]$ systemctl list-dependencies sshd.service | grep socket ● ├─lvm2-lvmetad.socket ● ├─lvm2-lvmpolld.socket [vuser@fedora32-ssd systemd]$ systemctl list-dependencies sshd.socket | grep sshd sshd.socket Strange... Isn't it?! Zoran _______ On Sat, Sep 19, 2020 at 3:37 PM <srijan.nandi@gmail.com> wrote:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: [meta-mingw][PATCH] Override SDK_VENDOR
Joshua Watt
On Mon, Sep 21, 2020, 8:12 AM Samuli Piippo <samuli.piippo@...> wrote:
Thanks. I figured that was the case. This is testing on the AB.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: [meta-mingw][PATCH] Override SDK_VENDOR
Samuli Piippo
On Mon, 21 Sep 2020 at 15:53, Joshua Watt <JPEWhacker@...> wrote: On Fri, Sep 18, 2020 at 7:30 AM Samuli Piippo <samuli.piippo@...> wrote: This enables it for both x86_64-mingw32 and i686-mingw32 targets and it makes sense since it's not about the target bitness but the mingw implementation. w64 has support for both targets and provides improved support over the original mingw32. >
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: [meta-mingw][PATCH] Override SDK_VENDOR
Joshua Watt
On Fri, Sep 18, 2020 at 7:30 AM Samuli Piippo <samuli.piippo@qt.io> wrote:
Does this enable it for the i686 toolchain also? Does that make sense?
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: #yocto systemd not able to start sshd after a reboot
#yocto
srijan.nandi@...
Seems that some leftovers from System V still reside in YOCTO... Correct??? Not sure about that. I choose to remove the Conflicts line and add the following in the sshd.socket file.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|