Parents (Total: 35)

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

Key	Value
SHA-1	01094331C315996BD9740D19E85E15A36C1C2286
snap-authority	canonical
snap-filename	XSlaE4S2cu0h5r6o7dFaFiQIsugKLFpa_695.snap
snap-id	XSlaE4S2cu0h5r6o7dFaFiQIsugKLFpa_695
snap-name	root-framework
snap-publisher-id	VoUAJzdpg1T1K8hp70EmA7f7dJkxb7BA
snap-signkey	BWDEoaqyr25nF5SNCvEv2v7QnM9QsfCc0PBMYD_i2NGSQ32EF2d4D0hqUel3m8ul
snap-timestamp	2020-11-27T06:22:05.033990Z
source-url	https://api.snapcraft.io/api/v1/snaps/download/XSlaE4S2cu0h5r6o7dFaFiQIsugKLFpa_695.snap

Key	Value
FileSize	229384
MD5	DACE74053B5204E9364557645BF8268D
PackageDescription	Google's internal fork of OpenSSL for the Android SDK - devel The Android SDK builds against a static version of BoringSSL, Google's internal fork of OpenSSL. This package should never be used for anything but Android SDK packages that already depend on it. . BoringSSL arose because Google used OpenSSL for many years in various ways and, over time, built up a large number of patches that were maintained while tracking upstream OpenSSL. As Google’s product portfolio became more complex, more copies of OpenSSL sprung up and the effort involved in maintaining all these patches in multiple places was growing steadily. . This is the Android AOSP fork of BoringSSL which is designed to be used by Android and its SDK. BoringSSL is only ever statically linked into apps, and pinned to a commit version. Upstream has no official releases of BoringSSL on its own, so it must be included separately for each project that uses it. . This package contains the development files.
PackageMaintainer	Android Tools Maintainers <android-tools-devel@lists.alioth.debian.org>
PackageName	android-libboringssl-dev
PackageSection	libdevel
PackageVersion	13~preview2-3
SHA-1	057B15825C0D6B81F13F69CA24198A48944FD79E
SHA-256	FB84B312C4805AEF3187979B253507C859AD03797625114E06C482ED7BED7AF4

Key	Value
FileSize	196672
MD5	A33CB737CDCD1850D2BCA94612A793D6
PackageDescription	Google's internal fork of OpenSSL for the Android SDK - devel The Android SDK builds against a static version of BoringSSL, Google's internal fork of OpenSSL. This package should never be used for anything but Android SDK packages that already depend on it. . BoringSSL arose because Google used OpenSSL for many years in various ways and, over time, built up a large number of patches that were maintained while tracking upstream OpenSSL. As Google’s product portfolio became more complex, more copies of OpenSSL sprung up and the effort involved in maintaining all these patches in multiple places was growing steadily. . This is the Android AOSP fork of BoringSSL which is designed to be used by Android and its SDK. BoringSSL is only ever statically linked into apps, and pinned to a commit version. Upstream has no official releases of BoringSSL on its own, so it must be included separately for each project that uses it. . This package contains the development files.
PackageMaintainer	Android Tools Maintainers <android-tools-devel@lists.alioth.debian.org>
PackageName	android-libboringssl-dev
PackageSection	libdevel
PackageVersion	10.0.0+r36-2~exp1
SHA-1	07E03767080BF32FF153921D979A30E921E99528
SHA-256	6CCFBC49D0DE291CACB233FA9EC8FF961FBB5001D3DAC6C56D6DD97C9388767E

Key	Value
FileSize	196668
MD5	2D66790F147E45051A7E1B6C07FE4D81
PackageDescription	Google's internal fork of OpenSSL for the Android SDK - devel The Android SDK builds against a static version of BoringSSL, Google's internal fork of OpenSSL. This package should never be used for anything but Android SDK packages that already depend on it. . BoringSSL arose because Google used OpenSSL for many years in various ways and, over time, built up a large number of patches that were maintained while tracking upstream OpenSSL. As Google’s product portfolio became more complex, more copies of OpenSSL sprung up and the effort involved in maintaining all these patches in multiple places was growing steadily. . This is the Android AOSP fork of BoringSSL which is designed to be used by Android and its SDK. BoringSSL is only ever statically linked into apps, and pinned to a commit version. Upstream has no official releases of BoringSSL on its own, so it must be included separately for each project that uses it. . This package contains the development files.
PackageMaintainer	Android Tools Maintainers <android-tools-devel@lists.alioth.debian.org>
PackageName	android-libboringssl-dev
PackageSection	libdevel
PackageVersion	10.0.0+r36-2~exp1
SHA-1	0A85FB6565603A625F1F37208C0CDE784AA261C4
SHA-256	56E583602F779EEF273D41F7955B391E008611EEBCCC0CD834F59E6260134749

Key	Value
SHA-1	0BD43A023CD2ABA0D757FE61CEADD4FD43C8C403
snap-authority	canonical
snap-filename	XSlaE4S2cu0h5r6o7dFaFiQIsugKLFpa_620.snap
snap-id	XSlaE4S2cu0h5r6o7dFaFiQIsugKLFpa_620
snap-name	root-framework
snap-publisher-id	VoUAJzdpg1T1K8hp70EmA7f7dJkxb7BA
snap-signkey	BWDEoaqyr25nF5SNCvEv2v7QnM9QsfCc0PBMYD_i2NGSQ32EF2d4D0hqUel3m8ul
snap-timestamp	2020-11-27T06:22:05.033990Z
source-url	https://api.snapcraft.io/api/v1/snaps/download/XSlaE4S2cu0h5r6o7dFaFiQIsugKLFpa_620.snap

Key	Value
SHA-1	0D1449986F6E37C3B72DB99134F8BB709C2242BD
snap-authority	canonical
snap-filename	jtBG52gsnZJLjq3VteGFOyMnEqtHAWAs_535.snap
snap-id	jtBG52gsnZJLjq3VteGFOyMnEqtHAWAs_535
snap-name	weebl-tools
snap-publisher-id	G1rqdx35XwIQVfWVmEqirmnuYKCXHT66
snap-signkey	BWDEoaqyr25nF5SNCvEv2v7QnM9QsfCc0PBMYD_i2NGSQ32EF2d4D0hqUel3m8ul
snap-timestamp	2019-07-31T16:57:59.595562Z
source-url	https://api.snapcraft.io/api/v1/snaps/download/jtBG52gsnZJLjq3VteGFOyMnEqtHAWAs_535.snap

Key	Value
FileSize	229384
MD5	61B02032406499E2E9E9A2EFAA716B9E
PackageDescription	Google's internal fork of OpenSSL for the Android SDK - devel The Android SDK builds against a static version of BoringSSL, Google's internal fork of OpenSSL. This package should never be used for anything but Android SDK packages that already depend on it. . BoringSSL arose because Google used OpenSSL for many years in various ways and, over time, built up a large number of patches that were maintained while tracking upstream OpenSSL. As Google’s product portfolio became more complex, more copies of OpenSSL sprung up and the effort involved in maintaining all these patches in multiple places was growing steadily. . This is the Android AOSP fork of BoringSSL which is designed to be used by Android and its SDK. BoringSSL is only ever statically linked into apps, and pinned to a commit version. Upstream has no official releases of BoringSSL on its own, so it must be included separately for each project that uses it. . This package contains the development files.
PackageMaintainer	Android Tools Maintainers <android-tools-devel@lists.alioth.debian.org>
PackageName	android-libboringssl-dev
PackageSection	libdevel
PackageVersion	13~preview2-3
SHA-1	160FD521CA19C287ADFE4F5924F3258DD6C9FC8D
SHA-256	5933705B873219C75369DC9BC37D0E4AB77BCC754F523AB07D9FE0FC3C5A8BB8

Key	Value
FileSize	196668
MD5	459F471EDACED4DDCCCE670CF0204030
PackageDescription	Google's internal fork of OpenSSL for the Android SDK - devel The Android SDK builds against a static version of BoringSSL, Google's internal fork of OpenSSL. This package should never be used for anything but Android SDK packages that already depend on it. . BoringSSL arose because Google used OpenSSL for many years in various ways and, over time, built up a large number of patches that were maintained while tracking upstream OpenSSL. As Google’s product portfolio became more complex, more copies of OpenSSL sprung up and the effort involved in maintaining all these patches in multiple places was growing steadily. . This is the Android AOSP fork of BoringSSL which is designed to be used by Android and its SDK. BoringSSL is only ever statically linked into apps, and pinned to a commit version. Upstream has no official releases of BoringSSL on its own, so it must be included separately for each project that uses it. . This package contains the development files.
PackageMaintainer	Android Tools Maintainers <android-tools-devel@lists.alioth.debian.org>
PackageName	android-libboringssl-dev
PackageSection	libdevel
PackageVersion	10.0.0+r36-2~exp1
SHA-1	2349AEC390BB83E0D82E98CFA88FBB321A6D667D
SHA-256	C21F6AB364A994516AC45CB45328EB589DDFE3659A34F959B8F47510C7E9CDF9

Key	Value
FileSize	229388
MD5	87383CEEB8A47E7663FA78EE40F8A058
PackageDescription	Google's internal fork of OpenSSL for the Android SDK - devel The Android SDK builds against a static version of BoringSSL, Google's internal fork of OpenSSL. This package should never be used for anything but Android SDK packages that already depend on it. . BoringSSL arose because Google used OpenSSL for many years in various ways and, over time, built up a large number of patches that were maintained while tracking upstream OpenSSL. As Google’s product portfolio became more complex, more copies of OpenSSL sprung up and the effort involved in maintaining all these patches in multiple places was growing steadily. . This is the Android AOSP fork of BoringSSL which is designed to be used by Android and its SDK. BoringSSL is only ever statically linked into apps, and pinned to a commit version. Upstream has no official releases of BoringSSL on its own, so it must be included separately for each project that uses it. . This package contains the development files.
PackageMaintainer	Android Tools Maintainers <android-tools-devel@lists.alioth.debian.org>
PackageName	android-libboringssl-dev
PackageSection	libdevel
PackageVersion	13~preview2-3
SHA-1	292DFD6810EC042D001369DD511E3C44C614E4C6
SHA-256	5037A7E9EA7AFDDE5EEF0C1B5E66909DD6E0AE34F64FCF1CAC8CE9302BD13367

Key	Value
FileName	http://archlinux.mirror.root.lu//pool//community//gitlab-gitaly-13.10.0-1-x86_64.pkg.tar.zst
MD5	2A8C385CB60E2F402A9DC8628972F633
SHA-1	2C103188EEF2752C568E51F1FABA8DC8FAFDCCF1
SHA-256	4C4DED3809C20732DC0DE42C0784F62F06F699BF5C1DC1AC46734C8D0E6822FB
SSDEEP	1572864:JCylj6DjF4JS2azTgXDKIkcpRgmkb2XpPjTudrEbq8NKXsue3Y28Cxg+SAXqoz1U:Jtlj+Z4J42KIk6jBYrOg87nPUX
TLSH	T1AD68335282F3A04BE1E94535C70B1B7842948E037A85CB25A85B71F6F4B3DD1FA18BED