From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] multipath-tools: update to 0.6.4
Date: Mon, 30 Jan 2017 13:18:05 +0100 [thread overview]
Message-ID: <20170130121805.GA13746@jama> (raw)
In-Reply-To: <20170127101200.25785-1-patrick.ohly@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1054 bytes --]
On Fri, Jan 27, 2017 at 11:11:23AM +0100, Patrick Ohly wrote:
> No particular reason for updating besides following upstream.
>
> Only kpartx has been tested after updating! Seems to work as before;
> unfortunately that means that as in 0.5.0, "kpartx -d" doesn't do
> anything.
>
> Upstream refreshed the COPYING file, hence the checksum change:
> $ git log --oneline 0.5.0..HEAD COPYING
> bf05f63 multipath-tools: replace COPYING with a fresh copy from gnu.org
> 1d6c88a Update FSF address
>
> The QA error that do-not-link-libmpathpersist-to-TMPDIR.patch fixes
> no longer occurs because upstream changed that particular part of
> the Makefile.
>
> A new patch is needed to avoid building libcheckerrdb, which depends
> on the (currently) unavailable librados.
FWIW: it would be even better if you mark
https://patchwork.openembedded.org/patch/136518/
as Superseded as patchwork is where I take patches for master-next and I
need to remember that there was e-mail reply for this one that it should
be ignored.
Thanks
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]
next prev parent reply other threads:[~2017-01-30 12:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-27 10:11 [PATCH] multipath-tools: update to 0.6.4 Patrick Ohly
2017-01-27 10:44 ` Patrick Ohly
2017-01-30 12:18 ` Martin Jansa [this message]
2017-01-30 13:29 ` Patrick Ohly
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=20170130121805.GA13746@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox