dskvr / opkg

Automatically exported from code.google.com/p/opkg
0 stars 0 forks source link

opkg failed to extract data files with packages created with dpkg-1.17.5 #151

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1.Create debian package (keeping control and data files) with dpkg version 
1.17.5 
2.then try to download the packages on to board using opkg-cl(0.1.8) --download 
option
3.Opkg successfully download the control file and failed to download the data 
file (data.tar.gz)
4. If I create a debian package with same control and data files using dpkg 
-1.16.1.2 and everything works as expected. 

What is the expected output? What do you see instead?
DPKG-1.16.1.2 (i386) --> always works (opkg successfully downloads all files)
DPKG-1.17.5 (amd64) --> failed to download data.tar.gz(opkg successfully 
downloads control.tar.gz and not the data.tar.gz)
OPKG-0.1.8 should download all files (control.tar.gz and data.tar.gz) but it 
downloads control file and not the data.tar.gz. OPKG not even print any error.

What version of the product are you using? On what operating system?
OPKG-0.1.8
DEVICE - TI - beagle bone - AM335x board
Arc- armv7l

Please provide any additional information below.
My config file

#custom https URL

dest ram /tmp
lists_dir ext /tmp/var/lib/opkg/
arch all 100
arch armv7l 200
arch armel 300

Original issue reported on code.google.com by balu.sab...@gmail.com on 10 Nov 2014 at 3:54

GoogleCodeExporter commented 8 years ago
A more recent version of opkg should print a better error message. Otherwise, 
this is just the fact that dpkg now uses .tar.xz rather than .tar.gz for the 
data archive member, which is discussed in issue 148.

Original comment by paul.betafive on 10 Nov 2014 at 4:06

GoogleCodeExporter commented 8 years ago
Dear  paul.betafive,

Thanks for your immediate reply and I appreciate your answer.
I also just found out the same error,
while debugging opkg module, found error in function deb_extract() in 
unarchive.c file and which explains the issue of latest dpkg uses .tar.xz 
rather than .tar.gz.

I am really sorry for a duplicate defect and I didn't see the details of issue 
148, in fact I wasn't knowing the exact problem at that time. 

Could you suggest best option to fix this issue with opkg-0.1.8 version?
We have few constraints like,
1) we are not allowed to increase the opkg version
2) we are allowed to upgrade/downgrade the dpkg version
or 
could we create a patch for opkg-0.1.8 to fix this issue?

Original comment by balu.sab...@gmail.com on 10 Nov 2014 at 4:21

GoogleCodeExporter commented 8 years ago
Look at the options used to create the package using dpkg. There should be a 
way to control the compression format used. A quick bit of googling lead to 
http://askubuntu.com/questions/396088/build-data-tar-gz-instead-of-data-tar-xz-i
nside-deb which may be of use.

Other than that I'm afraid you're on your own. opkg can't promise to support 
whatever changes dpkg decides to make as they may be inappropriate for embedded 
systems.

Original comment by paul.betafive on 10 Nov 2014 at 4:27

GoogleCodeExporter commented 8 years ago
Thanks again for your help:-)

I tried to create a package with dpkg-deb -Zgzip -b package_name 
package_name.deb and it worked fine:-)

So this option will make sure control and data archive in .tar.gz format.

This method would be workaround for this problem. 

Original comment by balu.sab...@gmail.com on 10 Nov 2014 at 6:28