Re: [yocto] unmodified binary RPM installed on rootfs?

2017-05-23 Thread Alexander Kanavin 

On 05/23/2017 03:16 AM, Russell Peterson wrote:


Of course, I decided to go for the gold and attempt to get this
recipe to handle a binary .tgz file that contains itself multiple rpm
files (one is binary, the other is a source rpm for the kernel
modules).  I added a do_unpack_extra function to do an rpm2cpio |
cpio operation on the binary rpm… and now see cpio malformed errors.
My guess is the rpm uses compression… but shouldn’t the rpm2cpio
handle that??


Does the same thing work on your host machine (using host's rpm2cpio)?

We have switched from rpm 5 to rpm4 recently, so you might be hit by the 
transition - can you try the same thing with pyro release, or master?


Also, can you copy-paste the recipe?

Alex
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] unmodified binary RPM installed on rootfs?

2017-05-22 Thread Alexander Kanavin 

On 05/22/2017 02:43 AM, Russell Peterson wrote:

I am fairly new to yocto and I think I’m having trouble installing an
RPM on the rootfs. What I am trying to do is install an arm64 binary RPM
file straight onto the root file system without a recipe… just use the
native rpm tool to put it there.  There are several reasons why I’m
experimenting with this.  Seems fairly simple but I have now been
messing around for days with little to show for it.  Here is what I’m doing…


Yocto does not currently support installing 3rd party RPMs. Even if it 
would install, whatever contents it has would very likely not work due 
to mismatches between the environment where the rpm was built and the 
environment where you are installing it. And --nodeps would only make 
the problem worse.


You have to write a recipe.


Alex

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] unmodified binary RPM installed on rootfs?

2017-05-21 Thread Russell Peterson 
Hello,

I am fairly new to yocto and I think I’m having trouble installing an RPM on 
the rootfs. What I am trying to do is install an arm64 binary RPM file straight 
onto the root file system without a recipe… just use the native rpm tool to put 
it there.  There are several reasons why I’m experimenting with this.  Seems 
fairly simple but I have now been messing around for days with little to show 
for it.  Here is what I’m doing…

Added to the image bb file:



ROOTFS_POSTPROCESS_COMMAND += "install_mtt ; "
 
IMAGE_LINGUAS ?= "en-US”  <— Wondered if this was a UTF-8 issue
 
fakeroot install_mft () {
   ${STAGING_BINDIR_NATIVE}/rpm -i --nodeps --root=${IMAGE_ROOTFS}/ 
/mtt-4.7.0-21-arm64-rpm/RPMS/mtt-4.7.0-21.arm64.rpm
}
 
———

This is the error I see.   
 
DEBUG: Executing shell function install_mft
error: unpacking of archive failed: cpio: Bad magic
WARNING: 
/yocto-00dc025f/work/mymach-poky-linux/core-image-full/1.0-r0/temp/run.install_mtt.2846:1
 exit 1 from '/yocto-00dc025f/sysroots/x86_64-linux/usr/bin/rpm -i ---nodeps 
--root=/yocto-00dc025f/work/mymach-poky-linux/core-image-full/1.0-r0/rootfs/ 
/mtt-4.7.0-21-arm64-rpm/RPMS/mtt-4.7.0-21.arm64.rpm’

Seems like this should work.  I have no idea what magic number the file command 
doesn’t like.  I looked through the files and they all look legit.  Maybe this 
is an RPM version issue?  I think the original RPM was created with 4.8 and the 
poky version I’m using is 5.3?


-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto