public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Urade, Yogita" <yogita.urade@windriver.com>
To: Steve Sakoman <steve@sakoman.com>,
	Randy MacLeod <randy.macleod@windriver.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: Patchtest results for [OE-core][kirkstone][PATCH 1/1] tiff: fix CVE-2023-6228
Date: Fri, 19 Jan 2024 15:15:01 +0530	[thread overview]
Message-ID: <612e18ed-e1c1-4c8e-8d09-b8f49dea8795@windriver.com> (raw)
In-Reply-To: <CAOSpxdaY1Cu0esFRFvF5Y9z53MbXGy33Hgp77ZrR+uWzU_34pQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 5557 bytes --]

Hi Steve,

I will send v2.

../Yogita

On 19-01-2024 03:56, Steve Sakoman wrote:
> **
> *CAUTION: This email comes from a non Wind River email account!*
> Do not click links or open attachments unless you recognize the sender 
> and know the content is safe.
>
>
> On Thu, Jan 18, 2024 at 12:21 PM Randy MacLeod 
> <randy.macleod@windriver.com> wrote:
>
>     Yogita,
>
>     Pleae tell people if you will send a v2 or if you plan to fix the
>     warning in a follow-up commit.
>
>     I don't see your commit in Steve's kirkstone-nut repo so I think
>     he's expecting a v2.
>
>     https://git.openembedded.org/openembedded-core-contrib/log/?h=stable/kirkstone-nut
>     <https://urldefense.com/v3/__https://git.openembedded.org/openembedded-core-contrib/log/?h=stable*kirkstone-nut__;Lw!!AjveYdw8EvQ!YU0jUlESROyvIHz4FVZrOrilRo-Y5kO1NUfhHnoIBHX50tcIqgkBVcKXqaSdFMkZrr5_0JCJCKv7BOX6c9s$>\
>
>
> I was expecting a response as to which approach would be taken.  When 
> there was no response I removed the patch under the theory that it is 
> better not to merge a half right CVE fix.
>
> Steve
>
>
>     -------- Forwarded Message --------
>     Subject: 	Patchtest results for [OE-core][kirkstone][PATCH 1/1]
>     tiff: fix CVE-2023-6228
>     Date: 	Thu, 18 Jan 2024 11:03:04 +0000
>     From: 	Patchtest via lists.openembedded.org
>     <https://urldefense.com/v3/__http://lists.openembedded.org__;!!AjveYdw8EvQ!YU0jUlESROyvIHz4FVZrOrilRo-Y5kO1NUfhHnoIBHX50tcIqgkBVcKXqaSdFMkZrr5_0JCJCKv7tnqDBQM$>
>     <patchtest=automation.yoctoproject.org@lists.openembedded.org>
>     <mailto:patchtest=automation.yoctoproject.org@lists.openembedded.org>
>     Reply-To: 	patchtest@automation.yoctoproject.org
>     To: 	yurade <yogita.urade@windriver.com>
>     <mailto:yogita.urade@windriver.com>
>     CC: 	openembedded-core@lists.openembedded.org
>
>
>
>     Thank you for your submission. Patchtest identified one
>     or more issues with the patch. Please see the log below for
>     more information:
>
>     ---
>     Testing patch
>     /home/patchtest/share/mboxes/kirkstone-1-1-tiff-fix-CVE-2023-6228.patch
>
>     FAIL: test CVE check ignore: CVE_CHECK_IGNORE is deprecated and
>     should be replaced by CVE_STATUS
>     (test_metadata.TestMetadata.test_cve_check_ignore)
>
>     PASS: pretest src uri left files
>     (test_metadata.TestMetadata.pretest_src_uri_left_files)
>     PASS: test CVE tag format (test_patch.TestPatch.test_cve_tag_format)
>     PASS: test Signed-off-by presence
>     (test_mbox.TestMbox.test_signed_off_by_presence)
>     PASS: test Signed-off-by presence
>     (test_patch.TestPatch.test_signed_off_by_presence)
>     PASS: test Upstream-Status presence
>     (test_patch.TestPatch.test_upstream_status_presence_format)
>     PASS: test author valid (test_mbox.TestMbox.test_author_valid)
>     PASS: test commit message presence
>     (test_mbox.TestMbox.test_commit_message_presence)
>     PASS: test lic files chksum modified not mentioned
>     (test_metadata.TestMetadata.test_lic_files_chksum_modified_not_mentioned)
>     PASS: test max line length
>     (test_metadata.TestMetadata.test_max_line_length)
>     PASS: test mbox format (test_mbox.TestMbox.test_mbox_format)
>     PASS: test non-AUH upgrade (test_mbox.TestMbox.test_non_auh_upgrade)
>     PASS: test shortlog format (test_mbox.TestMbox.test_shortlog_format)
>     PASS: test shortlog length (test_mbox.TestMbox.test_shortlog_length)
>     PASS: test src uri left files
>     (test_metadata.TestMetadata.test_src_uri_left_files)
>
>     SKIP: pretest pylint: No python related patches, skipping test
>     (test_python_pylint.PyLint.pretest_pylint)
>     SKIP: test bugzilla entry format: No bug ID found
>     (test_mbox.TestMbox.test_bugzilla_entry_format)
>     SKIP: test lic files chksum presence: No added recipes, skipping
>     test (test_metadata.TestMetadata.test_lic_files_chksum_presence)
>     SKIP: test license presence: No added recipes, skipping test
>     (test_metadata.TestMetadata.test_license_presence)
>     SKIP: test pylint: No python related patches, skipping test
>     (test_python_pylint.PyLint.test_pylint)
>     SKIP: test series merge on head: Merge test is disabled for now
>     (test_mbox.TestMbox.test_series_merge_on_head)
>     SKIP: test summary presence: No added recipes, skipping test
>     (test_metadata.TestMetadata.test_summary_presence)
>     SKIP: test target mailing list: Series merged, no reason to check
>     other mailing lists (test_mbox.TestMbox.test_target_mailing_list)
>
>     ---
>
>     Please address the issues identified and
>     submit a new revision of the patch, or alternatively, reply to this
>     email with an explanation of why the patch should be accepted. If you
>     believe these results are due to an error in patchtest, please
>     submit a
>     bug at https://bugzilla.yoctoproject.org/
>     <https://urldefense.com/v3/__https://bugzilla.yoctoproject.org/__;!!AjveYdw8EvQ!YU0jUlESROyvIHz4FVZrOrilRo-Y5kO1NUfhHnoIBHX50tcIqgkBVcKXqaSdFMkZrr5_0JCJCKv7cTLpTjc$>
>     (use the 'Patchtest' category
>     under 'Yocto Project Subprojects'). For more information on specific
>     failures, see: https://wiki.yoctoproject.org/wiki/Patchtest
>     <https://urldefense.com/v3/__https://wiki.yoctoproject.org/wiki/Patchtest__;!!AjveYdw8EvQ!YU0jUlESROyvIHz4FVZrOrilRo-Y5kO1NUfhHnoIBHX50tcIqgkBVcKXqaSdFMkZrr5_0JCJCKv7xETUYNk$>.
>     Thank
>     you!
>

[-- Attachment #2: Type: text/html, Size: 10123 bytes --]

      reply	other threads:[~2024-01-19  9:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-18 11:03 Patchtest results for [OE-core][kirkstone][PATCH 1/1] tiff: fix CVE-2023-6228 patchtest
2024-01-18 22:21 ` Fwd: " Randy MacLeod
2024-01-18 22:26   ` Steve Sakoman
2024-01-19  9:45     ` Urade, Yogita [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=612e18ed-e1c1-4c8e-8d09-b8f49dea8795@windriver.com \
    --to=yogita.urade@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=randy.macleod@windriver.com \
    --cc=steve@sakoman.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox