On Mon, 2017-01-30 at 13:18 +0100, Martin Jansa wrote: > 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, I'll try to remember that going forward. Would have been a nice testcase for [Patchwork-Status: Superseded] -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. -- _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-devel
