Alexander Kanavin
> via lists.openembedded.org
> *Sent:* Wednesday, September 15, 2021 8:36 PM
> *To:* Steve Sakoman
> *Cc:* Ranjitsinh Rathod ; Patches and
> discussions about the oe-core layer <
> openembedded-core@lists.openembedded.org>; Ranjitsinh Rathod <
>
of Alexander Kanavin via
lists.openembedded.org
Sent: Wednesday, September 15, 2021 8:36 PM
To: Steve Sakoman
Cc: Ranjitsinh Rathod ; Patches and discussions
about the oe-core layer ; Ranjitsinh
Rathod
Subject: Re: [OE-core] [meta][dunfell][PATCH] rpm: Handle proper return value
to avoid m
At this point I have to note that I am removing the patch altogether with
the upcoming upgrade of rpm to 4.17, as I'm also switching the compression
format to zstd, and the patch is generally difficult to maintain and
rebase. If you care about xz compression, please do work with upstream to
get it
On Wed, Sep 8, 2021 at 4:02 AM Ranjitsinh Rathod
wrote:
>
> From: Ranjitsinh Rathod
>
> Change in 2 patch as below to avoid critical issues
> 1) 0001-rpm-rpmio.c-restrict-virtual-memory-usage-if-limit-s.patch
> Handled return values of getrlimit() and lzma_cputhreads() functions
> to avoid
[Edited Message Follows]
On Mon, Sep 13, 2021 at 11:34 AM, Steve Sakoman wrote:
>
> RPMSIGTAG_FILESIGNATURELENGTH
Hi, Steve and Ranjitsinh,
Sorry for the late response.
I know that the RPMSIGTAG_FILESIGNATURES and RPMSIGTAG_FILESIGNATURELENGTH are
defined in the original commit, but are not
On Mon, Sep 13, 2021 at 11:34 AM, Steve Sakoman wrote:
>
> RPMSIGTAG_FILESIGNATURELENGTH
Sorry for the late reponse.
I know that the RPMSIGTAG_FILESIGNATURES and RPMSIGTAG_FILESIGNATURELENGTH are
defined in the original commit, but are not used.
I left it with the author`s intent. If the build
On Wed, Sep 8, 2021 at 4:02 AM Ranjitsinh Rathod
wrote:
>
> From: Ranjitsinh Rathod
>
> Change in 2 patch as below to avoid critical issues
> 1) 0001-rpm-rpmio.c-restrict-virtual-memory-usage-if-limit-s.patch
> Handled return values of getrlimit() and lzma_cputhreads() functions
> to avoid
Can someone please check this and confirm if this can go on dunfell?
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#155984):
https://lists.openembedded.org/g/openembedded-core/message/155984
Mute This Topic:
From: Ranjitsinh Rathod
Change in 2 patch as below to avoid critical issues
1) 0001-rpm-rpmio.c-restrict-virtual-memory-usage-if-limit-s.patch
Handled return values of getrlimit() and lzma_cputhreads() functions
to avoid unexpected behaviours like devide by zero and potential read
of
