All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rudolf J Streif <rudolf.streif@ibeeto.com>
To: Yocto <yocto@lists.yoctoproject.org>
Subject: Force binary package install
Date: Tue, 7 Jun 2022 11:59:38 -0700	[thread overview]
Message-ID: <22848052-7e8c-d0c4-1c42-6d71022956bd@ibeeto.com> (raw)


[-- Attachment #1.1.1: Type: text/plain, Size: 2273 bytes --]

I have been handed a binary package that I am integrating into a Yocto 
build.

When dnf runs it complains about missing dependencies. These are 
standard libraries of course but the culprit is the incompatible 
version. The software runs fine when I install it on the target using 
the script/tar installation it comes with. Needless to say that YP 
packaging QA complains about this already when assembling the package. 
However, there I can silence the complaints with INSANE_SKIP.

Unfortunately I have not found a method doing the same when the package 
is installed by the image class.

Is there an elegant way around it?


Error:
  Problem: conflicting requests
   - nothing provides libdl.so.2 needed by 
xxx-single-group-0.1-r0.cortexa53_crypto
   - nothing provides libdl.so.2(GLIBC_2.0) needed by 
xxx-single-group-0.1-r0.cortexa53_crypto
   - nothing provides libdl.so.2(GLIBC_2.1) needed by 
xxx-single-group-0.1-r0.cortexa53_crypto
   - nothing provides libgcc_s.so.1 needed by 
xxx-single-group-0.1-r0.cortexa53_crypto
   - nothing provides libgcc_s.so.1(GCC_3.0) needed by 
xxx-single-group-0.1-r0.cortexa53_crypto
   - nothing provides libm.so.6 needed by 
xxx-single-group-0.1-r0.cortexa53_crypto
   - nothing provides libm.so.6(GLIBC_2.0) needed by 
xxx-single-group-0.1-r0.cortexa53_crypto
   - nothing provides libm.so.6(GLIBC_2.1) needed by 
xxx-single-group-0.1-r0.cortexa53_crypto
   - nothing provides libpthread.so.0 needed by 
xxx-single-group-0.1-r0.cortexa53_crypto
   - nothing provides libpthread.so.0(GLIBC_2.0) needed by 
xxx-single-group-0.1-r0.cortexa53_crypto
   - nothing provides libpthread.so.0(GLIBC_2.1) needed by 
xxx-single-group-0.1-r0.cortexa53_crypto
   - nothing provides libpthread.so.0(GLIBC_2.2) needed by 
xxx-single-group-0.1-r0.cortexa53_crypto
   - nothing provides libpthread.so.0(GLIBC_2.3.2) needed by 
xxx-single-group-0.1-r0.cortexa53_crypto
   - nothing provides librt.so.1 needed by 
xxx-single-group-0.1-r0.cortexa53_crypto
   - nothing provides librt.so.1(GLIBC_2.2) needed by 
xxx-single-group-0.1-r0.cortexa53_crypto
(try to add '--skip-broken' to skip uninstallable packages)


-- 
Rudolf J Streif
CEO/CTO ibeeto
+1.855.442.3386 x700


[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 1717 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]

             reply	other threads:[~2022-06-07 18:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-07 18:59 Rudolf J Streif [this message]
2022-06-07 19:44 ` [yocto] Force binary package install Alexander Kanavin
2022-06-07 19:57   ` Rudolf J Streif
2022-06-07 22:12     ` Alexander Kanavin
2022-06-07 22:48       ` Rudolf J Streif
2022-06-07 23:36         ` Chuck Wolber
2022-06-08  1:17           ` Rudolf J Streif
2022-06-08 15:54             ` Richard Purdie
2022-06-13 20:08               ` Rudolf J Streif
2022-06-13 21:32                 ` Richard Purdie
2022-06-14  0:09                   ` Rudolf J Streif
2022-06-08  9:59         ` Alexander Kanavin

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=22848052-7e8c-d0c4-1c42-6d71022956bd@ibeeto.com \
    --to=rudolf.streif@ibeeto.com \
    --cc=yocto@lists.yoctoproject.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 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.