All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Marko, Peter" <Peter.Marko@siemens.com>
To: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/5] cve-check: honor RM_OLD_IMAGE flag
Date: Mon, 5 Jun 2017 11:05:58 +0000	[thread overview]
Message-ID: <6D4566C9E07A8D4DAB6F935696920A841B84072D@ATVIES991UAMSX.ww300.siemens.net> (raw)
In-Reply-To: <1496647273-9693-2-git-send-email-peter.marko@siemens.com>

> +                if d.getVar('RM_OLD_IMAGE') == "1":
> +                    os.remove(os.path.realpath(manifest_link))

I have been working with Krogoth and ported my changes to master.
It seems this flag is no longer supported, thus this commit is wrong (or good only for backporting to Krogoth).
I'll remove it in v2 as soon as I get feedback on the other commits, too.

Peter


  reply	other threads:[~2017-06-05 11:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-05  7:21 [PATCH 0/5] cve-check improvements Peter Marko
2017-06-05  7:21 ` [PATCH 1/5] cve-check: honor RM_OLD_IMAGE flag Peter Marko
2017-06-05 11:05   ` Marko, Peter [this message]
2017-06-05  7:21 ` [PATCH 2/5] cve-check: add do_rootfs dependency on cve-check Peter Marko
2017-06-05  7:21 ` [PATCH 3/5] cve-check: do not parse error output Peter Marko
2017-06-05  7:21 ` [PATCH 4/5] cve-check: clean cve-check recipe result before re-building Peter Marko
2017-06-05  7:21 ` [PATCH 5/5] cve-check-tool: fix crash on exceptions Peter Marko
2017-06-07  6:04 ` [PATCH v2 0/4] cve-check improvements Peter Marko
2017-06-07  6:04 ` [PATCH v2 1/4] cve-check: add do_rootfs dependency on cve-check Peter Marko
2017-06-07  6:04 ` [PATCH v2 2/4] cve-check: do not parse error output Peter Marko
2017-06-07  6:04 ` [PATCH v2 3/4] cve-check: clean cve-check recipe result before re-building Peter Marko
2017-06-07  6:04 ` [PATCH v2 4/4] cve-check-tool: fix crash on exceptions Peter Marko
2017-06-07 16:03   ` Leonardo Sandoval
2017-06-07 16:20     ` Marko, Peter

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=6D4566C9E07A8D4DAB6F935696920A841B84072D@ATVIES991UAMSX.ww300.siemens.net \
    --to=peter.marko@siemens.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.