Result for 093A439D5D086AE50BFAE392EE460F5B593FCFE0

Query result

Key Value
FileName./usr/share/doc/logback/download.html
FileSize5427
MD53567475F532B5CE59DBFFF7938B9554A
SHA-1093A439D5D086AE50BFAE392EE460F5B593FCFE0
SHA-256C1910D17D0952B2C1F508F259798D1CCC64B0D531787C407A69D3927582BD727
SSDEEP96:kvxqBg7w/1DO30O5xm9jt5amaIDkAttXKPiOZTL/FY:LEw/k30O5xm1tQdxJiSTL/+
TLSHT112B1A54A7EF9D502A5540599D0F0BF29ED3D82873304ACD9B08C01BABFD6B959CDF189
hashlookup:parent-total3
hashlookup:trust65

Network graph view

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
MD51A81C57AC6D4D007AD89B235593845CA
PackageArchnoarch
PackageDescriptionLogback is intended as a successor to the popular log4j project. At present time, logback is divided into three modules, logback-core, logback-classic and logback-access. The logback-core module lays the groundwork for the other two modules. The logback-classic module can be assimilated to a significantly improved version of log4j. Moreover, logback-classic natively implements the SLF4J API so that you can readily switch back and forth between logback and other logging frameworks such as log4j or java.util.logging (JUL). The logback-access module integrates with Servlet containers, such as Tomcat and Jetty, to provide HTTP-access log functionality. Note that you could easily build your own module on top of logback-core.
PackageMaintainerFedora Project
PackageNamelogback
PackageRelease2.fc21
PackageVersion1.1.1
SHA-14052EDA507E4DAFFC18D2E888EAEEA06D6383547
SHA-256FDAA35261A9A71C536C9705EA941B4885BC40E5DF791A59F6127D46E8154057D
Key Value
MD5AADCA2C125979584424BEE65809F8BFD
PackageArchnoarch
PackageDescriptionLogback is intended as a successor to the popular log4j project. At present time, logback is divided into three modules, logback-core, logback-classic and logback-access. The logback-core module lays the groundwork for the other two modules. The logback-classic module can be assimilated to a significantly improved version of log4j. Moreover, logback-classic natively implements the SLF4J API so that you can readily switch back and forth between logback and other logging frameworks such as log4j or java.util.logging (JUL). The logback-access module integrates with Servlet containers, such as Tomcat and Jetty, to provide HTTP-access log functionality. Note that you could easily build your own module on top of logback-core.
PackageMaintainerFedora Project
PackageNamelogback
PackageRelease2.fc21
PackageVersion1.1.1
SHA-1A29B4CCE2C8BD25ED6BC051A0E72DA06709E18E4
SHA-2561D5F7BD921EBE616CE099F62D7080FBB7E2E7F524EBE2B6A5D849DE06D730C66
Key Value
MD505953EA7B283F6488FEA8D0C0E70146C
PackageArchnoarch
PackageDescriptionLogback is intended as a successor to the popular log4j project. At present time, logback is divided into three modules, logback-core, logback-classic and logback-access. The logback-core module lays the groundwork for the other two modules. The logback-classic module can be assimilated to a significantly improved version of log4j. Moreover, logback-classic natively implements the SLF4J API so that you can readily switch back and forth between logback and other logging frameworks such as log4j or java.util.logging (JUL). The logback-access module integrates with Servlet containers, such as Tomcat and Jetty, to provide HTTP-access log functionality. Note that you could easily build your own module on top of logback-core.
PackageMaintainerFedora Project
PackageNamelogback
PackageRelease2.fc21
PackageVersion1.1.1
SHA-14059A99CADDBFABF3D418C244ADA67E72C30DEA2
SHA-2568D64146A3B6B80B87D56DABB828DDAD19554F3DE5183329C12A52A13585847F4