The commit message should reference the two new CVEs as well:
CVE-2022-3786 and CVE-2022-3602: X.509 Email Address Buffer Overflows
https://www.openssl.org/blog/blog/2022/11/01/email-address-overflows/
On Tue, Nov 1, 2022 at 10:03 AM edtanous via lists.openembedded.org
wrote:
> From: Ed
Currently the hciattach bcm43xx firmware loader looks up the firmware
blob in /etc/firmware . Change this to /lib/firmware instead, so that
the path is consistent with Linux kernel which also looks up firmware
for the WiFi part in /lib/firmware .
Signed-off-by: Marek Vasut
---
Cc: Alexander
On Tue, 2022-11-01 at 13:40 -0400, Sean Anderson wrote:
> On 11/1/22 13:29, Richard Purdie wrote:
> > On Tue, 2022-11-01 at 12:14 -0400, Sean Anderson wrote:
> > > On 10/28/22 11:37, Richard Purdie wrote:
> > > > On Fri, 2022-10-28 at 11:29 -0400, Sean Anderson wrote:
> > > > > On 10/28/22 11:09,
On 11/1/22 13:44, Richard Purdie wrote:
> On Tue, 2022-11-01 at 13:40 -0400, Sean Anderson wrote:
>> On 11/1/22 13:29, Richard Purdie wrote:
>> > On Tue, 2022-11-01 at 12:14 -0400, Sean Anderson wrote:
>> > > On 10/28/22 11:37, Richard Purdie wrote:
>> > > > On Fri, 2022-10-28 at 11:29 -0400, Sean
From: Ed Tanous
OpenSSL 3.0.5 includes a HIGH level security vulnerability [1].
Upgrade the recipe to point to 3.0.7.
CVE-2022-3358 is reported fixed in 3.0.6, so drop the patch for that as
well.
[1] https://www.openssl.org/news/vulnerabilities.html
Signed-off-by: Ed Tanous
---
On 11/1/22 13:29, Richard Purdie wrote:
> On Tue, 2022-11-01 at 12:14 -0400, Sean Anderson wrote:
>> On 10/28/22 11:37, Richard Purdie wrote:
>> > On Fri, 2022-10-28 at 11:29 -0400, Sean Anderson wrote:
>> > > On 10/28/22 11:09, Richard Purdie wrote:
>> > > > On Wed, 2022-10-26 at 13:21 -0400,
On 11/1/22 3:03 PM, Gundlupet Raju, Sandeep wrote:
Hello,
We wanted to know what the actual use case is for running weston as
weston user only in OE core
http://cgit.openembedded.org/openembedded-core/tree/meta/recipes-graphics/wayland/weston-init/weston.service#n44
How is this expected to
The underlying _run() method has an ignore_status argument and can
either return the exit code or raise an exception if it is non-zero.
Add the same argument to the run() method so that test cases can change
this value. It currently defaults to True as that is the existing
behaviour, but a
This test doesn't get exercised on the autobuilder and so it was broken:
specifically some of the ln commands silently fail and the chroot isn't
usable.
Rewrite the test case to correctly construct a chroot so the test can
pass.
Signed-off-by: Ross Burton
---
meta/lib/oeqa/runtime/cases/dnf.py
Hi Armin,
On Tue, Oct 11, 2022 at 12:02 AM Khem Raj wrote:
>
> perf has need for python setuptools when scripting is enabled
> from 6.0.0 onwards it seems to throw an explicit error
>
> Signed-off-by: Khem Raj
> Cc: Bruce Ashfield
This one landed in master:
On 11/1/22 10:11 AM, Fabio Estevam wrote:
Hi Armin,
On Tue, Oct 11, 2022 at 12:02 AM Khem Raj wrote:
perf has need for python setuptools when scripting is enabled
from 6.0.0 onwards it seems to throw an explicit error
Signed-off-by: Khem Raj
Cc: Bruce Ashfield
This one landed in master:
On Tue, 1 Nov 2022 at 19:30, Sean Anderson wrote:
> I believe in order to set up pwbot you need a computer with
>
> - The git repository you want to track on it. The easiest way to do this is
> probably to run it on git.openembedded.org itself.
> - A patchwork API key (to modify the patch
The answer is basically 'patches welcome'. The original reason for
adding a weston user was to simply not run weston as root (which was
the case before). Further improving this to allow regular users use
core-image-weston for graphical things would be good, but figuring out
technical specifics is
On Tue, 1 Nov 2022 at 19:02, Alexander Kanavin via
lists.openembedded.org
wrote:
> > You can set up something like pwbot [3], which integrates with patchwork
> > and your repository. It produces messages like [4] automatically when it
> > notices they have been merged into the repositiry, and
Signed-off-by: Alexander Kanavin
---
meta/recipes-devtools/rust/rust/crossbeam_atomic.patch | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-devtools/rust/rust/crossbeam_atomic.patch
b/meta/recipes-devtools/rust/rust/crossbeam_atomic.patch
index
On Tue, 1 Nov 2022 at 10:17, Alexander Kanavin via
lists.openembedded.org
wrote:
>
> Rust targets have the form of 'arch-unknown-linux-gnu' while
> oe's native targets are 'arch-linux-gnu', e.g. omit the vendor.
>
> The effect this has on rust-native builds is that rust first builds
> itself as
On Tue, 1 Nov 2022 at 18:54, Sean Anderson via lists.openembedded.org
wrote:
> If you use a tool like b4 [1] it can automatically generate a summary
> thank-you message.
> As an example, [2]. This keeps the number of messages down and is not terribly
> burdensome for maintainers (since it fits
On 11/1/22 14:02, Alexander Kanavin wrote:
> [You don't often get email from alex.kana...@gmail.com. Learn why this is
> important at https://aka.ms/LearnAboutSenderIdentification ]
>
> On Tue, 1 Nov 2022 at 18:54, Sean Anderson via lists.openembedded.org
> wrote:
>> If you use a tool like b4
On 1 Nov 2022, at 21:02, Marek Vasut via lists.openembedded.org
wrote:
>>> +CFLAGS:append = " -DFIRMWARE_DIR=\\"${nonarch_base_libdir}/firmware\\""
>> why do we use append and not += here ?
>
> Isn't the override syntax preferred now ?
Different behaviour for different purposes. += would be
On 10/28/22 11:37, Richard Purdie wrote:
> On Fri, 2022-10-28 at 11:29 -0400, Sean Anderson wrote:
>> On 10/28/22 11:09, Richard Purdie wrote:
>> > On Wed, 2022-10-26 at 13:21 -0400, Sean Anderson wrote:
>> > > As noted in the cover letter, I ran
>> > >
>> > > oe-selftest -r
On Tue, 2022-11-01 at 12:14 -0400, Sean Anderson wrote:
> On 10/28/22 11:37, Richard Purdie wrote:
> > On Fri, 2022-10-28 at 11:29 -0400, Sean Anderson wrote:
> > > On 10/28/22 11:09, Richard Purdie wrote:
> > > > On Wed, 2022-10-26 at 13:21 -0400, Sean Anderson wrote:
> > > > > As noted in the
On Tue, Nov 1, 2022 at 7:21 AM Khem Raj wrote:
>
> On 11/1/22 10:11 AM, Fabio Estevam wrote:
> > Hi Armin,
> >
> > On Tue, Oct 11, 2022 at 12:02 AM Khem Raj wrote:
> >>
> >> perf has need for python setuptools when scripting is enabled
> >> from 6.0.0 onwards it seems to throw an explicit error
On 11/1/22 4:54 AM, Marek Vasut wrote:
Currently the hciattach bcm43xx firmware loader looks up the firmware
blob in /etc/firmware . Change this to /lib/firmware instead, so that
the path is consistent with Linux kernel which also looks up firmware
for the WiFi part in /lib/firmware .
Hi
Can you send the patch using git-send-email? Your mailer is either sending the
patch as plain attachments or reformatting the plain text, so git am can’t
apply it.
Ross
> On 1 Nov 2022, at 11:42, Blake Alexander via lists.openembedded.org
> wrote:
>
> [Edited Message Follows]
>
Signed-off-by: Sakib Sajal
---
meta/recipes-devtools/go/{go-1.19.2.inc => go-1.19.3.inc} | 2 +-
...o-binary-native_1.19.2.bb => go-binary-native_1.19.3.bb} | 6 +++---
...cross-canadian_1.19.2.bb => go-cross-canadian_1.19.3.bb} | 0
.../go/{go-cross_1.19.2.bb => go-cross_1.19.3.bb}
On 11/1/22 21:41, Khem Raj wrote:
On 11/1/22 4:54 AM, Marek Vasut wrote:
Currently the hciattach bcm43xx firmware loader looks up the firmware
blob in /etc/firmware . Change this to /lib/firmware instead, so that
the path is consistent with Linux kernel which also looks up firmware
for the WiFi
> On 1 Nov 2022, at 17:40, Sean Anderson via lists.openembedded.org
> wrote:
>
> I really wish you guys sent thank-you messages when you merged something.
> Makes
> it a lot easier to keep track of which series still need work.
My workflow is to have everything I submit in a local feature
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *popt* to *1.19* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe popt failed.
NOTE: Starting bitbake server...
NOTE: Reconnecting to
On Tue, 2022-11-01 at 05:35 -1000, Steve Sakoman wrote:
> There were 66 entries in the raffle:
>
> steve@hexa ~/Desktop $ wc -l cve-raffle.txt
> 66 cve-raffle.txt
>
> Many thanks to all who participated, this is great progress!
>
> And the winner is:
>
> steve@hexa ~/Desktop $ shuf -n 1
From: "Qiu, Zheng"
The CVE number in the patch is a typo. CVE-2022-2053 is not related to
libtiff. So fix it.
Signed-off-by: Zheng Qiu
Signed-off-by: Richard Purdie
(cherry picked from commit c9f76ef859b0b4edb83ac098816b625f52c78173)
Signed-off-by: Steve Sakoman
---
From: Ross Burton
Backport fixes from upstream for the following CVEs:
- CVE-2022-3599
- CVE-2022-3597
- CVE-2022-3626
- CVE-2022-3627
- CVE-2022-3570
- CVE-2022-3598
Signed-off-by: Ross Burton
Signed-off-by: Alexandre Belloni
Signed-off-by: Richard Purdie
(cherry picked from commit
From: Ross Burton
Signed-off-by: Ross Burton
Signed-off-by: Alexandre Belloni
(cherry picked from commit 5d30f124274d2822d72b56f84eb8c8ae64e31e0d)
Signed-off-by: Steve Sakoman
---
...ak-in-XRegisterIMInstantiateCallback.patch | 57 +++
From: Ross Burton
Signed-off-by: Ross Burton
Signed-off-by: Alexandre Belloni
(cherry picked from commit 769576f36aac9652525beec5c7e8a4d26632b844)
Signed-off-by: Steve Sakoman
---
meta/recipes-graphics/xorg-xserver/xserver-xorg.inc | 2 ++
1 file changed, 2 insertions(+)
diff --git
From: Ross Burton
Signed-off-by: Ross Burton
Signed-off-by: Alexandre Belloni
(cherry picked from commit e32401d8bf44afcca88af7e4c5948d2c28e1813f)
Signed-off-by: Steve Sakoman
---
...possible-memleaks-in-XkbGetKbdByName.patch | 63 +++
Please review this set of patches for langdale and have comments back by
end of day Friday.
Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/4401
The following changes since commit d40f7ddcfbdd5cb1d9f96271fefddf67e9044bb9:
openssl: Fix
From: Hitendra Prajapati
Upstream-Status: Backport from
https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=5485c56679d7c49b96e8fc8ca708b0b7e7c03c4b]
Description:
CVE-2022-3358 openssl: Using a Custom Cipher with NID_undef may lead to
NULL encryption.
Affects "openssl < 3.0.6"
From: Ross Burton
Signed-off-by: Ross Burton
Signed-off-by: Alexandre Belloni
Signed-off-by: Richard Purdie
(cherry picked from commit d820389728b0f5e085954b4f995da2b2014acedf)
Signed-off-by: Steve Sakoman
---
meta/recipes-devtools/qemu/qemu.inc | 1 +
From: Liam Beguin
The meson-wrapper adds setup options to facilitate cross-compilation.
The current options are exclusive to the setup sub-command and might
cause issues with other sub-commands.
Update the wrapper to make options sub-command specific.
Signed-off-by: Liam Beguin
Signed-off-by:
From: wangmy
Signed-off-by: Wang Mingyu
Signed-off-by: Alexandre Belloni
(cherry picked from commit 3c87597dcde7676858f76c1066cd87195ecc8aef)
Signed-off-by: Steve Sakoman
---
.../recipes-devtools/meson/{meson_0.63.2.bb => meson_0.63.3.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
On Tue, Nov 1, 2022 at 3:29 PM Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:
> On Tue, 2022-11-01 at 05:35 -1000, Steve Sakoman wrote:
> > There were 66 entries in the raffle:
> >
> > steve@hexa ~/Desktop $ wc -l cve-raffle.txt
> > 66 cve-raffle.txt
> >
> > Many thanks to all who
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *meson* to *0.64.0* has Failed
(devtool error).
Detailed error information:
The following devtool command failed: upgrade meson -V 0.64.0
NOTE: Starting bitbake server...
NOTE:
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *mtd-utils* to *2.1.5* has
Succeeded.
Next steps:
- apply the patch: git am 0001-mtd-utils-upgrade-2.1.4-2.1.5.patch
- check the changes to upstream patches and summarize
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-bcrypt* to *4.0.1*
has Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-cryptography-vectors*
to *38.0.2* has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-cryptography-vectors-upgrade-38.0.1-38.0.2.patch
- check the
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-pip* to *22.3* has
Succeeded.
Next steps:
- apply the patch: git am 0001-python3-pip-upgrade-22.2.2-22.3.patch
- check the changes to upstream patches and summarize
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libedit* to *20221030-3.1*
has Succeeded.
Next steps:
- apply the patch: git am
0001-libedit-upgrade-20210910-3.1-20221030-3.1.patch
- check the changes to upstream
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *mtools* to *4.0.42* has
Succeeded.
Next steps:
- apply the patch: git am 0001-mtools-upgrade-4.0.41-4.0.42.patch
- check the changes to upstream patches and summarize them
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-pbr* to *5.11.0* has
Succeeded.
Next steps:
- apply the patch: git am 0001-python3-pbr-upgrade-5.10.0-5.11.0.patch
- check the changes to upstream patches and
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe
*python3-hatch-fancy-pypi-readme* to *22.8.0* has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-hatch-fancy-pypi-readme-upgrade-22.7.0-22.8..patch
- check
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-dbusmock* to *0.28.6*
has Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-pytest* to *7.2.0*
has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-pytest-upgrade-7.1.3-7.2.0.patch
- check the changes to upstream patches and
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libidn2* to *2.3.4* has
Succeeded.
Next steps:
- apply the patch: git am 0001-libidn2-upgrade-2.3.3-2.3.4.patch
- check the changes to upstream patches and summarize them
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *repo* to *2.29.5* has
Succeeded.
Next steps:
- apply the patch: git am 0001-repo-upgrade-2.29.3-2.29.5.patch
- check the changes to upstream patches and summarize them in
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-mako* to *1.2.3* has
Succeeded.
Next steps:
- apply the patch: git am 0001-python3-mako-upgrade-1.2.2-1.2.3.patch
- check the changes to upstream patches and
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-pytest-subtests* to
*0.9.0* has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-pytest-subtests-upgrade-0.8.0-0.9.0.patch
- check the changes to
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-psutil* to *5.9.3*
has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-psutil-upgrade-5.9.2-5.9.3.patch
- check the changes to upstream patches and
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-pyrsistent* to
*0.19.1* has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-pyrsistent-upgrade-0.18.1-0.19.1.patch
- check the changes to upstream
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-zipp* to *3.10.0* has
Succeeded.
Next steps:
- apply the patch: git am 0001-python3-zipp-upgrade-3.9.0-3.10.0.patch
- check the changes to upstream patches and
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-wheel* to *0.38.0*
has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-wheel-upgrade-0.37.1-0.38.0.patch
- check the changes to upstream patches and
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *llvm* to *15.0.3* has Failed
(devtool error).
Detailed error information:
The following devtool command failed: finish -f llvm
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *ccache* to *4.7.2* has
Succeeded.
Next steps:
- apply the patch: git am 0001-ccache-upgrade-4.6.3-4.7.2.patch
- check the changes to upstream patches and summarize them in
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *systemd-boot* to *252* has
Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe systemd-boot failed.
NOTE: Starting bitbake server...
NOTE:
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *gnu-config* to
*f992bcc08219edb283d2ab31dd3871a4a0e8220e* has Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade gnu-config -S
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *go-runtime* to *1.19.2* has
Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe go-runtime failed.
NOTE: Starting bitbake server...
NOTE:
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *go* to *1.19.2* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe go failed.
NOTE: Starting bitbake server...
NOTE: Reconnecting to
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *orc* to *0.4.33* has
Succeeded.
Next steps:
- apply the patch: git am 0001-orc-upgrade-0.4.32-0.4.33.patch
- check the changes to upstream patches and summarize them in the
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *patchelf* to *0.16.1* has
Succeeded.
Next steps:
- apply the patch: git am 0001-patchelf-upgrade-0.15.0-0.16.1.patch
- check the changes to upstream patches and summarize
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *make* to *4.4* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe make failed.
NOTE: Starting bitbake server...
NOTE: Reconnecting to
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *diffstat* to *1.65* has
Succeeded.
Next steps:
- apply the patch: git am 0001-diffstat-upgrade-1.64-1.65.patch
- check the changes to upstream patches and summarize them in
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-hatchling* to
*1.11.1* has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-hatchling-upgrade-1.11.0-1.11.1.patch
- check the changes to upstream
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *mmc-utils* to
*4a32d090dcf6fec6ef0948e59094c4de406906cd* has Succeeded.
Next steps:
- apply the patch: git am 0001-mmc-utils-upgrade-to-latest-revision.patch
- check the
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-dtschema* to *2022.9*
has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-dtschema-upgrade-2022.8.3-2022.9.patch
- check the changes to upstream
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *glib-2.0* to *2.74.1* has
Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe glib-2.0 failed.
NOTE: Starting bitbake server...
NOTE:
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *inetutils* to *2.4* has
Succeeded.
Next steps:
- apply the patch: git am 0001-inetutils-upgrade-2.3-2.4.patch
- check the changes to upstream patches and summarize them in
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *gettext* to *0.21.1* has
Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe gettext failed.
NOTE: Starting bitbake server...
NOTE:
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *bind* to *9.18.8* has
Succeeded.
Next steps:
- apply the patch: git am 0001-bind-upgrade-9.18.7-9.18.8.patch
- check the changes to upstream patches and summarize them in
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *netbase* to *6.4* has
Succeeded.
Next steps:
- apply the patch: git am 0001-netbase-upgrade-6.3-6.4.patch
- check the changes to upstream patches and summarize them in the
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *glib-networking* to *2.74.0*
has Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *expat* to *2.5.0* has
Succeeded.
Next steps:
- apply the patch: git am 0001-expat-upgrade-2.4.9-2.5.0.patch
- check the changes to upstream patches and summarize them in
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *readline* to *8.2* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe readline failed.
NOTE: Starting bitbake server...
NOTE:
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libxcrypt-compat* to *4.4.29*
has Succeeded.
Next steps:
- apply the patch: git am 0001-libxcrypt-compat-upgrade-4.4.28-4.4.29.patch
- check the changes to upstream patches
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *systemd* to *252* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe systemd failed.
NOTE: Starting bitbake server...
NOTE: Reconnecting
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *socat* to *1.7.4.4* has
Succeeded.
Next steps:
- apply the patch: git am 0001-socat-upgrade-1.7.4.3-1.7.4.4.patch
- check the changes to upstream patches and summarize them
This release was yanked from PyPi.
https://github.com/pypa/wheel/issues/478
On Tue, Nov 1, 2022 at 5:41 PM Auto Upgrade Helper
wrote:
> Hello,
>
> this email is a notification from the Auto Upgrade Helper
> that the automatic attempt to upgrade the recipe *python3-wheel* to
> *0.38.0* has
https://docs.pytest.org/en/stable/changelog.html#pytest-7-2-0-2022-10-23
Excerpt from upstream release notes:
Deprecations
* #10012: Update pytest.PytestUnhandledCoroutineWarning to a
deprecation; it will raise an error in pytest 8.
* #10396: pytest no longer depends on the py
https://github.com/pytest-dev/pytest-subtests/blob/main/CHANGELOG.rst#090-2022-10-28
0.9.0 (2022-10-28)
* Python 3.11 is officially supported.
* Dropped support for Python 3.6.
Signed-off-by: Tim Orling
---
...ytest-subtests_0.8.0.bb => python3-pytest-subtests_0.9.0.bb} | 2 +-
1 file
https://hypothesis.readthedocs.io/en/latest/changes.html#v6-56-4
6.56.4 - 2022-10-28
* This patch updates some docs, and depends on exceptiongroup 1.0.0 final
to avoid a bug in the previous version.
6.56.3 - 2022-10-17
* This patch teaches text() to rewrite a few more filter predicates
38.0.3 - 2022-11-01
* Updated Windows, macOS, and Linux wheels to be compiled with OpenSSL
3.0.7, which resolves CVE-2022-3602 and CVE-2022-3786.
38.0.2 - 2022-10-11 (YANKED)
Attention!
This release was subsequently yanked from PyPI due to a regression in
OpenSSL.
* Updated Windows, macOS,
https://github.com/giampaolo/psutil/blob/master/HISTORY.rst#593
2022-10-18
Enhancements
* 2040, [macOS]: provide wheels for arm64 architecture. (patch by
Matthieu Darbois)
Bug fixes
* 2116, [macOS], [critical]: `psutil.net_connections`_ fails with
RuntimeError.
* 2135, [macOS]:
https://github.com/more-itertools/more-itertools/blob/master/docs/versions.rst#900
9.0.0
* Potentially breaking changes
- `grouper` no longer accepts an integer as its first
argument. Previously this raised a DeprecationWarning.
- `collate` has been removed. Use the built-in
https://launchpad.net/pytz/+announcement/30743
pytz 2022.6, containing the 2022f IANA database, has been released.
There are no code changes.
https://launchpad.net/pytz/+announcement/30736
pytz 2022.5 has been released containing the IANA 2022e database
release. There are no code changes.
https://github.com/jaraco/zipp/blob/main/CHANGES.rst#v3100
v3.10.0
* zipp is now a package.
https://github.com/jaraco/zipp/blob/main/CHANGES.rst#v391
v3.9.1
* Removed 'print' expression in test_pickle.
* bpo-43651: Apply io.text_encoding on Python 3.10 and later.
Signed-off-by: Tim Orling
* Refresh python3-bcrypt-crates.inc
Upstream release notes[1]:
* We now build PyPy manylinux wheels.
* Fixed a bug where passing an invalid salt to checkpw could result in
a pyo3_runtime.PanicException. It now correctly raises a ValueError.
[1] https://github.com/pyca/bcrypt/#401
qemuarmv5 passes testimage on with the linux-yocto-dev kernel. Add it
to the compatible machines list for that recipe.
Signed-off-by: Jon Mason
---
meta/recipes-kernel/linux/linux-yocto-dev.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
This is to get rid of the intermittent failures in clock_gettime04,
which are likely caused by different clock tick rates on platforms.
Here give two thresholds (in milliseconds) for comparison, one for
COARSE clock and one for the rest.
Signed-off-by: Xiangyu Chen
---
https://github.com/python/typing_extensions/blob/main/CHANGELOG.md#release-440-october-6-2022
Release 4.4.0 (October 6, 2022)
* Add typing_extensions.Any a backport of python 3.11's Any class
which is subclassable at runtime. (backport from python/cpython#31841,
by Shantanu and Jelle
https://www.sphinx-doc.org/en/master/changes.html#release-5-3-0-released-oct-16-2022
Release 5.3.0 (released Oct 16, 2022)
* #10759: LaTeX: add latex_table_style and support the 'booktabs',
'borderless', and 'colorrows' styles. (thanks to Stefan
Wiehler for initial pull
From: Teoh Jay Shen
Include fixes for CVE-2022-3352.
Signed-off-by: Teoh Jay Shen
Signed-off-by: Luca Ceresoli
(cherry picked from commit 8aa707f80ae1cfe89d5e20ec1f1632a65149aed4)
Signed-off-by: Steve Sakoman
---
meta/recipes-support/vim/vim.inc | 4 ++--
1 file changed, 2 insertions(+), 2
From: Ross Burton
Overview of changes in 1.50.10, 16-09-2022
=
- Avoid some unnecessary strdups
- Fix line height computations with a non-trivial CTM
Signed-off-by: Ross Burton
Signed-off-by: Luca Ceresoli
(cherry picked from commit
From: wangmy
disable-hardcoded-configs.patch
refreshed for new version
Changelo:
=
- Made it possible again to have FAT32 filesystems with less
than 0xfff5 clusters
- Make FAT32 entries 0 and 1 match what windows 10 does
- Misc source code and configure script cleanup
Signed-off-by:
1 - 100 of 197 matches
Mail list logo
