PaxHeader.folder

[Michael Hart]

I would agree with you that would be most expedient thing to do.

Just wanted to add that David Faure, faure at kde.org, the creator of KTar had
to say to me

*"I made KTar parse (and ignore) Pax headers (*), but I strongly doubt that*
*KArchive (KTar) is actually creating Pax headers, it has no code for that.*
*
*
*(*) see bug 309463, commit fff2a02946cde51702ba77c51b03e2ff1d57810f in
kdelibs.*
*
*
*These headers are created by GNU tar, aren't they? "*


Anyway I happen to have the latest version of tar, version 1.26 and I can't
directly create PaxHeaders.number by using it.

Can anyone point me to the code in kdevelop 4.x.y that actually uses
KArchive/KTar to discover if there is more than KArchive being used to open
and parse the templates, old version of cpio, pax and gtar etc will produce
PaxHeaders.number

There are just one too many KDE application having this issue on a whole
when I check Google

Thanks

On Fri, Jan 4, 2013 at 3:00 PM, Andreas Pakulat <apaku at gmx.de> wrote:

> Hi,
>
> On Fri, Jan 4, 2013 at 7:31 PM, Michael Hart
> <michael.george.hart at gmail.com> wrote:
> > I will look to see if I can discover what is causing KArchive to produce
> > PaxHeaders.number and offer a fix at the OS level, but I think that this
> > kdevelop 4 needs to correctly address the issue what it the proper way to
> > handle a PaxHeaders.number generation
>
> The fix is to get whatever KArchive uses to not generate the headers
> in the first place. Thats the only thing that needs fixing, adding
> workarounds for this problem in all apps that use KArchive is just
> silly and won't happen anyway.
>
> Andreas
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20130104/ae1ac083/attachment-0001.html>