Result for 23961B70CC18B28D5BC0F8FFF46C1A3EBDC42C07

Query result

Key Value
FileName./usr/share/pycentral/buildbot/site-packages/buildbot/dnotify.py
FileSize3498
MD5853FD26ABF6313E1791C8D5CA1DA24F0
SHA-123961B70CC18B28D5BC0F8FFF46C1A3EBDC42C07
SHA-256C793E7E0085CE13087790C4E8341159C4450DE50E4E4B1EC82EF14965F495128
SSDEEP96:smIyqTBGi9dRFTlq4A9zcrkdQL8uB8Cl8slVl:sXjlriQzesLl
TLSHT12271532E364AE510DA53CB425507B9A3930FA47B095C545079FFD5901F0AA7043DAFDE
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
FileSize784208
MD5AEB21D3489AE99C35F3B1202D8151944
PackageDescriptiona system to automate the compile/test cycle The BuildBot is a system to automate the compile/test cycle required by most software projects to validate code changes. By automatically rebuilding and testing the tree each time something has changed, build problems are pinpointed quickly, before other developers are inconvenienced by the failure. The guilty developer can be identified and harassed without human intervention. . By running the builds on a variety of platforms, developers who do not have the facilities to test their changes everywhere before checkin will at least know shortly afterwards whether they have broken the build or not. Warning counts, lint checks, image size, compile time, and other build parameters can be tracked over time, are more visible, and are therefore easier to improve.
PackageMaintainerUbuntu MOTU Developers <ubuntu-motu@lists.ubuntu.com>
PackageNamebuildbot
PackageSectiondevel
PackageVersion0.7.4-2ubuntu2
SHA-1D78E4B1A7456A815F4581BFEDDEBAC25875B637F
SHA-25683A456DEEECBBF32717C6A6C84A726BFAF89958FB591D6E50789EF64906E6A29
Key Value
FileSize598958
MD5269C01E87B42C78EF611962ECE9FD040
PackageDescriptiona system to automate the compile/test cycle The BuildBot is a system to automate the compile/test cycle required by most software projects to validate code changes. By automatically rebuilding and testing the tree each time something has changed, build problems are pinpointed quickly, before other developers are inconvenienced by the failure. The guilty developer can be identified and harassed without human intervention. . By running the builds on a variety of platforms, developers who do not have the facilities to test their changes everywhere before checkin will at least know shortly afterwards whether they have broken the build or not. Warning counts, lint checks, image size, compile time, and other build parameters can be tracked over time, are more visible, and are therefore easier to improve.
PackageMaintainerMatthias Klose <doko@debian.org>
PackageNamebuildbot
PackageSectiondevel
PackageVersion0.7.2-0ubuntu1
SHA-1043239DA8109A623CB6D5C37EA7B27C5FAB899D7
SHA-2566FC226AEAEA981EE1231DD414EA92A0CBE6B4C651D74E35A1A789AD7B8D501CB