From: Martin Jansa <martin.jansa@gmail.com>
To: Paul Barker <paul@paulbarker.me.uk>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: Clashing man pages
Date: Sun, 19 May 2013 14:54:51 +0200 [thread overview]
Message-ID: <20130519125451.GH3196@jama> (raw)
In-Reply-To: <CANyK_8eXDE0PFgtzrBdXw3=eXrn5H_hdZ6ivVj4+TRQbnC1+eg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2676 bytes --]
On Sun, May 19, 2013 at 01:00:24PM +0100, Paul Barker wrote:
> I'm generating a rootfs image which I intend to be usable
> interactively so I've added IMAGE_FEATURES += "doc-pkgs" to my image
> recipe. do_rootfs fails with the following clashes:
>
> | * check_data_file_clashes: Package ncurses-doc wants to install
> file /home/pbarker/build/20130518_wych/build/tmp/work/qemuarm-wych-linux-gnueabi/wych-image-full/1.0-r0/rootfs/usr/share/man/man1/reset.1
> | But that file is already provided by package * util-linux-doc
> | * opkg_install_cmd: Cannot install package ncurses-doc.
> | * check_data_file_clashes: Package coreutils-doc wants to install
> file /home/pbarker/build/20130518_wych/build/tmp/work/qemuarm-wych-linux-gnueabi/wych-image-full/1.0-r0/rootfs/usr/share/man/man1/kill.1
> | But that file is already provided by package * util-linux-doc
> | * opkg_install_cmd: Cannot install package coreutils-doc.
> | * check_data_file_clashes: Package shadow-doc wants to install file
> /home/pbarker/build/20130518_wych/build/tmp/work/qemuarm-wych-linux-gnueabi/wych-image-full/1.0-r0/rootfs/usr/share/man/man5/passwd.5
> | But that file is already provided by package * man-pages
> | * check_data_file_clashes: Package shadow-doc wants to install file
> /home/pbarker/build/20130518_wych/build/tmp/work/qemuarm-wych-linux-gnueabi/wych-image-full/1.0-r0/rootfs/usr/share/man/man3/getspnam.3
> | But that file is already provided by package * man-pages
> | * opkg_install_cmd: Cannot install package shadow-doc.
>
> I've explicitly said I want coreutils and man-pages, the rest is being
> pulled in implicitly as dependencies of something. There's nothing in
> qa.log or the bitbake output to suggest that installed files are
> clashing so I'm not sure if this could have been reported earlier.
>
> The best fix I can think of at the minute is to add a bbappend to my
> layer which removes the clashing man pages from one of the packages in
> each case, leaving the files just in the package I do want to take
> precedence. If anyone has any better ideas let me know.
>
> I know we have update-alternatives for executables but is there a way
> to link this with the relevant man page? So for example when I select
> kill from coreutils, kill.1 is provided by coreutils as well, when I
> select kill from util-linux, kill.1 is provided by util-linux as well.
There was some discussion about this already
http://lists.linuxtogo.org/pipermail/openembedded-core/2013-January/034744.html
but only response I got was about conflicting /usr/share/info/dir :/
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2013-05-19 13:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-19 12:00 Clashing man pages Paul Barker
2013-05-19 12:54 ` Martin Jansa [this message]
2013-05-20 9:07 ` Paul Barker
2013-05-20 16:13 ` Mark Hatle
2013-05-20 17:39 ` Khem Raj
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=20130519125451.GH3196@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul@paulbarker.me.uk \
/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.