From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Files not getting into the debug packages
Date: Wed, 04 Jul 2012 13:58:09 +0100 [thread overview]
Message-ID: <1341406689.3906.15.camel@ted> (raw)
In-Reply-To: <CAJ2CSBv9amOtH=LdU+37ZoNo0LB0B6uJ-=osARD0d_Chuppu9Q@mail.gmail.com>
On Wed, 2012-07-04 at 15:19 +0300, Damian, Alexandru wrote:
> Hi guys,
>
> I'm trying to run a udev package upgrade (See attached patch).
>
> I get this error,
>
> ERROR: QA Issue: non debug package contains .debug directory: udev
> path /work/i586-poky-linux/udev-182-r0/packages-split/udev/lib/udev/udev/.debug/v4l_id
> ERROR: QA Issue: non debug package contains .debug directory: udev
> path /work/i586-poky-linux/udev-182-r0/packages-split/udev/lib/udev/udev/.debug/cdrom_id
> ERROR: QA Issue: non debug package contains .debug directory: udev
> path /work/i586-poky-linux/udev-182-r0/packages-split/udev/lib/udev/udev/.debug/mtd_probe
> ERROR: QA Issue: non debug package contains .debug directory: udev
> path /work/i586-poky-linux/udev-182-r0/packages-split/udev/lib/udev/udev/.debug/accelerometer
> ERROR: QA Issue: non debug package contains .debug directory: udev
> path /work/i586-poky-linux/udev-182-r0/packages-split/udev/lib/udev/udev/.debug/scsi_id
> ERROR: QA Issue: non debug package contains .debug directory: udev
> path /work/i586-poky-linux/udev-182-r0/packages-split/udev/lib/udev/udev/.debug/udevd
> ERROR: QA Issue: non debug package contains .debug directory: udev
> path /work/i586-poky-linux/udev-182-r0/packages-split/udev/lib/udev/udev/.debug/keymap
> ERROR: QA Issue: non debug package contains .debug directory: udev
> path /work/i586-poky-linux/udev-182-r0/packages-split/udev/lib/udev/udev/.debug/collect
> ERROR: QA Issue: non debug package contains .debug directory: udev
> path /work/i586-poky-linux/udev-182-r0/packages-split/udev/lib/udev/udev/.debug/ata_id
> ERROR: QA run found fatal errors. Please consider fixing them.
>
>
> although I added the files to the debug package (I think)
>
> FILES_${PN}-dbg += "${libexecdir}/.debug"
> +FILES_${PN}-dbg += "${libexecdir}/udev/udev/.debug/"
> +FILES_${PN}-dbg += "${libexecdir}/udev/udev/.debug/*"
> FILES_${PN}-dev = "${datadir}/pkgconfig/udev.pc"
>
> Can somebody please point out what I'm doing wrong ?
The path in question is:
/lib/udev/udev/
and libexecdir is /usr/libexec/ so
${libexecdir}/udev/udev/.debug/
expands to the wrong thing. You probably want ${base_libdir}/udev/udev/.
The double udev there does look a little odd...
Cheers,
Richard
prev parent reply other threads:[~2012-07-04 13:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-04 12:19 Files not getting into the debug packages Damian, Alexandru
2012-07-04 12:56 ` Damian, Alexandru
2012-07-04 12:58 ` Richard Purdie [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=1341406689.3906.15.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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