Parents (Total: 74)

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

Key	Value
MD5	E4BA4F1D0DD09EA1A15526EE30A553A7
PackageArch	armv7hl
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	python39-hyper
PackageRelease	22.1
PackageVersion	0.7.0+git89.b77e758
SHA-1	05569304AD26B2DEEA49CCA3CFD35E0FC49BA849
SHA-256	10F3F2267FC620A050973634339F280C0A19E4E16D66BEA60A336F4CF4B28336

Key	Value
SHA-1	08151CC94E178D15C51B73BA5B84F91BF4845C33
snap-authority	canonical
snap-filename	BYa8IlUQqqTyhwCjoPWb8Pf2ZaBKQdSv_471.snap
snap-id	BYa8IlUQqqTyhwCjoPWb8Pf2ZaBKQdSv_471
snap-name	home-assistant-snap
snap-publisher-id	Zgwwrb2vssjDtam8qFmo4ezg3koyPPyQ
snap-signkey	BWDEoaqyr25nF5SNCvEv2v7QnM9QsfCc0PBMYD_i2NGSQ32EF2d4D0hqUel3m8ul
snap-timestamp	2022-01-14T16:38:28.794566Z
source-url	https://api.snapcraft.io/api/v1/snaps/download/BYa8IlUQqqTyhwCjoPWb8Pf2ZaBKQdSv_471.snap

Key	Value
MD5	230FA0E2EBD2DD933AD9CB6188644A32
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	python3-hyper
PackageRelease	lp154.3.1
PackageVersion	0.7.0+git89.b77e758
SHA-1	0F5886BE598F899B92024B647F15D3F785202A26
SHA-256	D3195C8328611CBF8840241B17530DD8D6A1C3CC4F1F1C0E87C728F29D505913

Key	Value
MD5	31955200C08CDF52593FF20218F74FCF
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	lp153.26.1
PackageVersion	0.7.0+git88.18b629b
SHA-1	10F0E361EB08A214FDC727B05299B9570B8B0BA8
SHA-256	F8546291C6BC86AE48824B6D0E75FA5298FEC99A585A869B1A60FCD83928AD7D

Key	Value
MD5	D6A363DDF2582209474BEB9C1B9ADFBF
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	10.1
PackageVersion	0.7.0+git88.18b629b
SHA-1	11EBF0E259AE64C5A461D4ADD0523A9862DFA19F
SHA-256	078BACBBDF15CCFC8606F52383C8FC6110F82EEB8C8A5965116A261E01DAC578

Key	Value
MD5	C6DB909AB7C0042B756D98DD39E4ED3C
PackageArch	armv7hl
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	python39-hyper
PackageRelease	27.2
PackageVersion	0.7.0+git88.18b629b
SHA-1	13F6EB6D27DB5630D67FB0588BA8BB282B682335
SHA-256	3240E5DC01A1D984214FC7E1FF5B1A508D3D7ED6FC62F3F4D06CFD7C3CB14745

Key	Value
MD5	CE588096A5AEFD7C1CE008D4DC3E730E
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	python3-hyper
PackageRelease	7.2
PackageVersion	0.7.0+git88.18b629b
SHA-1	14A5A787E85C373FC4467C0EE55D6D1CED38DBB9
SHA-256	9B828B0CB09B33F0E41ED8E8BC27A3959DD89A5092CF054EA4B85163104E67F6

Key	Value
MD5	0FF21B8F566A9CFA821D1CEB097DD66A
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	python3-hyper
PackageRelease	19.2
PackageVersion	0.7.0+git88.18b629b
SHA-1	15754C062B825746514E015887B8067EA29655F0
SHA-256	6677A4EC3B010F11AD333EE4D5EB9A83E0C61C2BB822E4C256DD110FD105C88F

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	D65F069CF43D2DA4587DD88381293A40
PackageArch	armv7hl
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	python38-hyper
PackageRelease	27.2
PackageVersion	0.7.0+git88.18b629b
SHA-1	170E5BC1F3AEB893E706FB7611C7C4AA977ED25B
SHA-256	B7636DF11E69A857937F28740F7367B26E09B8F083430F63781B8C5CBB9308FB