Parents (Total: 2)

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

Key	Value
MD5	F84B0FA42A451178CC5BAC56B621F012
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	ruby3.0-rubygem-mime-types
PackageRelease	1.44
PackageVersion	2.6.1
SHA-1	B72E8FBCF6EACBD4B8B582B43AA853603531E92F
SHA-256	D6AEFFD078F4ED9AAD66C904B5A60798ED005A2B6930335526910F57C8C1A276

Key	Value
MD5	8056051BC11F3E12168A3DC1FB698CDF
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	ruby3.0-rubygem-mime-types
PackageRelease	1.43
PackageVersion	2.6.1
SHA-1	4F23309833DF9702D06A66AE9455016A3E0D38F4
SHA-256	67FE954E480C84D022C33E0F6A1033F9C784534B60DD39926BA73CAD7B0B90A1