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	513D268C0661E16F6D0E780C861C3A61
PackageArch	x86_64
PackageDescription	This tool's purpose is to help you determine which revision of a subversion repository contains a change. It does this by employing a binary search. It will manage the current revision of your checkout directory, and narrow in on the target revision, as you give it clues about the current revision such as "before" (this revision is before the one you want) or "after" (this revision is after the one you want). Start a bisect session with the "start" command. Then, walk the binary tree by using the "before" and "after" commands. When you are done, the tool will tell you the target revision. The most common usage scenario is finding out which rev a bug was introduced in. For this purpose, some command aliases have been added: if the current revision contains the bug, you can use the "bad" command (meaning, this revision is "after" the change you want to find), otherwise use the "good" command (meaning, this revision is "before" the change you want to find). All commands should be run from within a subversion checkout directory. After a "svn-bisect start", all subsequent svn-bisect commands need to be run from that same directory.
PackageName	svn-bisect
PackageRelease	4.58
PackageVersion	1.1
SHA-1	9F316FA29006CCD3BB30EDE9DB9EA07815C733F5
SHA-256	12963F07FFBB6BD7FD672BD96CED4DDFF34E2155A43A6BBBAD5C310FDE2BE24C

Key	Value
MD5	D51DE50AF3D2F8FAFCF8A2A83B656BD9
PackageArch	i586
PackageDescription	This tool's purpose is to help you determine which revision of a subversion repository contains a change. It does this by employing a binary search. It will manage the current revision of your checkout directory, and narrow in on the target revision, as you give it clues about the current revision such as "before" (this revision is before the one you want) or "after" (this revision is after the one you want). Start a bisect session with the "start" command. Then, walk the binary tree by using the "before" and "after" commands. When you are done, the tool will tell you the target revision. The most common usage scenario is finding out which rev a bug was introduced in. For this purpose, some command aliases have been added: if the current revision contains the bug, you can use the "bad" command (meaning, this revision is "after" the change you want to find), otherwise use the "good" command (meaning, this revision is "before" the change you want to find). All commands should be run from within a subversion checkout directory. After a "svn-bisect start", all subsequent svn-bisect commands need to be run from that same directory.
PackageName	svn-bisect
PackageRelease	4.58
PackageVersion	1.1
SHA-1	CFC56153CEA949C8846095CA4F9F103527FE1FD3
SHA-256	960EF2D925481CCFF6BF3458FA2D5ED474D36142B4DD21CF6C471DEB5BA0A71F

Key	Value
MD5	27840A9C9B219CC57C0023569FCD6EEF
PackageArch	x86_64
PackageDescription	This tool's purpose is to help you determine which revision of a subversion repository contains a change. It does this by employing a binary search. It will manage the current revision of your checkout directory, and narrow in on the target revision, as you give it clues about the current revision such as "before" (this revision is before the one you want) or "after" (this revision is after the one you want). Start a bisect session with the "start" command. Then, walk the binary tree by using the "before" and "after" commands. When you are done, the tool will tell you the target revision. The most common usage scenario is finding out which rev a bug was introduced in. For this purpose, some command aliases have been added: if the current revision contains the bug, you can use the "bad" command (meaning, this revision is "after" the change you want to find), otherwise use the "good" command (meaning, this revision is "before" the change you want to find). All commands should be run from within a subversion checkout directory. After a "svn-bisect start", all subsequent svn-bisect commands need to be run from that same directory.
PackageName	svn-bisect
PackageRelease	lp152.4.1
PackageVersion	1.1
SHA-1	D0FAD2C4F91717DFF0F9C1B7CBA19D8FAA63DB33
SHA-256	321A5FC8294DA2C2C2A0F303A5ECD36F8EFA235A0071E35A554CB7011833E80A

Key	Value
MD5	153F784CB30F3EFB162FB0B0D20DE141
PackageArch	armv7hl
PackageDescription	This tool's purpose is to help you determine which revision of a subversion repository contains a change. It does this by employing a binary search. It will manage the current revision of your checkout directory, and narrow in on the target revision, as you give it clues about the current revision such as "before" (this revision is before the one you want) or "after" (this revision is after the one you want). Start a bisect session with the "start" command. Then, walk the binary tree by using the "before" and "after" commands. When you are done, the tool will tell you the target revision. The most common usage scenario is finding out which rev a bug was introduced in. For this purpose, some command aliases have been added: if the current revision contains the bug, you can use the "bad" command (meaning, this revision is "after" the change you want to find), otherwise use the "good" command (meaning, this revision is "before" the change you want to find). All commands should be run from within a subversion checkout directory. After a "svn-bisect start", all subsequent svn-bisect commands need to be run from that same directory.
PackageName	svn-bisect
PackageRelease	4.18
PackageVersion	1.1
SHA-1	B45C324DE5D40D86026ECEE9859BA4E0EE864B30
SHA-256	B8B1AB2FBA70238F423BFD2160DE8127D609218988EB12CDDD574CDD03381D6C

Key	Value
MD5	FAFF88CF2680A6086B5E99A268B37B75
PackageArch	armv7hl
PackageDescription	This tool's purpose is to help you determine which revision of a subversion repository contains a change. It does this by employing a binary search. It will manage the current revision of your checkout directory, and narrow in on the target revision, as you give it clues about the current revision such as "before" (this revision is before the one you want) or "after" (this revision is after the one you want). Start a bisect session with the "start" command. Then, walk the binary tree by using the "before" and "after" commands. When you are done, the tool will tell you the target revision. The most common usage scenario is finding out which rev a bug was introduced in. For this purpose, some command aliases have been added: if the current revision contains the bug, you can use the "bad" command (meaning, this revision is "after" the change you want to find), otherwise use the "good" command (meaning, this revision is "before" the change you want to find). All commands should be run from within a subversion checkout directory. After a "svn-bisect start", all subsequent svn-bisect commands need to be run from that same directory.
PackageName	svn-bisect
PackageRelease	4.58
PackageVersion	1.1
SHA-1	2C49CC70CE354D6FA3B36DFC9B91B41D919605DF
SHA-256	76A46F87651C54B72A245CA314C1E21B4374DDEED556811467E88DEFD0C38388

Key	Value
MD5	FD1F1863CAF66E75A2C5E8628C5F6D33
PackageArch	x86_64
PackageDescription	This tool's purpose is to help you determine which revision of a subversion repository contains a change. It does this by employing a binary search. It will manage the current revision of your checkout directory, and narrow in on the target revision, as you give it clues about the current revision such as "before" (this revision is before the one you want) or "after" (this revision is after the one you want). Start a bisect session with the "start" command. Then, walk the binary tree by using the "before" and "after" commands. When you are done, the tool will tell you the target revision. The most common usage scenario is finding out which rev a bug was introduced in. For this purpose, some command aliases have been added: if the current revision contains the bug, you can use the "bad" command (meaning, this revision is "after" the change you want to find), otherwise use the "good" command (meaning, this revision is "before" the change you want to find). All commands should be run from within a subversion checkout directory. After a "svn-bisect start", all subsequent svn-bisect commands need to be run from that same directory.
PackageName	svn-bisect
PackageRelease	lp153.4.16
PackageVersion	1.1
SHA-1	E6C40DF622D2D1716006C4BE3A11A7BDD4D3B273
SHA-256	A4B787935B0FA9D76D0653A1B349F6A659DB2C3CA6D4AC4E1ACE2501ED88F2CF

Key	Value
MD5	68D91362324FDBF27F3737F629BCE4C7
PackageArch	x86_64
PackageDescription	This tool's purpose is to help you determine which revision of a subversion repository contains a change. It does this by employing a binary search. It will manage the current revision of your checkout directory, and narrow in on the target revision, as you give it clues about the current revision such as "before" (this revision is before the one you want) or "after" (this revision is after the one you want). Start a bisect session with the "start" command. Then, walk the binary tree by using the "before" and "after" commands. When you are done, the tool will tell you the target revision. The most common usage scenario is finding out which rev a bug was introduced in. For this purpose, some command aliases have been added: if the current revision contains the bug, you can use the "bad" command (meaning, this revision is "after" the change you want to find), otherwise use the "good" command (meaning, this revision is "before" the change you want to find). All commands should be run from within a subversion checkout directory. After a "svn-bisect start", all subsequent svn-bisect commands need to be run from that same directory.
PackageName	svn-bisect
PackageRelease	lp151.4.1
PackageVersion	1.1
SHA-1	E2B9A72D7FC6D9F802947B0C2D46415DDB1E6F31
SHA-256	F7B699A6A6BA14871D9A334FFEF5AD211F8097EF9C2D6BEA6839BC8A34051056