Parents (Total: 3)

The searched file hash is included in 3 parent files which include package known and seen by metalookup. A sample is included below:

Key	Value
MD5	548C10308035A27E9490AD11223B7D8B
PackageArch	x86_64
PackageDescription	The mime-types library provides a library and registry for information about MIME content type definitions. It can be used to determine defined filename extensions for MIME types, or to use filename extensions to look up the likely MIME type definitions. MIME content types are used in MIME-compliant communications, as in e-mail or HTTP traffic, to indicate the type of content which is transmitted. The mime-types library provides the ability for detailed information about MIME entities (provided as an enumerable collection of MIME::Type objects) to be determined and used. There are many types defined by RFCs and vendors, so the list is long but by definition incomplete; don't hesitate to add additional type definitions. MIME type definitions found in mime-types are from RFCs, W3C recommendations, the {IANA Media Types registry}[https://www.iana.org/assignments/media-types/media-types.xhtml], and user contributions. It conforms to RFCs 2045 and 2231. This is release 2.6 with two new experimental features. The first new feature is a new default registry storage format that greatly reduces the initial memory use of the mime-types library. This feature is enabled by requiring +mime/types/columnar+ instead of +mime/types+ with a small performance cost and no change in *total* memory use if certain methods are called (see {Columnar Store}[#columnar-store] for more details). The second new feature is a logger interface that conforms to the expectations of an ActiveSupport::Logger so that warnings can be written to an application's log rather than the default location for +warn+. This interface may be used for other logging purposes in the future. mime-types 2.6 is the last planned version of mime-types 2.x, so deprecation warnings are no longer cached but provided every time the method is called. mime-types 2.6 supports Ruby 1.9.2 or later.
PackageName	ruby2.7-rubygem-mime-types
PackageRelease	1.44
PackageVersion	2.6.1
SHA-1	92D23CC5F41D92327884B811D7B205C78FD2300F
SHA-256	C21804F36237A06C6DCC16B82F8416EA02E89052780819D6647BEAF2AEF2AC8B

Key	Value
MD5	89EE1DA600E6450B54FCD4154799329A
PackageArch	i586
PackageDescription	The mime-types library provides a library and registry for information about MIME content type definitions. It can be used to determine defined filename extensions for MIME types, or to use filename extensions to look up the likely MIME type definitions. MIME content types are used in MIME-compliant communications, as in e-mail or HTTP traffic, to indicate the type of content which is transmitted. The mime-types library provides the ability for detailed information about MIME entities (provided as an enumerable collection of MIME::Type objects) to be determined and used. There are many types defined by RFCs and vendors, so the list is long but by definition incomplete; don't hesitate to add additional type definitions. MIME type definitions found in mime-types are from RFCs, W3C recommendations, the {IANA Media Types registry}[https://www.iana.org/assignments/media-types/media-types.xhtml], and user contributions. It conforms to RFCs 2045 and 2231. This is release 2.6 with two new experimental features. The first new feature is a new default registry storage format that greatly reduces the initial memory use of the mime-types library. This feature is enabled by requiring +mime/types/columnar+ instead of +mime/types+ with a small performance cost and no change in *total* memory use if certain methods are called (see {Columnar Store}[#columnar-store] for more details). The second new feature is a logger interface that conforms to the expectations of an ActiveSupport::Logger so that warnings can be written to an application's log rather than the default location for +warn+. This interface may be used for other logging purposes in the future. mime-types 2.6 is the last planned version of mime-types 2.x, so deprecation warnings are no longer cached but provided every time the method is called. mime-types 2.6 supports Ruby 1.9.2 or later.
PackageName	ruby2.7-rubygem-mime-types
PackageRelease	1.44
PackageVersion	2.6.1
SHA-1	CF07139C74FF6D0AEB82BB688D71C47084E97CA4
SHA-256	84B75F779704CBED4DB794A83D8D0E3BB4131BB7ECDB9D9735CBABD22C1FE3C4

Key	Value
MD5	A6627C24CB382405ED34D58088BD4835
PackageArch	x86_64
PackageDescription	The mime-types library provides a library and registry for information about MIME content type definitions. It can be used to determine defined filename extensions for MIME types, or to use filename extensions to look up the likely MIME type definitions. MIME content types are used in MIME-compliant communications, as in e-mail or HTTP traffic, to indicate the type of content which is transmitted. The mime-types library provides the ability for detailed information about MIME entities (provided as an enumerable collection of MIME::Type objects) to be determined and used. There are many types defined by RFCs and vendors, so the list is long but by definition incomplete; don't hesitate to add additional type definitions. MIME type definitions found in mime-types are from RFCs, W3C recommendations, the {IANA Media Types registry}[https://www.iana.org/assignments/media-types/media-types.xhtml], and user contributions. It conforms to RFCs 2045 and 2231. This is release 2.6 with two new experimental features. The first new feature is a new default registry storage format that greatly reduces the initial memory use of the mime-types library. This feature is enabled by requiring +mime/types/columnar+ instead of +mime/types+ with a small performance cost and no change in *total* memory use if certain methods are called (see {Columnar Store}[#columnar-store] for more details). The second new feature is a logger interface that conforms to the expectations of an ActiveSupport::Logger so that warnings can be written to an application's log rather than the default location for +warn+. This interface may be used for other logging purposes in the future. mime-types 2.6 is the last planned version of mime-types 2.x, so deprecation warnings are no longer cached but provided every time the method is called. mime-types 2.6 supports Ruby 1.9.2 or later.
PackageName	ruby2.7-rubygem-mime-types
PackageRelease	1.43
PackageVersion	2.6.1
SHA-1	065F4F55FCDBFCBC05B36E8C62DE47E16C3F344F
SHA-256	8314C8FC75FC85B3A08B542359C49FE009F5153CD75A21A3133977733FB6C0F5