All,
The below were the owners of enhancements or bugs closed during the last
week!
Who
Count
randy.macl...@windriver.com
7
richard.pur...@linuxfoundation.org
2
ross.bur...@arm.com
1
louis.ran...@syslinbit.com
1
bruce.ashfi...@gmail.com
1
Grand Total
12
Thanks,
Stephen K.
All,
Below is the list as of top 31 bug owners as of the end of WW24 of who have
open medium or higher bugs and enhancements against YP 4.3. There are 90
possible work days left until the final release candidates for YP 4.3 needs
to be released.
Who
Count
michael.opdenac...@bootlin.com
32
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#Newc
On closer look, it should even say:
export MAGIC="\$OECORE_NATIVE_SYSROOT/usr/share/misc/magic.mgc"
If you can test this and confirm that it works, a patch would be welcome.
Alex
On Mon, 19 Jun 2023 at 18:55, Alexander Kanavin via
lists.yoctoproject.org
wrote:
>
> I think there is a mistake in
I think there is a mistake in the file recipe (and rpm has the problem too):
cat <<- EOF > ${D}${SDKPATHNATIVE}/environment-setup.d/file.sh
export MAGIC="$OECORE_NATIVE_SYSROOT${datadir}/misc/magic.mgc"
EOF
$OECORE_NATIVE_SYSROOT should be prefixed with a \ to prev
Hello, I'm trying to add the arm toolchain to my yocto project but I just got
this error
```
| cp: cannot stat
'.../tmp-glibc/work/cortexa7t2hf-neon-vfpv4-ostl-linux-gnueabi/external-arm-toolchain/2022.02-r0/image/local/SUPPORTED':
No such file or directory
```
It comes from the `external-arm-to
Hi,
I'm working on master oe core master branch and run into problem with file for
nativesdk (buildtools tarball).
File started to use MAGIC variable initialized from
.../environment-setup.d/file.sh, like
/usr/local/oe-sdk-hardcoded-buildpath/sysroots/x86_64-xesdk-linux/usr/share/misc/magic.mgc
Currently the code can race as there is a read/write thread handling the stdio
but
there is no guarantee that when the process exits, the thread has handled all
the
data. This results in output where "END:" isn't actually at the end of the logs
but somewhere in the middle of the output.
Synchron
On Mon, 2023-06-19 at 09:53 +, Ross Burton wrote:
> On 19 Jun 2023, at 10:48, Alex Kiernan via lists.yoctoproject.org
> wrote:
> > FWIW we swapped out our x86_64 build machines for Aarch64 build
> > machines (both 20.04) in AWS with pretty much zero pain - it went way
> > better than I was ex
On 19 Jun 2023, at 10:48, Alex Kiernan via lists.yoctoproject.org
wrote:
> FWIW we swapped out our x86_64 build machines for Aarch64 build
> machines (both 20.04) in AWS with pretty much zero pain - it went way
> better than I was expecting. That said we don't run ptests, or qemu,
> or …
Sure, o
On Mon, Jun 19, 2023 at 10:44 AM Ross Burton wrote:
>
> On 19 Jun 2023, at 10:34, Richard Purdie via lists.yoctoproject.org
> wrote:
> > The ARM worker worries me a lot more. The 1804 worker is currently
> > stable but I do worry a bit what will happen when we change the OS on
> > that machine.
On Mon, 2023-06-19 at 09:44 +, Ross Burton wrote:
> On 19 Jun 2023, at 10:34, Richard Purdie via lists.yoctoproject.org
> wrote:
> > The ARM worker worries me a lot more. The 1804 worker is currently
> > stable but I do worry a bit what will happen when we change the OS on
> > that machine. I
On 19 Jun 2023, at 10:34, Richard Purdie via lists.yoctoproject.org
wrote:
> The ARM worker worries me a lot more. The 1804 worker is currently
> stable but I do worry a bit what will happen when we change the OS on
> that machine. In theory it should be fine and it could well be but that
> hardw
On Mon, 19 Jun 2023 at 11:34, Richard Purdie
wrote:
> This isn't as simple as you'd think.
>
> The x86 worker will be dropped when maintenance comes around to that
> point on the autobuilder, it is in the queue.
>
> The ARM worker worries me a lot more. The 1804 worker is currently
> stable but I
On Mon, 2023-06-19 at 11:02 +0200, Alexander Kanavin wrote:
> Even if we would have a subscription with Canonical, it would not be
> fair to ask contributors to fix issues that occur only on distribution
> available through commercial channels. So yes, it should be dropped
> ASAP.
>
> Alex
>
> On
Even if we would have a subscription with Canonical, it would not be
fair to ask contributors to fix issues that occur only on distribution
available through commercial channels. So yes, it should be dropped
ASAP.
Alex
On Mon, 19 Jun 2023 at 10:35, Michael Opdenacker via
lists.yoctoproject.org
w
Greetings,
I know that we are still testing and supporting Ubuntu 18.04, but should
we go on doing it?
This version no longer has public updates, so unless we have a
subscription with Canonical, we are going to be out of sync with the
updates that Ubuntu 18.04 subscribers get.
What do you
17 matches
Mail list logo
