Result for 097E2B2738DD279187E2C27EABEB92DEF4ED1FC6

Query result

Key Value
CRC326FF8D0F3
FileNameconfig.site
FileSize880
MD56E34946C247C282046F2CD58C2374DEC
OpSystemCode{'MfgCode': '1006', 'OpSystemCode': '362', 'OpSystemName': 'TBD', 'OpSystemVersion': 'none'}
ProductCode{'ApplicationType': 'Operating System', 'Language': 'English', 'MfgCode': '2194', 'OpSystemCode': '51', 'ProductCode': '17393', 'ProductName': 'Fedora 23 Server 32-bit', 'ProductVersion': '2015'}
RDS:package_id293705
SHA-1097E2B2738DD279187E2C27EABEB92DEF4ED1FC6
SHA-256B92B63CAB3165B0EE318A18CBDC3AFD8CA9DD46EBA39CEA50979E8E20C3C032E
SSDEEP24:q67L1o44HxxLJRTLoM8amiFu/SS9QlZVQmi4QSvLc9pXa:TNFKVh8DiaaQ4lTcnq
SpecialCode
TLSHT1CD11EF79F5DBF169342040E976CB70511A87C3AF5174291CF2CCB5402B7F308A2B4676
dbnsrl_modern_rds
insert-timestamp1678966180.0167987
sourceRDS.db
hashlookup:parent-total23
hashlookup:trust100

Network graph view

Parents (Total: 23)

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

Key Value
MD534E61527C76109E7855FF4E45E9EC9A6
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-101CA510A51726EA7817EAC3465337306F35EF77A
SHA-256128B90117069853D63091D14B1FBA65A85ADC4B1079FCA09B9DED0E28EFB1685
Key Value
MD50DD39E890CE20CE4348DDF0CE160F888
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
PackageRelease18.fc22
PackageVersion2.69
SHA-1070B32C41344DF62F9D5DD770A82978E7518FBEB
SHA-2564A68305B9607EC614D77D24D62ABF8C007C60670052C23C129D34D42F97A4333
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
MD548C01DC471FB759C704D74367E42E909
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-1392BC7B2A3ABA9AF23CDA1AD2579FFBBF15005BF
SHA-25646151555730D5A568D92245E1B5F98A3441E41E0140EB75AA227C359BEA8E85F
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
MD598D9785D129A9730F644C8FACFB1E219
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
PackageRelease18.fc22
PackageVersion2.69
SHA-1694A7D2B0B9E3BC7369C5503D26387D9B94018F5
SHA-25641D5A7897C5BD28463A0BD5DBAE673F9275BB8A918B45393AA4905705F7FD6B8
Key Value
MD56E2376D61CCC22A604BA274E3C23FD61
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-16B701D5E54ACADFB88E8E2CD2CCE8811CEE39EB7
SHA-256A3FB7CE4282CA766037ABF046176C56519C3EDEE64E2F3BE5529B12D6E755186
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
MD5B7B9B9AC0C949F5ABB38F9CBF8294D45
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.
PackageMaintainerCentOS Buildsys <bugs@centos.org>
PackageNameautoconf
PackageRelease29.el8
PackageVersion2.69
SHA-17DED40B1C6D6B773F4F722480385A795D16968DD
SHA-2569AACBB294B025BBD17F31F037FEDD28CC3F30852FFB4917A3DA4C364BADE8072