Bug#291194: dpkg should handle tar posix format
Adam D. Barratt, le mer 19 jan 2005 14:22:48 -0000, a dit :
> On Wednesday, January 19, 2005 1:38 PM, Samuel Thibault
> <samuel.thibault@ens-lyon.org> wrote:
>
> > Scott James Remnant, le mer 19 jan 2005 11:35:51 +0000, a dit :
> >> On Wed, 2005-01-19 at 12:02 +0100, Samuel Thibault wrote:
> >>
> >>> So as to have proper file name encoding, I'm used to have
> >>> TAR_OPTIONS=--format=posix
> >>> But then built packages don't work:
> >>>
> >> I think this is a dup of the above bug. If that patch doesn't work,
> >> please unmerge these bugs.
> >
> > It doesn't. Doing some gdb showed me that the first tar entry has
> > h.Type 'x', which is unknown. Here is the printing of the first
> > header: (gdb) p *(TarHeader *)block
> > $10 = {Name = "./PaxHeaders.28427/.", '\0' <repeats 79 times>,
>
> GNU tar indeed does not understand `x' (or any other lower-case letter) as a
> valid file type.
Indeed, that seems to be a posix type that testing and unstable tars
produce. Dpkg should be prepared to handle that some day.
Regards,
Samuel
Reply to: