[poky] Fwd: Poky build failure with "Could not invoke dnf" error message.

[AshishKumar Mishra]

Hi Richard / Khem Raj ,

Thanks for the pointer & indeed that was the problem  !!!!

Would it be possible to share any link / pointers to help me understand the
"packaging " aspect of recipe

*Predominantly , how are the package being created from the files being
copied to {D)<some-folder>*
*and what are the essential rules i need to know .*
(Like ALLOW_EMPTY_${PN} = “1” we are informing that the package can be
empty )

But i am not able to understand :-
a) Who & how are packages being created from files copied in
{D)<some-folder>
b) What are the rules (Like ALLOW_EMPTY_${PN} = “1 ) for empty package ?
c) When would we get an empty package.

Like looking for pointers i came across below link but was unable to get
clear picture .
http://lists.openembedded.org/pipermail/openembedded-core/2012-July/064040.html

Sorry for long thread but i am trying to implement things & learn yocto.

Thanks
Ashish















On Mon, Oct 14, 2019 at 3:48 PM Khem Raj <raj.khem at gmail.com> wrote:

>
>
> On Mon, Oct 14, 2019 at 11:10 AM <richard.purdie at linuxfoundation.org>
> wrote:
>
>> On Mon, 2019-10-14 at 15:24 +0530, AshishKumar Mishra wrote:
>> > Thanks for replying back Richard.
>> >
>> > I can see the RPM generated at "tmp/deploy/rpm/core2_32" .
>> >
>> > [15:14:38]:~/Documents/linux-foundation-projects/yocto/build-armour :
>> find tmp/* -name 'eth0*' | grep rpm
>> > tmp/deploy/rpm/core2_32/eth0-dev-0.1-r0.core2_32.rpm
>> > tmp/deploy/rpm/core2_32/eth0-dbg-0.1-r0.core2_32.rpm
>> >
>> tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/oe-rootfs-repo/rpm/core2_32/eth0-dev-0.1-r0.core2_32.rpm
>> >
>> tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/oe-rootfs-repo/rpm/core2_32/eth0-dbg-0.1-r0.core2_32.rpm
>> >
>> tmp/work/core2-32-poky-linux/eth0/0.1-r0/deploy-rpms/core2_32/eth0-dev-0.1-r0.core2_32.rpm
>> >
>> tmp/work/core2-32-poky-linux/eth0/0.1-r0/deploy-rpms/core2_32/eth0-dbg-0.1-r0.core2_32.rpm
>> >
>> > This is my folder skeleton & attached is the recipe
>> > ~/Documents/linux-foundation-projects/yocto/meta-mechanic/recipes-
>> > armour (master) : ls
>> > armour  eth0-0.1  images
>> > ~/Documents/linux-foundation-projects/yocto/meta-mechanic/recipes-
>> > armour (master) : ls eth0-0.1/*
>> > eth0-0.1/eth0_0.1.bb
>> >
>> > eth0-0.1/eth0-0.1:
>> > eth0.service
>> >
>> > Is there any specific dependency which i am missing or if i am doing
>> > any thing wrong here .
>>
>> In the list above I see "eth0-dev" and "eth0-dbg" but no "eth0"
>> package.
>>
>> The error is therefore correct in that no "eth0" package exists. Why, I
>> don't know but you need to look at the recipe and figure out why the
>> expected package isn't generated.
>
>
> Most probably it’s an empty package and is eventually deleted by packager
> try ALLOW_EMPTY_${PN} = “1” and of that works then you know that’s the
> problem so you need to fix the packaging to not rdepend on an empty package
>
>>
>>
>> Cheers,
>>
>> Richard
>>
>> --
>> _______________________________________________
>> poky mailing list
>> poky at yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/poky
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/poky/attachments/20191014/7b3903c3/attachment.html>