[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 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 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