All, It isn't clear if the following is a bug, but it's a real question. Besides, this was the only cpio-related mailing list that I could find.
I'm writing an emacs application to handle cpio(1) archives. It is intended, in part, to work like tar-mode and dired. However, with some archives (and some entries within those archives, it looks to me like the *filesize* field is too large by one byte. The archives still unpack properly, but manual checking of the *filesize* field reflects that bug for those entries. I think I've reflected the GNU cpio(1) code correctly. I'd like to know if I've stumbled across something known (and therefore also what that is) or if it's a new bug. Here's the information on what I'm using to debug this: - OS: Linux Mint 18 (I believe). - Kernel: 4.4.0-21-generic #37-Ubuntu SMP - emacs: 24.5 - GNU cpio: 2.11 If you care, a copy of the current source is attached. It will also be posted to the emacs developers' mailing list. Thanks. -- ,Doug Douglas Lewan (908) 720-7908 What one programmer can do in one month, two programmers can do in two months. -- Fred Brooks
cpio-mode-0.01-20171218121614.tar.gz
Description: GNU Zip compressed data
