Re: Unexpected behaviour of MIME::Types

Could be a corrupted types.db file?

Some things, you could check:

type perl # correct perl in use?
echo $PERL_MIME_TYPE_DB # is it set? (should not // set for testing)
perldoc -l MIME::Types # something like $DIR/Types.pod.

There, inspect file $DIR/types.db. diff with versions of that file which work/work-not. Watch for line-endings, etc. Details of parsing can be found in MIME::Types::_read_db().

Comment on Re: Unexpected behaviour of MIME::Types Select or Download Code

Replies are listed 'Best First'.
Re^2: Unexpected behaviour of MIME::Types by choroba (Cardinal) on Jan 28, 2018 at 17:37 UTC
Yes, there were some extra lines in `types.db`. Reinstall of MIME::Types after cleaning `.cpan/build` helped. ($q=q:Sq=~/;[c](.)(.)/;chr(-\|\|-\|5+lengthSq)`"S\|oS2"`map{chr \|+ord }map{substrSq`S_+\|`\|}3E\|-\|`7**2-3:)=~y+S\|`+$1,++print+eval$q,q,a, [download]	[reply] [d/l] [select]