Result for AAD7CD572D60847F97F2DCC653A79E34044DA88C

Query result

Key Value
FileNameautoconf-2.69-perl-5.22-autoscan.patch
FileSize820
MD5AA07AFE5A671DF25BF1878831702D5B9
RDS:package_id293705
SHA-1AAD7CD572D60847F97F2DCC653A79E34044DA88C
SHA-256A1B6AAFD4F42B244F8234B45132B130F26D5518CE202CA903C747A50F0020617
SSDEEP24:rzqfztgF2x08x41uJ2xdfYr92xy2yOQwI2L21C4Y7fdYG:rAzyF2xLxlJ2xC92xy2+wI2L2wB
TLSHT14C01FD5202C708704A0A51F27646378E7B6B565113D9A54C749E27B4FF08F2F72DE24A
insert-timestamp1678966179.776178
sourceRDS.db
hashlookup:parent-total6
hashlookup:trust80

Network graph view

Parents (Total: 6)

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

Key Value
MD57E65072782F48EA9477967C93B80AD74
PackageArchnoarch
PackageDescriptionGNU's Autoconf is a tool for configuring source code and Makefiles. Using Autoconf, programmers can create portable and configurable packages, since the person building the package is allowed to specify various configuration options. You should install Autoconf if you are developing software and would like to create shell scripts that configure your source code packages. If you are installing Autoconf, you will also need to install the GNU m4 package. Note that the Autoconf package is not required for the end-user who may be configuring software with an Autoconf-generated script; Autoconf is only required for the generation of the scripts, not their use.
PackageMaintainerAlmaLinux Packaging Team <packager@almalinux.org>
PackageNameautoconf
PackageRelease29.el8
PackageVersion2.69
SHA-13DAFBE48A32EDAA7915A1472EBC2C0B49FDF7208
SHA-256AD5FDF72AE5F6A1A9826AABB385DD39A77CB6C2A91D25F75ADE2CC3153163708
Key Value
MD53C8876FE17434AECE534D5DE30C05478
PackageArchnoarch
PackageDescriptionGNU's Autoconf is a tool for configuring source code and Makefiles. Using Autoconf, programmers can create portable and configurable packages, since the person building the package is allowed to specify various configuration options. You should install Autoconf if you are developing software and would like to create shell scripts that configure your source code packages. If you are installing Autoconf, you will also need to install the GNU m4 package. Note that the Autoconf package is not required for the end-user who may be configuring software with an Autoconf-generated script; Autoconf is only required for the generation of the scripts, not their use.
PackageMaintainerFedora Project
PackageNameautoconf
PackageRelease34.fc33
PackageVersion2.69
SHA-16F05FECBD3E1ECD59C4026E82DB2B7856119A9A9
SHA-256CB0F859C1C325097F39FC157FE8A320A9C9BF288F496EAF44377FF1820851CE5
Key Value
MD57E46946550A7EF9D8DA98C14D8A67803
PackageArchnoarch
PackageDescriptionGNU's Autoconf is a tool for configuring source code and Makefiles. Using Autoconf, programmers can create portable and configurable packages, since the person building the package is allowed to specify various configuration options. You should install Autoconf if you are developing software and would like to create shell scripts that configure your source code packages. If you are installing Autoconf, you will also need to install the GNU m4 package. Note that the Autoconf package is not required for the end-user who may be configuring software with an Autoconf-generated script; Autoconf is only required for the generation of the scripts, not their use.
PackageMaintainerFedora Project
PackageNameautoconf
PackageRelease33.fc32
PackageVersion2.69
SHA-10E7E397571320CC1C91086B9C59478D4F03A2B89
SHA-2563EA6708097021976D839BA1C75CBB86F2DF5547B7C75B51CBF7CF4A732C356B8
Key Value
MD503E6723070AF99983BA5217E63FBFAFD
PackageArchnoarch
PackageDescriptionGNU's Autoconf is a tool for configuring source code and Makefiles. Using Autoconf, programmers can create portable and configurable packages, since the person building the package is allowed to specify various configuration options. You should install Autoconf if you are developing software and would like to create shell scripts that configure your source code packages. If you are installing Autoconf, you will also need to install the GNU m4 package. Note that the Autoconf package is not required for the end-user who may be configuring software with an Autoconf-generated script; Autoconf is only required for the generation of the scripts, not their use.
PackageMaintainerFedora Project
PackageNameautoconf
PackageRelease21.fc23
PackageVersion2.69
SHA-11E576A7C381FCB014BDAF770C56EC98FB2D67270
SHA-25696829FBF4B4CD33462BADA14541250AC49946C99902C864A319F0EE9B18D511B
Key Value
MD54C51B9390CBCE855A5B4BB6D3985520D
PackageArchnoarch
PackageDescriptionGNU's Autoconf is a tool for configuring source code and Makefiles. Using Autoconf, programmers can create portable and configurable packages, since the person building the package is allowed to specify various configuration options. You should install Autoconf if you are developing software and would like to create shell scripts that configure your source code packages. If you are installing Autoconf, you will also need to install the GNU m4 package. Note that the Autoconf package is not required for the end-user who may be configuring software with an Autoconf-generated script; Autoconf is only required for the generation of the scripts, not their use.
PackageMaintainerCloudLinux Packaging Team <packager@cloudlinux.com>
PackageNameautoconf
PackageRelease27.el8
PackageVersion2.69
SHA-1C22381A1A2C8FADD6834B6DF4FEBA11D1C0D7F7A
SHA-2564B4147C6FF8E5C8E074DEFB039380D66D3E76E90AF3A9EE10059093447A673DC
Key Value
MD5D5261E4E134867CCBDF1A7C042C91379
PackageArchnoarch
PackageDescriptionGNU's Autoconf is a tool for configuring source code and Makefiles. Using Autoconf, programmers can create portable and configurable packages, since the person building the package is allowed to specify various configuration options. You should install Autoconf if you are developing software and would like to create shell scripts that configure your source code packages. If you are installing Autoconf, you will also need to install the GNU m4 package. Note that the Autoconf package is not required for the end-user who may be configuring software with an Autoconf-generated script; Autoconf is only required for the generation of the scripts, not their use.
PackageMaintainerFedora Project
PackageNameautoconf
PackageRelease36.fc34
PackageVersion2.69
SHA-1A1CC6732D5965AAF281770AED85B71ED1F8C8238
SHA-2563A30DD7BBA487842337E1C91A39983B38E86BB6AF5CE607A7EFF9422908AB24F