Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Jussi Kukkonen <jussi.kukkonen@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/5] xf86-input-vmmouse: Upgrade 13.0.0 -> 13.1.0
Date: Fri, 10 Jul 2015 22:23:47 +0100	[thread overview]
Message-ID: <1436563427.3310.16.camel@linuxfoundation.org> (raw)
In-Reply-To: <5946300c9c5e9e0be705a2db59c1bd03340a629a.1436427694.git.jussi.kukkonen@intel.com>

On Thu, 2015-07-09 at 10:52 +0300, Jussi Kukkonen wrote:
> Remove backported patch.
> 
> Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com>
> -

This caused:

ERROR: QA Issue: xf86-input-vmmouse: Files/directories were installed but not shipped in any package:
  /usr/libx32/udev
  /usr/libx32/udev/rules.d
  /usr/libx32/udev/rules.d/69-xorg-vmmouse.rules
Please set FILES such that these items are packaged. Alternatively if they are unneeded, avoid installing them or delete them within do_install. [installed-vs-shipped]

https://autobuilder.yoctoproject.org/main/builders/nightly-x32/builds/385/steps/BuildImages/logs/stdio

on the nightly-x32 build. Looks like its not multilib safe. Looking at
the code, the udev directory seems to have gone from base_libdir to
libdir?

Cheers,

Richard



  reply	other threads:[~2015-07-10 21:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-09  7:51 [PATCH 0/5] Upgrades for clutter and X related recipes Jussi Kukkonen
2015-07-09  7:52 ` [PATCH 1/5] xproto: Upgrade 7.0.27 -> 7.0.28 Jussi Kukkonen
2015-07-09  7:52 ` [PATCH 2/5] xf86-input-vmmouse: Upgrade 13.0.0 -> 13.1.0 Jussi Kukkonen
2015-07-10 21:23   ` Richard Purdie [this message]
2015-07-10 22:11   ` Burton, Ross
2015-07-09  7:52 ` [PATCH 3/5] cogl-1.0: Upgrade 1.18.2 -> 1.20.0 Jussi Kukkonen
2015-07-09  7:52 ` [PATCH 4/5] clutter-1.0: Upgrade 1.20.0 -> 1.22.4 Jussi Kukkonen
2015-07-09  7:52 ` [PATCH 5/5] clutter-gtk-1.0: Upgrade 1.4.4 -> 1.6.2 Jussi Kukkonen

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=1436563427.3310.16.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=jussi.kukkonen@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox