All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Wolber <chuckwolber@gmail.com>
To: Rudolf J Streif <rudolf.streif@ibeeto.com>
Cc: Alexander Kanavin <alex.kanavin@gmail.com>,
	Yocto <yocto@lists.yoctoproject.org>
Subject: Re: [yocto] Force binary package install
Date: Tue, 7 Jun 2022 16:36:05 -0700	[thread overview]
Message-ID: <CAB=6tBThBW4mZbVWpOZoYC-onO0TX=xDhv6k6zg_2Z2jUuhhzw@mail.gmail.com> (raw)
In-Reply-To: <9bd2408c-3309-11e6-2bba-37f69d90e4e2@ibeeto.com>

[-- Attachment #1: Type: text/plain, Size: 1526 bytes --]

> >> 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
>>
>
Could this be considered a bug in the package_rpm.bbclass? It seems to me
that if you skip files-rdeps,
we might not want to be adding anything into splitpreinst. Otherwise it
seems silly to tell insane.bbclass
to skip something that RPM is going to ding you on later anyway. Or maybe I
am confused...

In any case, I believe what you may be seeing can be viewed as an RPM-ism,
and not necessarily a
yocto-ism per se. So you might consider trying one of the following to work
around the problem:

Experiment with using a virtual provider. It may be possible to just map
the dependency manually to
what is already there.

If you _know_ that your dependency is truly isolated to your recipe, you
may be able to set RPROVIDES
values in your recipe so the resulting RPM thinks the dependencies are met
internally.

Patch package_rpm.bbclass to add a guard variable around the setting of
splitpreinst. Add that
guard variable to your recipe so it selectively turns off the pre-install
checks for that particular package.
Or just check for files-rdeps in INSANE_SKIP and do the same thing...

Stop fighting RPM and switch to a different package type like IPK.

..Ch:W..

-- 
*"Perfection must be reached by degrees; she requires the slow hand of
time." - Voltaire*

[-- Attachment #2: Type: text/html, Size: 2566 bytes --]

  reply	other threads:[~2022-06-07 23:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-07 18:59 Force binary package install Rudolf J Streif
2022-06-07 19:44 ` [yocto] " 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 [this message]
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='CAB=6tBThBW4mZbVWpOZoYC-onO0TX=xDhv6k6zg_2Z2jUuhhzw@mail.gmail.com' \
    --to=chuckwolber@gmail.com \
    --cc=alex.kanavin@gmail.com \
    --cc=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.