It's no tarball, it's a gzip file, as you can tell from *.gz Afaik messybox tar doesn't know how to implicitly invoke unzip
00000000 6c 69 62 70 75 6c 73 65 2d 6d 61 69 6e 6c 6f 6f |libpulse-mainloo| 00000010 70 2d 67 6c 69 62 30 5f 30 2e 39 2e 31 35 2d 31 |p-glib0_0.9.15-1| 00000020 6d 61 65 6d 6f 33 38 2b 30 6d 35 5f 61 72 6d 65 |maemo38+0m5_arme| 00000030 6c 2e 64 65 62 00 00 00 00 00 00 00 00 00 00 00 |l.deb...........| 00000040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00000050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00000060 00 00 00 00 30 30 30 30 36 34 34 00 80 00 00 00 |....0000644.....| 00000070 00 a6 f8 00 32 30 33 30 31 36 37 00 30 30 30 30 |....2030167.0000| 00000080 30 30 34 37 37 35 30 00 31 31 34 33 33 34 37 36 |0047750.11433476|
Other ExtensionsOne common extension, utilized by GNU tar, star, and other newer tar implementations, permits binary numbers in the standard numeric fields. This is flagged by setting the high bit of the first character. This permits 95-bit values for the length and time fields and 63-bit values for the uid, gid, and device numbers. GNU tar supports this extension for the length, mtime, ctime, and atime fields. Joerg Schilling's star program supports this extension for all numeric fields. Note that this extension is largely obsoleted by the extended attribute record provided by the pax interchange format.
One common extension, utilized by GNU tar, star, and other newer tar implementations, permits binary numbers in the standard numeric fields. This is flagged by setting the high bit of the first character. This permits 95-bit values for the length and time fields and 63-bit values for the uid, gid, and device numbers. GNU tar supports this extension for the length, mtime, ctime, and atime fields. Joerg Schilling's star program supports this extension for all numeric fields. Note that this extension is largely obsoleted by the extended attribute record provided by the pax interchange format.