[bug #15758] Uncompressing .tar.bz2 leads to malformed filename extension eventually

2006-02-16 Thread Pavel Tsekov
Update of bug #15758 (project mc): Category:Core = VFS Status:None = Need Info ___ Follow-up Comment #5: J.J., I've followed

[bug #15758] Uncompressing .tar.bz2 leads to malformed filename extension eventually

2006-02-16 Thread Pavel Tsekov
Follow-up Comment #6, bug #15758 (project mc): mc-4.6.1-0.8.1 is based on MC CVS from October 20, 2004. By that time the tar code was modified several times to properly deal with filenames starting with `./' (without the quotes). The code used in mc-4.6.1-0.8.1 contains only the first of these

[bug #15758] Uncompressing .tar.bz2 leads to malformed filename extension eventually

2006-02-16 Thread J.J. Garcia
Follow-up Comment #7, bug #15758 (project mc): Strange thing because i can reproduce it every time. Having that you tryied with the same package from rh that i, the only point i think is the contents of the tarbar compressed file to reproduce the bug. Another info is that it's not a tar.bz2

[bug #15758] Uncompressing .tar.bz2 leads to malformed filename extension eventually

2006-02-16 Thread J.J. Garcia
Follow-up Comment #8, bug #15758 (project mc): More info by the way you can check (long path strings involved): a) dont know if it is important but using for hdparm the following confing in /etc/sysconfig/harddisks USE_DMA=1 MULTIPLE_IO=16 EIDE_32BIT=3 LOOKAHEAD=1 EXTRA_PARAMS= b) The tar.bz2

[bug #15758] Uncompressing .tar.bz2 leads to malformed filename extension eventually

2006-02-16 Thread Pavel Tsekov
Update of bug #15758 (project mc): Status: Need Info = Duplicate ___ Follow-up Comment #9: Now this is a different story... The filename

[bug #15758] Uncompressing .tar.bz2 leads to malformed filename extension eventually

2006-02-16 Thread Pavel Tsekov
Update of bug #15758 (project mc): Open/Closed:Open = Closed ___ Follow-up Comment #10: Closing as duplicate of bug #13536. ___

[bug #15758] Uncompressing .tar.bz2 leads to malformed filename extension eventually

2006-02-16 Thread J.J. Garcia
Follow-up Comment #11, bug #15758 (project mc): Ok Pavel, Thx 4 the info, i'll feedback the info to CentOs packager to include the fix Cheers, Jose ___ Reply to this item at:

[bug #15758] Uncompressing .tar.bz2 leads to malformed filename extension eventually

2006-02-15 Thread J.J. Garcia
URL: http://savannah.gnu.org/bugs/?func=detailitemitem_id=15758 Summary: Uncompressing .tar.bz2 leads to malformed filename extension eventually Project: GNU Midnight Commander Submitted by: sm0ketst Submitted on: Wed 02/15/06 at 19:15

[bug #15758] Uncompressing .tar.bz2 leads to malformed filename extension eventually

2006-02-15 Thread Pavel Tsekov
Follow-up Comment #1, bug #15758 (project mc): Where did you get that file from ? At newlib's homepage I can only see .tar.gz files ? I've downloaded newlib-1.12.0.tar.gz and tried to reproduce but the file ip_mroute.h extracted just fine. I didn't bother to try with the second file. I pressed

[bug #15758] Uncompressing .tar.bz2 leads to malformed filename extension eventually

2006-02-15 Thread J.J. Garcia
Follow-up Comment #2, bug #15758 (project mc): It's a tar.bz2 i did by using the same source as you and using the command: $ tar cvjf ./newlib-1.12.0.tar.bz2 ./newlib-1.12.0 I've patched this sources and packaged in a new tar.bz2 file, that's all. Don't know if you rebuilded it to a tar.bz2 or

[bug #15758] Uncompressing .tar.bz2 leads to malformed filename extension eventually

2006-02-15 Thread Leonard den Ottolander
Follow-up Comment #3, bug #15758 (project mc): This looks very much like an issue for which I committed a fix 7 months ago where files with names of NAMSIZ were truncated one char. NAMSIZ = 100, and in this case the affected file names are both 50 chars. Exactly half that length. Odd. Try if

[bug #15758] Uncompressing .tar.bz2 leads to malformed filename extension eventually

2006-02-15 Thread Pavel Tsekov
Follow-up Comment #4, bug #15758 (project mc): Leonard, this thought crossed my mind as soon as I noticed this bugreport but that fix was for filenames of length 100 so it I guess it must be something else. I'll try to follow J.J's instructions to create a tar.bz2 file off the original tar.gz