| Summary: | app-arch/ipkg-utils - ipkg-make-index is not working with tar > 1.13 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Philipp Wehrheim <flip> |
| Component: | Current packages | Assignee: | Seemant Kulleen (RETIRED) <seemant> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | jnrowe |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | ipkg-utils-tar_fixes.patch | ||
Created attachment 133274 [details, diff]
ipkg-utils-tar_fixes.patch
Patch that implements the necessary changes spotted by Philipp, for
both versions in portage. It also changes the name of the tar binary
that is called to gtar, as --wildcards is unlikely to be supported with
tar when userland_GNU is false.
Seemant, it's a definite version bump situation in my opinion as
functionality that is common for certain scenarios is broken, even if it
hasn't been spotted in the past.
Suggested changelog entry of:
Small fixes for current tar compatibility. Thanks to Philipp
Wehrheim for reporting.
Thanks,
James
Thanks James :) in cvs. Thanks Phillip, for the report. |
When ipkg-make-index is executed and tar version > 1.13 is installed it fails. This is because /usr/lib/python2.4/site-packages/ipkg.py runs tar with '*control' but does not set the "--wildcards" parameter. The wildcard parameter is not known in tar version 1.13 but since gentoo is currently using tar 1.{17,18} this should not be a big issue. To solve the problem /usr/lib/python2.4/site-packages/ipkg.py needs to be updated. from: control = os.popen("ar p "+fn+" control.tar.gz | tar xfzO - '*control'","r") to: control = os.popen("ar p "+fn+" control.tar.gz | tar xfzO - --wildcards '*control'","r") etc etc Reproducible: Always