Re: Buggy "mime-support" package? :-(
At 02:31 PM 1/6/97 -0500, Dale Scheetz wrote: >On Mon, 6 Jan 1997, Brian C. White wrote: > >> >> None of these are technically supposed to depend on mime-support. They >> should only test for its availability before calling the "install-mime" >> program. This is documented in the "install-mime" man page. >> >Well, I can only speak to the needs of the pine package. /etc/mailcap is >provided by mime-support and needed by pine. This is the reason for it's >dependence on mime-support. Install-mime is not needed or used by the pine >installation scripts, so is not the issue here. I can only assume that the >other packages mentioned have similar needs and therefore, rightly, depend >on mime-support. > Not for xanim, I'll fix it when I get the chance, but the reason I had it depend is b/c for "newbies" it will be mostly useless without it, such as if they are using netscape and they are used to having the files they download be played automatically. Shaya -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: Buggy "mime-support" package? :-( (re:)
[EMAIL PROTECTED] (Timothy Phan) writes: > While we are on the subject of mime-support, I'd like to know > if there is some command that I can run at the command line to > decode a mime'd file? munpack (1) - unpack messages in MIME or split-uuencode format in the mpack package. Guy -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: Buggy "mime-support" package? :-(
> > None of these are technically supposed to depend on mime-support. They > > should only test for its availability before calling the "install-mime" > > program. This is documented in the "install-mime" man page. > > Well, I can only speak to the needs of the pine package. /etc/mailcap is > provided by mime-support and needed by pine. This is the reason for it's > dependence on mime-support. Install-mime is not needed or used by the pine > installation scripts, so is not the issue here. I can only assume that the > other packages mentioned have similar needs and therefore, rightly, depend > on mime-support. Yes, of course. I wasn't thinking about programs using it. Brian ( [EMAIL PROTECTED] ) --- Want to get it together? We can help! http://www.verisim.com/coordinator/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: Buggy "mime-support" package? :-( (re:)
On Mon, 6 Jan 1997, Timothy Phan wrote: > Hi, > > While we are on the subject of mime-support, I'd like to know > if there is some command that I can run at the command line to > decode a mime'd file? > The program is called munpack and will be found in the mpack package in the mail section. I use it all the time...with much success. Luck, Dwarf -- aka Dale Scheetz Phone: 1 (904) 656-9769 Flexible Software 11000 McCrackin Road e-mail: [EMAIL PROTECTED] Tallahassee, FL 32308 If you don't see what you want, just ask -- -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: Buggy "mime-support" package? :-(
On Mon, 6 Jan 1997, Brian C. White wrote: > > None of these are technically supposed to depend on mime-support. They > should only test for its availability before calling the "install-mime" > program. This is documented in the "install-mime" man page. > Well, I can only speak to the needs of the pine package. /etc/mailcap is provided by mime-support and needed by pine. This is the reason for it's dependence on mime-support. Install-mime is not needed or used by the pine installation scripts, so is not the issue here. I can only assume that the other packages mentioned have similar needs and therefore, rightly, depend on mime-support. Luck, Dwarf -- aka Dale Scheetz Phone: 1 (904) 656-9769 Flexible Software 11000 McCrackin Road e-mail: [EMAIL PROTECTED] Tallahassee, FL 32308 If you don't see what you want, just ask -- -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: Buggy "mime-support" package? :-( (re:)
Hi,
While we are on the subject of mime-support, I'd like to know
if there is some command that I can run at the command line to
decode a mime'd file?
Thanks!
Brian C. White wrote:
:
:> Well, trying to deinstall the mime-support for apparent reasons i just get
:> *lots* of dependancy conflicts making it impossible to do without this
:> thing. Here the relevant lines from the dselect dialog:
:> cut-here
:> pine depends on mime-support
:> apache depends on mime-support
:> xpdf depends on mime-support (>= 2.01-1)
:> metamail depends on mime-support (>= 2.02-1)
:> lynx recommends mime-support
:> xanim depends on mime-support (>= 2.08)
:> cut-here
:
--
Timothy C. Phan ([EMAIL PROTECTED])
NEC America, Inc. ASL
1525 Walnut Hill Ln. Irving, TX 75038
tel: (214)-518-3437 fax: (214)-518-3499
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: Buggy "mime-support" package? :-(
> Anyway, the main trouble seems to be that the Debian-1.2 /etc/mailcap has > grown to a rather ridiculous size as compared to the version provided with > Debian-1.1.xx: > cut-here > [root]/root > v /etc/mailcap* > -rw-r--r-- 1 root root 320596 Dec 24 04:12 /etc/mailcap > -rw-r--r-- 1 root root 502 Nov 30 13:41 /etc/mailcap.bak > -rw-r--r-- 1 root root 841 Dec 3 17:59 /etc/mailcap.dpkg-dist > cut-here I've seen one other case of this. It happened because the /etc/mailcap was not in the proper format. The latest mime-support package v2.09 (probably only in "bo") checks for this problem but older ones didn't. I suggest you remove the /etc/mailcap file and reinstall the "mime-support" package. > Well, trying to deinstall the mime-support for apparent reasons i just get > *lots* of dependancy conflicts making it impossible to do without this > thing. Here the relevant lines from the dselect dialog: > cut-here > pine depends on mime-support > apache depends on mime-support > xpdf depends on mime-support (>= 2.01-1) > metamail depends on mime-support (>= 2.02-1) > lynx recommends mime-support > xanim depends on mime-support (>= 2.08) > cut-here None of these are technically supposed to depend on mime-support. They should only test for its availability before calling the "install-mime" program. This is documented in the "install-mime" man page. Brian ( [EMAIL PROTECTED] ) --- It's not the days in your life, but the life in your days that counts. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Buggy "mime-support" package? :-(
One thing which really bothers me about Debian-1.2 is that it almost takes ages for lynx to come up at my 486DX-33 with 20MB. Measuring time for starting lynx with a locally served web page (apache) i get the following result: cut-here [pseelig]/home/pseelig > date ; xterm -e lynx http://localhost/ && date Sun Jan 5 03:10:16 MET 1997 Sun Jan 5 03:12:33 MET 1997 [pseelig]/home/pseelig > cut-here During these incredible *2 minutes and 17 seconds* there goes on a lot of testing in the background as can be verified with the 'ps' command: cut-here [pseelig]/home/pseelig > ps PID TT STAT TIME COMMAND 229 p0 S 0:02 /bin/bash 403 p2 S 0:34 pine -i 5903 p4 S 0:02 /bin/bash 6509 p3 S 0:02 lynx http://localhost/ 7286 p4 R 0:00 ps 7287 p3 S 0:00 sh -c test "`echo charset} | tr "[A-Z]" "[a-z]"`" = iso-8 7288 p3 R 0:00 sh -c test "`echo charset} | tr "[A-Z]" "[a-z]"`" = iso-8 7299 p3 R 0:00 sh -c test "`echo charset} | tr "[A-Z]" "[a-z]"`" = iso-8 [pseelig]/home/pseelig > cut-here The same happens from time to time in 'pine' depending upon the message's content which nonetheless are non critical ASCII texts. I just hate the idea of having my system slowed down like this just for viewing ASCII based texts like HTML or whatever. Anyway, the main trouble seems to be that the Debian-1.2 /etc/mailcap has grown to a rather ridiculous size as compared to the version provided with Debian-1.1.xx: cut-here [root]/root > v /etc/mailcap* -rw-r--r-- 1 root root 320596 Dec 24 04:12 /etc/mailcap -rw-r--r-- 1 root root 502 Nov 30 13:41 /etc/mailcap.bak -rw-r--r-- 1 root root 841 Dec 3 17:59 /etc/mailcap.dpkg-dist cut-here Well, trying to deinstall the mime-support for apparent reasons i just get *lots* of dependancy conflicts making it impossible to do without this thing. Here the relevant lines from the dselect dialog: cut-here pine depends on mime-support apache depends on mime-support xpdf depends on mime-support (>= 2.01-1) metamail depends on mime-support (>= 2.02-1) lynx recommends mime-support xanim depends on mime-support (>= 2.08) cut-here When i instead replace this overly large "/etc/mailcap" with the smaller sized "/etc/mailcap.dpkg-dist" lynx takes less than 3 seconds to come up at my humble system: cut-here [pseelig]/home/pseelig > date ; xterm -e lynx http://localhost/ && date Sun Jan 5 03:38:44 MET 1997 Sun Jan 5 03:38:48 MET 1997 [pseelig]/home/pseelig > cut-here I don't know if this is a reasonable way of dealing with this problem but at the moment i see no other way. As 'dpkg --status mime-support' reveals: "Other packages add themselves as viewers/editors/composers/etc by using the provided "install-mime" program." Maybe one of these other packages using "install-mime" has a bug resulting in growing /etc/mailcap to such a large extent? Or maybe "install-mime" itself has a bug? Anybody had similiar experiences? I'll try it out by deinstalling and then reinstalling the packages that depend on mime-support one of these days and if nobody else has already found out what it is all about. Regards, P. *8^) -- Paul Seelig [EMAIL PROTECTED] African Music Archive - Institute for Ethnology and Africa Studies Johannes Gutenberg-University - Forum 6 - 55099 Mainz/Germany Our AMA Homepage in the WWW at http://www.uni-mainz.de/~bender/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
