Result for F39109A2DFCA2EA25E6A5E355FD5248C45A628CC

Query result

Key Value
FileName./usr/share/doc/packages/mirror-registry/README.md
FileSize1225
MD54FA9E59B2B4EB89E1D70211F229CF1D7
SHA-1F39109A2DFCA2EA25E6A5E355FD5248C45A628CC
SHA-256E3FE9D1421E24FF9C145CF5EFA910F6CF4717E80FA5510091C544E1573B114D9
SSDEEP24:LuMuXWFtM6OKiaGHFXf/VWXrINz52gd1GIUsJtpqFJBxRO8UrMoFJBN:LuMuT3Ko/VWXENz52gd1GxsJm+dr/N
TLSHT18721AD1BDF45B96317D242FD7D7A22B07F2280C181664E52FB3492FC61654DE193F6A0
hashlookup:parent-total18
hashlookup:trust100

Network graph view

Parents (Total: 18)

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

Key Value
MD59F46264D144CC90B40F899561729A5B7
PackageArchs390x
PackageDescriptionmirror-registry will analyse a remote registry and create a yaml file with all containers and tags matching a regex to sync with skopeo to a private registry. While this tool understands the architecture flag for containers, skopeo does not really use this information yet. If a repository contains multi-arch containers, it will fail if there is no container for the architecture it is running on, else it will use the architecture which it is running on.
PackageMaintainerhttps://bugs.opensuse.org
PackageNamemirror-registry
PackageReleasebp153.1.65
PackageVersion1.1
SHA-1001A578DCC94A066DA7A5C324D1CBD7713034EA6
SHA-256A3147F92691D81A8DA20CC18073BE1CBD047B6D3CA64920D515043CD9D11109E
Key Value
MD5764A65F9D22F70F7044128DD857972CF
PackageArchx86_64
PackageDescriptionmirror-registry will analyse a remote registry and create a yaml file with all containers and tags matching a regex to sync with skopeo to a private registry. While this tool understands the architecture flag for containers, skopeo does not really use this information yet. If a repository contains multi-arch containers, it will fail if there is no container for the architecture it is running on, else it will use the architecture which it is running on.
PackageNamemirror-registry
PackageRelease6.78
PackageVersion1.1
SHA-11516FB158B82C20166B40F755BB3CA0F9DAA73F0
SHA-256EF6BA2F62CE2D65656EA6444F60C09B9C10AEAB6892A6F1DC4AA69BE603870C3
Key Value
MD55D08B307413FB63DFFAE239338EC56F2
PackageArchx86_64
PackageDescriptionmirror-registry will analyse a remote registry and create a yaml file with all containers and tags matching a regex to sync with skopeo to a private registry. While this tool understands the architecture flag for containers, skopeo does not really use this information yet. If a repository contains multi-arch containers, it will fail if there is no container for the architecture it is running on, else it will use the architecture which it is running on.
PackageNamemirror-registry
PackageRelease6.11
PackageVersion1.1
SHA-123DA734F5449E344348B9899F02476A4992A54AA
SHA-256EA985C93DFF10AD46AE8E2B9E7CCBE1730417006D24C356534FBAC0C53A01E5A
Key Value
MD5CB3DAE8C5079963096E437402084D1E0
PackageArchs390x
PackageDescriptionmirror-registry will analyse a remote registry and create a yaml file with all containers and tags matching a regex to sync with skopeo to a private registry. While this tool understands the architecture flag for containers, skopeo does not really use this information yet. If a repository contains multi-arch containers, it will fail if there is no container for the architecture it is running on, else it will use the architecture which it is running on.
PackageMaintainerhttps://bugs.opensuse.org
PackageNamemirror-registry
PackageReleasebp154.1.41
PackageVersion1.1
SHA-1347060C1EA0EEF3AFFB4A64403FA0BF0BBF2E947
SHA-2563F816424A2F43740DC2A112ED1B78B8DF27FBA11011958F29E106D3F71365D6F
Key Value
MD5CF64664B00BE486EF99806A43202F1A5
PackageArchx86_64
PackageDescriptionmirror-registry will analyse a remote registry and create a yaml file with all containers and tags matching a regex to sync with skopeo to a private registry. While this tool understands the architecture flag for containers, skopeo does not really use this information yet. If a repository contains multi-arch containers, it will fail if there is no container for the architecture it is running on, else it will use the architecture which it is running on.
PackageNamemirror-registry
PackageReleaselp151.5.1
PackageVersion1.1
SHA-13BFD4BAF56A25546A62B4EF63461AC4453105700
SHA-256EA8FED573893A3DDEC5DE06B0D1B44E71B41BF7FBECAF3F5B4043342220D691E
Key Value
MD53AB399FEB818E0F8ED7B8ED30ADF0CAB
PackageArchx86_64
PackageDescriptionmirror-registry will analyse a remote registry and create a yaml file with all containers and tags matching a regex to sync with skopeo to a private registry. While this tool understands the architecture flag for containers, skopeo does not really use this information yet. If a repository contains multi-arch containers, it will fail if there is no container for the architecture it is running on, else it will use the architecture which it is running on.
PackageMaintainerhttps://bugs.opensuse.org
PackageNamemirror-registry
PackageReleasebp154.1.41
PackageVersion1.1
SHA-13CE7C9507A64853A33FAB165F0C5DE699DAB1B54
SHA-2569E254BC7AC4875341188390FE00A6F6D10EA4B92CA3082E9EC3B39AFD9881BE7
Key Value
MD504A50FE2961CF9C99E631E97EAD012BD
PackageArchs390x
PackageDescriptionmirror-registry will analyse a remote registry and create a yaml file with all containers and tags matching a regex to sync with skopeo to a private registry. While this tool understands the architecture flag for containers, skopeo does not really use this information yet. If a repository contains multi-arch containers, it will fail if there is no container for the architecture it is running on, else it will use the architecture which it is running on.
PackageNamemirror-registry
PackageRelease6.77
PackageVersion1.1
SHA-16097D3F5466E7A46D7132638B5986E420D6CF43B
SHA-256882129EECE4BD97C81C7DEC26B4309E23599616AD0EE954F423991E227B7E48B
Key Value
MD5B56DF8D1BBBD3889FBDBFCB7031E5FAE
PackageArchx86_64
PackageDescriptionmirror-registry will analyse a remote registry and create a yaml file with all containers and tags matching a regex to sync with skopeo to a private registry. While this tool understands the architecture flag for containers, skopeo does not really use this information yet. If a repository contains multi-arch containers, it will fail if there is no container for the architecture it is running on, else it will use the architecture which it is running on.
PackageMaintainerhttps://bugs.opensuse.org
PackageNamemirror-registry
PackageReleasebp155.1.7
PackageVersion1.3
SHA-17DDD82222CE139DF7C1E1FEC843A6C0ED32335D8
SHA-2564EAE80D62D172B22F1A7564D657B9D977EBEB8B07E8C092970E9A9C8EF70DABA
Key Value
MD5C1E4589FDC1DE49B3CECBEB6634B826B
PackageArchx86_64
PackageDescriptionmirror-registry will analyse a remote registry and create a yaml file with all containers and tags matching a regex to sync with skopeo to a private registry. While this tool understands the architecture flag for containers, skopeo does not really use this information yet. If a repository contains multi-arch containers, it will fail if there is no container for the architecture it is running on, else it will use the architecture which it is running on.
PackageNamemirror-registry
PackageReleaselp152.6.5
PackageVersion1.1
SHA-1A4E5FD037438778A0BBFD6797ED7CA7FA1665198
SHA-25659F955129016329FF0139E2C0BB952C3A730DE905E2E5047C99E8BFD0B7AD76B
Key Value
MD5252F7B28058AED2A671BDD78DF5AED20
PackageArchs390x
PackageDescriptionmirror-registry will analyse a remote registry and create a yaml file with all containers and tags matching a regex to sync with skopeo to a private registry. While this tool understands the architecture flag for containers, skopeo does not really use this information yet. If a repository contains multi-arch containers, it will fail if there is no container for the architecture it is running on, else it will use the architecture which it is running on.
PackageMaintainerhttps://bugs.opensuse.org
PackageNamemirror-registry
PackageReleasebp156.1.14
PackageVersion1.4
SHA-1AB933B1CD0D48D5B23DF6BF7EB00C13838797736
SHA-256FAD1D558F8AC103D7F02C9DADFE6A7AE30825E5A312943C2C2CA7FA2DDB5997E