Closed GoogleCodeExporter closed 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
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
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
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
Original issue reported on code.google.com by
balu.sab...@gmail.com
on 10 Nov 2014 at 3:54