Parents (Total: 17)

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

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
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	196572
MD5	018FC7738D705924EF964C83D1760FBA
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-1
SHA-1	32076B022226B02EB00B211EE0C50347EA125303
SHA-256	EFDA2BF8FF82C655CB531191D5182F028509997AEF2DF7756E69DBA2562D754B

Key	Value
FileSize	196572
MD5	B462E1817734B6970617E93F8A346B7E
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-1
SHA-1	4F58DB3F36362F7808DEC6EDC83572B1530FF0E3
SHA-256	18FBD539DE4B7953144AEDC4A90BE2971768D78EE213E358901BC99ADE649C76

Key	Value
FileSize	196672
MD5	86CFA70ECD3DE5546A09426E4547AD81
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	606EFB6982B02632F9FF6BE79965760F48448312
SHA-256	68F66C4363AD3D877ABC7A5CB4C1B83662218C0DEE346FA3D39D95BEA87896A9

Key	Value
FileSize	196576
MD5	5252751258B5A80C6AFE2993E6395A4B
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-1
SHA-1	748635D106CEE5C19C5E25E0096F33CBEFEA34E1
SHA-256	5293A2024772E64D5E6062493D42289D3F87C2832A196030996763AA10281BA6

Key	Value
FileSize	196680
MD5	A407DEA8BD498539B7DA19EA3D9DCAA5
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	75E25F4714D554337150796E7B44CB4F7D3E3BD4
SHA-256	12F06AD70EF28E03890E8ACBAB206C597A10EA9A3043254F9677F1C4A9F5D761

Key	Value
FileSize	196564
MD5	99FAFCC32389257E11C480FC9049E831
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-1
SHA-1	7778458453D65362A098D67C448B2BBBC8CB782E
SHA-256	EDC459DA54F2F8CB3D96275927444EA7A71DE79F1C9AFF017206C05134E51DEA

Key	Value
MD5	33333885A18A68D24984D6CD805DE37B
PackageArch	x86_64
PackageDescription	This package provides debug sources for package qt5-qtwebengine. Debug sources are useful when developing applications that use this package or when debugging this package.
PackageMaintainer	Fedora Project
PackageName	qt5-qtwebengine-debugsource
PackageRelease	4.fc32
PackageVersion	5.13.2
SHA-1	7C195D08FAB3BE528A6342A4730A33A81EE77E76
SHA-256	00C4F72F0BCF60A5BA455BD87EE74CE85973429ECCA8CAE8EBD32A98A656FCC1