Result for 24AA22CF765349EE3C8B6B4C91A9DD8AB1AC259D

Query result

Key Value
FileName./usr/share/doc/packages/ruby2.7-rubygem-mime-types/History.rdoc
FileSize68
MD52C51BE9FFA36919865328C1960C3D4CE
SHA-124AA22CF765349EE3C8B6B4C91A9DD8AB1AC259D
SHA-25604626F55756BDAAA1D3E09C938416AB9EEF9E8267E52C5CBCC6F8671D00159BB
SSDEEP3:gC63cZA2PKEcVQTKGn:d11cVQ2Gn
TLSHT1C6A022E0C3B320202A808003EC08AE0233800C0F330A3F8032CC003A00C820B33CC880
hashlookup:parent-total2
hashlookup:trust60

Network graph view

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
MD5548C10308035A27E9490AD11223B7D8B
PackageArchx86_64
PackageDescriptionThe 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.
PackageNameruby2.7-rubygem-mime-types
PackageRelease1.44
PackageVersion2.6.1
SHA-192D23CC5F41D92327884B811D7B205C78FD2300F
SHA-256C21804F36237A06C6DCC16B82F8416EA02E89052780819D6647BEAF2AEF2AC8B
Key Value
MD5A6627C24CB382405ED34D58088BD4835
PackageArchx86_64
PackageDescriptionThe 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.
PackageNameruby2.7-rubygem-mime-types
PackageRelease1.43
PackageVersion2.6.1
SHA-1065F4F55FCDBFCBC05B36E8C62DE47E16C3F344F
SHA-2568314C8FC75FC85B3A08B542359C49FE009F5153CD75A21A3133977733FB6C0F5