Parents (Total: 134)

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

Key	Value
MD5	EB586D76A9D76CA957117B8EF6EC3D6F
PackageArch	x86_64
PackageDescription	This library allows for the identification of a file's likely MIME content type. This is release 1.25.1, fixing an issue with priority comparison for mime-types 1.x. The current release is 2.0, which only supports Ruby 1.9 or later. Release 1.25.1 contains all features of 1.25, including the experimental caching and lazy loading functionality. The caching and lazy loading features were initially implemented by Greg Brockman (gdb). As these features are experimental, they are disabled by default and must be enabled through the use of environment variables. The cache is invalidated on a per-version basis; the cache for version 1.25 will not be reused for any later version. To use lazy loading, set the environment variable +RUBY_MIME_TYPES_LAZY_LOAD+ to any value other than 'false'. When using lazy loading, the initial startup of MIME::Types is around 12–25× faster than normal startup (on my system, normal startup is about 90 ms; lazy startup is about 4 ms). This isn't generally useful, however, as the MIME::Types database has not been loaded. Lazy startup and load is just *slightly* faster—around 1 ms. The real advantage comes from using the cache. To enable the cache, set the environment variable +RUBY_MIME_TYPES_CACHE+ to a filename where MIME::Types will have read-write access. The first time a new version of MIME::Types is run using this file, it will be created, taking a little longer than normal. Subsequent loads using the same cache file will be approximately 3½× faster (25 ms) than normal loads. This can be combined with +RUBY_MIME_TYPES_LAZY_LOAD+, but this is *not* recommended in a multithreaded or multiprocess environment where all threads or processes will be using the same cache file. As the caching interface is still experimental, the only values cached are the default MIME::Types database, not any custom MIME::Types added by users. MIME types are used in MIME-compliant communications, as in e-mail or HTTP traffic, to indicate the type of content which is transmitted. MIME::Types provides the ability for detailed information about MIME entities (provided as a set of MIME::Type objects) to be determined and used programmatically. There are many types defined by RFCs and vendors, so the list is long but not complete; don't hesitate to ask to add additional information. This library follows the IANA collection of MIME types (see below for reference). MIME::Types for Ruby was originally based on MIME::Types for Perl by Mark Overmeer, copyright 2001 - 2009. MIME::Types is built to conform to the MIME types of RFCs 2045 and 2231. It tracks the {IANA registry}[http://www.iana.org/assignments/media-types/] ({ftp}[ftp://ftp.iana.org/assignments/media-types]) with some unofficial types added from the {LTSW collection}[http://www.ltsw.se/knbase/internet/mime.htp] and added by the users of MIME::Types.
PackageMaintainer	https://bugs.opensuse.org
PackageName	ruby2.5-rubygem-mime-types-1
PackageRelease	lp151.2.1
PackageVersion	1.25.1
SHA-1	00AE9723D83A90F9785907E350983E06BE96CFD1
SHA-256	9692DFAABEEC79DB6A2613952044CEAC902C69303BE66DB864E0DA2BDC971BCF

Key	Value
FileName	https://ftp.lysator.liu.se/pub/OpenBSD/6.9/packages//amd64//logstash-7.10.0v0.tgz
MD5	0DA46B8AC1EEE755C58DAE164C48E5E1
SHA-1	015C27AABA74A3A39021F1071CBAFC957159B3D3
SHA-256	EFFA8BFB169444D6962D50525086E0D090E831F5926EE0415726B67F6FDCCD44
SSDEEP	3145728:PfoSDFsHqt7L4BwVF+UIUDu1+eK1Jbf72:PH46gQ+UpufCJbfS
TLSH	T1967833A1D1785434E1ADBB30A4CFAB0420BA14D84FE5DC7EF7AF56B61B063C9911CB29

Key	Value
FileSize	110564
MD5	0C74CCB436E8FBE3233FBA70B9B9F332
PackageDescription	guess MIME type of files This library allows for the identification of a file's likely MIME content type. The identification of MIME content type is based on a file's filename extensions.
PackageMaintainer	Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageName	ruby-mime-types
PackageSection	ruby
PackageVersion	2.6.1-1
SHA-1	04606CB0A3F3DE84DFB314467E7246D451B47468
SHA-256	E1374B3457D413F8FB2565877E21E1B066D0D37EE9666A44331946D3AF0C47C5

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

Key	Value
MD5	0E0DBC6C28D3FF5C7CFDE6AF912187CD
PackageArch	noarch
PackageDescription	MIME::Types for Ruby manages a MIME Content-Type database that will return the Content-Type for a given filename. MIME::Types was originally based on and synchronized with MIME::Types for Perl by Mark Overmeer, copyright 2001 - 2009. As of version 1.15, the data format for the MIME::Type list has changed and the synchronization will no longer happen.
PackageMaintainer	Fedora Project
PackageName	rubygem-mime-types
PackageRelease	1.fc21
PackageVersion	1.25.1
SHA-1	07038484AD97DD08D762D26352052A94C8DB6A40
SHA-256	A8AE40433F0C470A5B7924A7BC603DAD483AD480D948EC527AB60B7AD7BF84E6

Key	Value
MD5	FFBCBE2491B946DD0FF2DE13FB9989C4
PackageArch	i586
PackageDescription	This library allows for the identification of a file's likely MIME content type. This is release 1.25.1, fixing an issue with priority comparison for mime-types 1.x. The current release is 2.0, which only supports Ruby 1.9 or later. Release 1.25.1 contains all features of 1.25, including the experimental caching and lazy loading functionality. The caching and lazy loading features were initially implemented by Greg Brockman (gdb). As these features are experimental, they are disabled by default and must be enabled through the use of environment variables. The cache is invalidated on a per-version basis; the cache for version 1.25 will not be reused for any later version. To use lazy loading, set the environment variable +RUBY_MIME_TYPES_LAZY_LOAD+ to any value other than 'false'. When using lazy loading, the initial startup of MIME::Types is around 12–25× faster than normal startup (on my system, normal startup is about 90 ms; lazy startup is about 4 ms). This isn't generally useful, however, as the MIME::Types database has not been loaded. Lazy startup and load is just *slightly* faster—around 1 ms. The real advantage comes from using the cache. To enable the cache, set the environment variable +RUBY_MIME_TYPES_CACHE+ to a filename where MIME::Types will have read-write access. The first time a new version of MIME::Types is run using this file, it will be created, taking a little longer than normal. Subsequent loads using the same cache file will be approximately 3½× faster (25 ms) than normal loads. This can be combined with +RUBY_MIME_TYPES_LAZY_LOAD+, but this is *not* recommended in a multithreaded or multiprocess environment where all threads or processes will be using the same cache file. As the caching interface is still experimental, the only values cached are the default MIME::Types database, not any custom MIME::Types added by users. MIME types are used in MIME-compliant communications, as in e-mail or HTTP traffic, to indicate the type of content which is transmitted. MIME::Types provides the ability for detailed information about MIME entities (provided as a set of MIME::Type objects) to be determined and used programmatically. There are many types defined by RFCs and vendors, so the list is long but not complete; don't hesitate to ask to add additional information. This library follows the IANA collection of MIME types (see below for reference). MIME::Types for Ruby was originally based on MIME::Types for Perl by Mark Overmeer, copyright 2001 - 2009. MIME::Types is built to conform to the MIME types of RFCs 2045 and 2231. It tracks the {IANA registry}[http://www.iana.org/assignments/media-types/] ({ftp}[ftp://ftp.iana.org/assignments/media-types]) with some unofficial types added from the {LTSW collection}[http://www.ltsw.se/knbase/internet/mime.htp] and added by the users of MIME::Types.
PackageName	ruby3.0-rubygem-mime-types-1
PackageRelease	15.25
PackageVersion	1.25.1
SHA-1	09B69D9CBEC9DB2CA57ED79CC331F772690C74AF
SHA-256	A0EA9C124FC4DDF9CB616C261FED7BC3A2DA6D9CAC24043FAB837F66E437E590

Key	Value
MD5	4E66352CDDFAFF93E62304947C47558C
PackageArch	noarch
PackageDescription	MIME::Types for Ruby manages a MIME Content-Type database that will return the Content-Type for a given filename. MIME::Types was originally based on and synchronized with MIME::Types for Perl by Mark Overmeer, copyright 2001 - 2009. As of version 1.15, the data format for the MIME::Type list has changed and the synchronization will no longer happen.
PackageMaintainer	Fedora Project
PackageName	rubygem-mime-types
PackageRelease	1.fc21
PackageVersion	1.25.1
SHA-1	0D9D618AB3B0B840365DC9F4E9010E4BF52CE78D
SHA-256	002C73D67085B4D288398DB02E490A79649E790F33302F4BA73BFFF0BE87F434

Key	Value
MD5	4030FEE0FD1AC4F0D5F24472757EF128
PackageArch	x86_64
PackageDescription	logstash is a tool for managing events and logs. You can use it to collect logs, parse them, and store them for later use (like, for searching).
PackageName	logstash
PackageRelease	1.1
PackageVersion	2.4.1
SHA-1	0FB5633CA3B47103AECFF28DACA4F1A7C853FB6F
SHA-256	1E085AF1447A079844D0B5D817C6FF0C04B70C9D63F14FA2528A8C43D458D5A1

Key	Value
MD5	EDBD442DD64F47DB279DE36D64418B00
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. This is release 2.99.1, the first scheduled data update for mime-types 2.x. As of mime-types 2.99. deprecation warnings are noisy and data that has been deprecated is now no longer available. The data is both dropped from the data files and is stubbed out as empty or +nil+ values as appropriate. mime-types-2.6 was the last version of mime-types 2.x with newly available features, and mime-types 2.99 will only receive quarterly updates to the IANA registered MIME media types plus any security updates that may be required. If the loss of the deprecated data matters, be sure to set your dependency appropriately: gem 'mime-types', '~> 2.6, < 2.99'.
PackageName	ruby2.5-rubygem-mime-types-2
PackageRelease	lp154.1.2
PackageVersion	2.99.3
SHA-1	1100A0CFB0EF5FC380F280CE6E65533419D9E2EB
SHA-256	F91F291F730E5C01F316BFEF300C0D341CF54CA5D49F79C134DA88FA7458FBD6

Key	Value
MD5	96B07E69CAC83D62D7EFBA98B071347E
PackageArch	x86_64
PackageDescription	This library allows for the identification of a file's likely MIME content type. This is release 1.25.1, fixing an issue with priority comparison for mime-types 1.x. The current release is 2.0, which only supports Ruby 1.9 or later. Release 1.25.1 contains all features of 1.25, including the experimental caching and lazy loading functionality. The caching and lazy loading features were initially implemented by Greg Brockman (gdb). As these features are experimental, they are disabled by default and must be enabled through the use of environment variables. The cache is invalidated on a per-version basis; the cache for version 1.25 will not be reused for any later version. To use lazy loading, set the environment variable +RUBY_MIME_TYPES_LAZY_LOAD+ to any value other than 'false'. When using lazy loading, the initial startup of MIME::Types is around 12–25× faster than normal startup (on my system, normal startup is about 90 ms; lazy startup is about 4 ms). This isn't generally useful, however, as the MIME::Types database has not been loaded. Lazy startup and load is just *slightly* faster—around 1 ms. The real advantage comes from using the cache. To enable the cache, set the environment variable +RUBY_MIME_TYPES_CACHE+ to a filename where MIME::Types will have read-write access. The first time a new version of MIME::Types is run using this file, it will be created, taking a little longer than normal. Subsequent loads using the same cache file will be approximately 3½× faster (25 ms) than normal loads. This can be combined with +RUBY_MIME_TYPES_LAZY_LOAD+, but this is *not* recommended in a multithreaded or multiprocess environment where all threads or processes will be using the same cache file. As the caching interface is still experimental, the only values cached are the default MIME::Types database, not any custom MIME::Types added by users. MIME types are used in MIME-compliant communications, as in e-mail or HTTP traffic, to indicate the type of content which is transmitted. MIME::Types provides the ability for detailed information about MIME entities (provided as a set of MIME::Type objects) to be determined and used programmatically. There are many types defined by RFCs and vendors, so the list is long but not complete; don't hesitate to ask to add additional information. This library follows the IANA collection of MIME types (see below for reference). MIME::Types for Ruby was originally based on MIME::Types for Perl by Mark Overmeer, copyright 2001 - 2009. MIME::Types is built to conform to the MIME types of RFCs 2045 and 2231. It tracks the {IANA registry}[http://www.iana.org/assignments/media-types/] ({ftp}[ftp://ftp.iana.org/assignments/media-types]) with some unofficial types added from the {LTSW collection}[http://www.ltsw.se/knbase/internet/mime.htp] and added by the users of MIME::Types.
PackageName	ruby2.6-rubygem-mime-types-1
PackageRelease	lp154.14.2
PackageVersion	1.25.1
SHA-1	111FF501BAC6C20455A8BBFD15543B5FD85CFC8A
SHA-256	69BC22AFACB2C6355ACF94537BF899636369202782DC52B35E34DE919C8DA83D