Parents (Total: 7)

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

Key	Value
MD5	2D0225AA8B060518D62B553576D1D9EC
PackageArch	x86_64
PackageDescription	hyper supports the final draft of the HTTP/2 specification: additionally, it provides support for drafts 14, 15, and 16 of the HTTP/2 specification. It also supports the final draft of the HPACK specification. hyper is intended to be a drop-in replacement for http.client, with a similar API. However, hyper intentionally does not name its classes the same way http.client does. This is because most servers do not support HTTP/2 at this time: I don't want you accidentally using hyper when you wanted http.client.
PackageMaintainer	https://bugs.opensuse.org
PackageName	python2-hyper
PackageRelease	bp153.1.17
PackageVersion	0.7.0+git88.18b629b
SHA-1	15B2457D1DBF96D0ED360C83D507C82D7260EDAB
SHA-256	28A3010B889C02A09236690D2CC739E35416F53444512A06602E09E9DEE211EF

Key	Value
MD5	E91879B8C372FCF3148FB24562F66483
PackageArch	x86_64
PackageDescription	hyper supports the final draft of the HTTP/2 specification: additionally, it provides support for drafts 14, 15, and 16 of the HTTP/2 specification. It also supports the final draft of the HPACK specification. hyper is intended to be a drop-in replacement for http.client, with a similar API. However, hyper intentionally does not name its classes the same way http.client does. This is because most servers do not support HTTP/2 at this time: I don't want you accidentally using hyper when you wanted http.client.
PackageMaintainer	https://bugs.opensuse.org
PackageName	python2-hyper
PackageRelease	lp152.3.1
PackageVersion	0.7.0+git88.18b629b
SHA-1	E4BF87B7458247465F2A1FA590B2A5B779A3C45F
SHA-256	F9060C0EEEF7E4647F998BB6FE7DD320118A440FB5310D37690030DC7A64DEFC

Key	Value
MD5	BA5EE713625780BC1952BBC5FEC64905
PackageArch	s390x
PackageDescription	hyper supports the final draft of the HTTP/2 specification: additionally, it provides support for drafts 14, 15, and 16 of the HTTP/2 specification. It also supports the final draft of the HPACK specification. hyper is intended to be a drop-in replacement for http.client, with a similar API. However, hyper intentionally does not name its classes the same way http.client does. This is because most servers do not support HTTP/2 at this time: I don't want you accidentally using hyper when you wanted http.client.
PackageMaintainer	https://bugs.opensuse.org
PackageName	python2-hyper
PackageRelease	bp153.1.17
PackageVersion	0.7.0+git88.18b629b
SHA-1	514C04EC553FBA162201A6161250A84B8F70F5A0
SHA-256	33E801CE210E672D9FDC6087A1BE1BFD41D10CFD04B9CE757452B3F7FF0F6D25

Key	Value
MD5	ECABFF93DFCDDFDF289C6A665DC06610
PackageArch	x86_64
PackageDescription	hyper supports the final draft of the HTTP/2 specification: additionally, it provides support for drafts 14, 15, and 16 of the HTTP/2 specification. It also supports the final draft of the HPACK specification. hyper is intended to be a drop-in replacement for http.client, with a similar API. However, hyper intentionally does not name its classes the same way http.client does. This is because most servers do not support HTTP/2 at this time: I don't want you accidentally using hyper when you wanted http.client.
PackageName	python2-hyper
PackageRelease	lp151.19.1
PackageVersion	0.7.0+git88.18b629b
SHA-1	3B93F9614955E2B4AD7A1F36330081EB8F571C86
SHA-256	C503B2737920AA89E6F7216D297DE9C1CFAA234A9A6A404C76FD1CFCB5A83D1F

Key	Value
MD5	7CB0D67AE5335F8C794A737164F5CAFF
PackageArch	x86_64
PackageDescription	hyper supports the final draft of the HTTP/2 specification: additionally, it provides support for drafts 14, 15, and 16 of the HTTP/2 specification. It also supports the final draft of the HPACK specification. hyper is intended to be a drop-in replacement for http.client, with a similar API. However, hyper intentionally does not name its classes the same way http.client does. This is because most servers do not support HTTP/2 at this time: I don't want you accidentally using hyper when you wanted http.client.
PackageName	python2-hyper
PackageRelease	7.2
PackageVersion	0.7.0+git88.18b629b
SHA-1	FC3751DE512EDB639B7C938239CC070BE534D008
SHA-256	802AE3B0A6B542B9F28CB275B89AE3793BEF3A16AEB5FE9C5135C14D5CA96BE1

Key	Value
MD5	FF59881DD07EFDE7A06B513C338BC24F
PackageArch	x86_64
PackageDescription	hyper supports the final draft of the HTTP/2 specification: additionally, it provides support for drafts 14, 15, and 16 of the HTTP/2 specification. It also supports the final draft of the HPACK specification. hyper is intended to be a drop-in replacement for http.client, with a similar API. However, hyper intentionally does not name its classes the same way http.client does. This is because most servers do not support HTTP/2 at this time: I don't want you accidentally using hyper when you wanted http.client.
PackageName	python2-hyper
PackageRelease	19.2
PackageVersion	0.7.0+git88.18b629b
SHA-1	6E1C8F6AB630C71816E19C85CED80F57E34FA868
SHA-256	F28F63DD5D20DD70311C7D15112F7F4DA9F29254D62DD59E331E577633DD2926

Key	Value
MD5	DBEB46B3E46D4B2556AE7C8D7511AB5A
PackageArch	x86_64
PackageDescription	hyper supports the final draft of the HTTP/2 specification: additionally, it provides support for drafts 14, 15, and 16 of the HTTP/2 specification. It also supports the final draft of the HPACK specification. hyper is intended to be a drop-in replacement for http.client, with a similar API. However, hyper intentionally does not name its classes the same way http.client does. This is because most servers do not support HTTP/2 at this time: I don't want you accidentally using hyper when you wanted http.client.
PackageName	python2-hyper
PackageRelease	lp151.7.2
PackageVersion	0.7.0+git88.18b629b
SHA-1	D64255D29B73F25B20AE332132D906FD395A68AA
SHA-256	DCB0A2C2DEA81390C8B490D5EB4169427821A3F360E121B1577ED3D9A8E7AF5A