From mboxrd@z Thu Jan  1 00:00:00 1970
Subject: Re: [meta][dunfell][PATCH] rpm: Handle proper return value to avoid major issues and removing unnecessary code
To: openembedded-core@lists.openembedded.org
From: "Minjae Kim" <flowergom@gmail.com>
X-Originating-Location: Seoul, KR (27.122.242.71)
X-Originating-Platform: Linux Chrome 78
User-Agent: GROUPS.IO Web Poster
MIME-Version: 1.0
Date: Mon, 13 Sep 2021 17:15:34 -0700
References: <CAOSpxdann93H+W0bcErYBFY5yp1E4Wr9R6DZdmGnmX4z_miLYQ@mail.gmail.com>
In-Reply-To: <CAOSpxdann93H+W0bcErYBFY5yp1E4Wr9R6DZdmGnmX4z_miLYQ@mail.gmail.com>
Message-ID: <25324.1631578534602076315@lists.openembedded.org>
Content-Type: multipart/alternative; boundary="hyp5DUFr7aFi3wQUzbBa"

--hyp5DUFr7aFi3wQUzbBa
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Mon, Sep 13, 2021 at 11:34 AM, Steve Sakoman wrote:

>=20
> 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 used.
I left it with the author`s intent. If the build goes well without those va=
riables, it doesn't seem to matter.

Thanks,
Minjae Kim.

--hyp5DUFr7aFi3wQUzbBa
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Mon, Sep 13, 2021 at 11:34 AM, Steve Sakoman wrote:<br />
<blockquote>RPMSIGTAG_FILESIGNATURELENGTH</blockquote>
Hi, Steve and&nbsp;<span style=3D"white-space: pre-wrap;">Ranjitsinh,</span=
><br />Sorry for the late response.<br /><span>I know that the RPMSIGTAG_FI=
LESIGNATURES and RPMSIGTAG_FILESIGNATURELENGTH are defined in the original =
commit, but are not used.<br />I left it with the author`s intent. If the b=
uild goes well without those variables, it doesn't seem to matter.<br /><br=
 />Thanks,<br />Minjae Kim.</span>

--hyp5DUFr7aFi3wQUzbBa--