Package: mpack Version: 1.6-8 Followup-For: Bug #497527 Control: severity 497527 important
This is still a problem with 1.6-8. Why else would you want to use munpack unless you were dealing with multipart messages? If i had to guess, i'd guess that most messages traversing the 'net today are multipart messages. I'm increasing the severity of this ticket, since half the package doesn't seem to work for the standard use case. 0 dkg@alice:/tmp$ printmimestructure < Ticket-6787.eml └┬╴multipart/alternative 21275 bytes ├─╴text/plain inline 6763 bytes └─╴text/html inline 14072 bytes 0 dkg@alice:/tmp$ munpack Ticket-6787.eml tempdesc.txt: File exists Did not find anything to unpack from Ticket-6787.eml 0 dkg@alice:/tmp$ --dkg -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing'), (200, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.7-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mpack depends on: ii libc6 2.13-37 mpack recommends no packages. Versions of packages mpack suggests: pn inews <none> ii postfix [mail-transport-agent] 2.9.3-2.1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
