Parents (Total: 13)

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

Key	Value
MD5	2A2254C846E9BA64DE0711D02D78579F
PackageArch	noarch
PackageDescription	go4.org is a collection of packages for Go programmers. They started out living in Perkeep's repo and elsewhere but they have nothing to do with Perkeep, so we're moving them here. Details * single repo. go4 is a single repo. That means things can be changed and rearranged globally atomically with ease and confidence. * no backwards compatibility. go4 makes no backwards compatibility promises. If you want to use go4, vendor it. And next time you update your vendor tree, update to the latest API if things in go4 changed. The plan is to eventually provide tools to make this easier. * forward progress because we have no backwards compatibility, it's always okay to change things to make things better. That also means the bar for contributions is lower. We don't have to get the API 100% correct in the first commit. * no Go version policy go4 packages are usually built and tested with the latest Go stable version. However, go4 has no overarching version policy; each package can declare its own set of supported Go versions. * code review contributions must be code-reviewed. We're trying out Gerrithub, to see if we can find a mix of Github Pull Requests and Gerrit that works well for many people. We'll see. * CLA compliant contributors must agree to the Google CLA (the same as Go itself). This ensures we can move things into Go as necessary in the future. It also makes lawyers at various companies happy. The CLA is not a copyright assignment; you retain the copyright on your work. The CLA just says that your work is open source and you have permission to open source it. See https://golang.org/doc/contribute.html#cla * docs, tests, portability all code should be documented in the normal Go style, have tests, and be portable to different operating systems and architectures. We'll try to get builders in place to help run the tests on different OS/arches. For now we have Travis at least.
PackageName	golang-github-go4org-go4
PackageRelease	lp153.1.1
PackageVersion	0.0.0+git20200411.f5505b9
SHA-1	9D227158B5B5A0265AC36C18F5D38B0290390B64
SHA-256	35F53C361161DC093CBA10BF319632A17A36D8C669199E5683D5E7F9309B9B90

Key	Value
MD5	695921E62DEC7F238BFC4328F8C8CC95
PackageArch	noarch
PackageDescription	go4.org is a collection of packages for Go programmers. They started out living in Perkeep's repo and elsewhere but they have nothing to do with Perkeep, so we're moving them here. Details * single repo. go4 is a single repo. That means things can be changed and rearranged globally atomically with ease and confidence. * no backwards compatibility. go4 makes no backwards compatibility promises. If you want to use go4, vendor it. And next time you update your vendor tree, update to the latest API if things in go4 changed. The plan is to eventually provide tools to make this easier. * forward progress because we have no backwards compatibility, it's always okay to change things to make things better. That also means the bar for contributions is lower. We don't have to get the API 100% correct in the first commit. * no Go version policy go4 packages are usually built and tested with the latest Go stable version. However, go4 has no overarching version policy; each package can declare its own set of supported Go versions. * code review contributions must be code-reviewed. We're trying out Gerrithub, to see if we can find a mix of Github Pull Requests and Gerrit that works well for many people. We'll see. * CLA compliant contributors must agree to the Google CLA (the same as Go itself). This ensures we can move things into Go as necessary in the future. It also makes lawyers at various companies happy. The CLA is not a copyright assignment; you retain the copyright on your work. The CLA just says that your work is open source and you have permission to open source it. See https://golang.org/doc/contribute.html#cla * docs, tests, portability all code should be documented in the normal Go style, have tests, and be portable to different operating systems and architectures. We'll try to get builders in place to help run the tests on different OS/arches. For now we have Travis at least.
PackageName	golang-github-go4org-go4
PackageRelease	1.2
PackageVersion	0.0.0+git20200411.f5505b9
SHA-1	B632CBE34A9008390EA96F4B7451B0B9D8931BC4
SHA-256	AC822E4AA232B43ACA25640E4241CA0E25369A16FF6E8F3F2BEB9FA0F13C8D72

Key	Value
MD5	52A98431881E26612EE68F9ED5AE47A0
PackageArch	noarch
PackageDescription	go4.org is a collection of packages for Go programmers. They started out living in Perkeep's repo and elsewhere but they have nothing to do with Perkeep, so we're moving them here. Details * single repo. go4 is a single repo. That means things can be changed and rearranged globally atomically with ease and confidence. * no backwards compatibility. go4 makes no backwards compatibility promises. If you want to use go4, vendor it. And next time you update your vendor tree, update to the latest API if things in go4 changed. The plan is to eventually provide tools to make this easier. * forward progress because we have no backwards compatibility, it's always okay to change things to make things better. That also means the bar for contributions is lower. We don't have to get the API 100% correct in the first commit. * no Go version policy go4 packages are usually built and tested with the latest Go stable version. However, go4 has no overarching version policy; each package can declare its own set of supported Go versions. * code review contributions must be code-reviewed. We're trying out Gerrithub, to see if we can find a mix of Github Pull Requests and Gerrit that works well for many people. We'll see. * CLA compliant contributors must agree to the Google CLA (the same as Go itself). This ensures we can move things into Go as necessary in the future. It also makes lawyers at various companies happy. The CLA is not a copyright assignment; you retain the copyright on your work. The CLA just says that your work is open source and you have permission to open source it. See https://golang.org/doc/contribute.html#cla * docs, tests, portability all code should be documented in the normal Go style, have tests, and be portable to different operating systems and architectures. We'll try to get builders in place to help run the tests on different OS/arches. For now we have Travis at least.
PackageName	golang-github-go4org-go4
PackageRelease	1.2
PackageVersion	0.0.0+git20200411.f5505b9
SHA-1	0DB6EDA7BB85291296D9049F446429FB66C93726
SHA-256	219CB7C8C84B293930EF381F30280CEF1E3451C1FE1F9EF1EC81686699C6C298

Key	Value
MD5	4BD88BEF7BD0E74C415EAA46B2FA422A
PackageArch	noarch
PackageDescription	go4.org is a collection of packages for Go programmers. They started out living in Perkeep's repo and elsewhere but they have nothing to do with Perkeep, so we're moving them here. Details * single repo. go4 is a single repo. That means things can be changed and rearranged globally atomically with ease and confidence. * no backwards compatibility. go4 makes no backwards compatibility promises. If you want to use go4, vendor it. And next time you update your vendor tree, update to the latest API if things in go4 changed. The plan is to eventually provide tools to make this easier. * forward progress because we have no backwards compatibility, it's always okay to change things to make things better. That also means the bar for contributions is lower. We don't have to get the API 100% correct in the first commit. * no Go version policy go4 packages are usually built and tested with the latest Go stable version. However, go4 has no overarching version policy; each package can declare its own set of supported Go versions. * code review contributions must be code-reviewed. We're trying out Gerrithub, to see if we can find a mix of Github Pull Requests and Gerrit that works well for many people. We'll see. * CLA compliant contributors must agree to the Google CLA (the same as Go itself). This ensures we can move things into Go as necessary in the future. It also makes lawyers at various companies happy. The CLA is not a copyright assignment; you retain the copyright on your work. The CLA just says that your work is open source and you have permission to open source it. See https://golang.org/doc/contribute.html#cla * docs, tests, portability all code should be documented in the normal Go style, have tests, and be portable to different operating systems and architectures. We'll try to get builders in place to help run the tests on different OS/arches. For now we have Travis at least.
PackageName	golang-github-go4org-go4
PackageRelease	1.2
PackageVersion	0.0.0+git20200411.f5505b9
SHA-1	6A6A562B614B39E7029691AD3754DAB9C0EDE373
SHA-256	8235D9289748587723FE61760E87ECAF2ED1C21BFA914C896B7B191CD14A7FDA

Key	Value
MD5	96350BF7449FF2DECDB479FC16FAE5EF
PackageArch	noarch
PackageDescription	go4.org is a collection of packages for Go programmers. They started out living in Perkeep's repo and elsewhere but they have nothing to do with Perkeep, so we're moving them here. Details * single repo. go4 is a single repo. That means things can be changed and rearranged globally atomically with ease and confidence. * no backwards compatibility. go4 makes no backwards compatibility promises. If you want to use go4, vendor it. And next time you update your vendor tree, update to the latest API if things in go4 changed. The plan is to eventually provide tools to make this easier. * forward progress because we have no backwards compatibility, it's always okay to change things to make things better. That also means the bar for contributions is lower. We don't have to get the API 100% correct in the first commit. * no Go version policy go4 packages are usually built and tested with the latest Go stable version. However, go4 has no overarching version policy; each package can declare its own set of supported Go versions. * code review contributions must be code-reviewed. We're trying out Gerrithub, to see if we can find a mix of Github Pull Requests and Gerrit that works well for many people. We'll see. * CLA compliant contributors must agree to the Google CLA (the same as Go itself). This ensures we can move things into Go as necessary in the future. It also makes lawyers at various companies happy. The CLA is not a copyright assignment; you retain the copyright on your work. The CLA just says that your work is open source and you have permission to open source it. See https://golang.org/doc/contribute.html#cla * docs, tests, portability all code should be documented in the normal Go style, have tests, and be portable to different operating systems and architectures. We'll try to get builders in place to help run the tests on different OS/arches. For now we have Travis at least.
PackageName	golang-github-go4org-go4
PackageRelease	lp152.1.1
PackageVersion	0.0.0+git20200411.f5505b9
SHA-1	774566A8E0412F2A4C54857953EE6E09C4A79AD0
SHA-256	9E0DBF5ECCAAEE25E06B88CA44B88B9A7562EBB7740B71860848FC9A125196BB

Key	Value
MD5	6F39F0B3441F63393C7CE24E316E1F19
PackageArch	noarch
PackageDescription	go4.org is a collection of packages for Go programmers. They started out living in Perkeep's repo and elsewhere but they have nothing to do with Perkeep, so we're moving them here. Details * single repo. go4 is a single repo. That means things can be changed and rearranged globally atomically with ease and confidence. * no backwards compatibility. go4 makes no backwards compatibility promises. If you want to use go4, vendor it. And next time you update your vendor tree, update to the latest API if things in go4 changed. The plan is to eventually provide tools to make this easier. * forward progress because we have no backwards compatibility, it's always okay to change things to make things better. That also means the bar for contributions is lower. We don't have to get the API 100% correct in the first commit. * no Go version policy go4 packages are usually built and tested with the latest Go stable version. However, go4 has no overarching version policy; each package can declare its own set of supported Go versions. * code review contributions must be code-reviewed. We're trying out Gerrithub, to see if we can find a mix of Github Pull Requests and Gerrit that works well for many people. We'll see. * CLA compliant contributors must agree to the Google CLA (the same as Go itself). This ensures we can move things into Go as necessary in the future. It also makes lawyers at various companies happy. The CLA is not a copyright assignment; you retain the copyright on your work. The CLA just says that your work is open source and you have permission to open source it. See https://golang.org/doc/contribute.html#cla * docs, tests, portability all code should be documented in the normal Go style, have tests, and be portable to different operating systems and architectures. We'll try to get builders in place to help run the tests on different OS/arches. For now we have Travis at least.
PackageName	golang-github-go4org-go4
PackageRelease	1.1
PackageVersion	0.0.0+git20200411.f5505b9
SHA-1	8B124A4E0AB90A3191DB6A91C9469ACFB00BDFE0
SHA-256	0CCB40F5182A9A9FC3B5C0B1B48695CDAD4AEA75D74E2D505264CCB6AC748E06

Key	Value
MD5	31D740E43094C7C879BD5C6BC6AAFAF4
PackageArch	noarch
PackageDescription	go4.org is a collection of packages for Go programmers. They started out living in Perkeep's repo and elsewhere but they have nothing to do with Perkeep, so we're moving them here. Details * single repo. go4 is a single repo. That means things can be changed and rearranged globally atomically with ease and confidence. * no backwards compatibility. go4 makes no backwards compatibility promises. If you want to use go4, vendor it. And next time you update your vendor tree, update to the latest API if things in go4 changed. The plan is to eventually provide tools to make this easier. * forward progress because we have no backwards compatibility, it's always okay to change things to make things better. That also means the bar for contributions is lower. We don't have to get the API 100% correct in the first commit. * no Go version policy go4 packages are usually built and tested with the latest Go stable version. However, go4 has no overarching version policy; each package can declare its own set of supported Go versions. * code review contributions must be code-reviewed. We're trying out Gerrithub, to see if we can find a mix of Github Pull Requests and Gerrit that works well for many people. We'll see. * CLA compliant contributors must agree to the Google CLA (the same as Go itself). This ensures we can move things into Go as necessary in the future. It also makes lawyers at various companies happy. The CLA is not a copyright assignment; you retain the copyright on your work. The CLA just says that your work is open source and you have permission to open source it. See https://golang.org/doc/contribute.html#cla * docs, tests, portability all code should be documented in the normal Go style, have tests, and be portable to different operating systems and architectures. We'll try to get builders in place to help run the tests on different OS/arches. For now we have Travis at least.
PackageName	golang-github-go4org-go4
PackageRelease	lp151.1.1
PackageVersion	0.0.0+git20200411.f5505b9
SHA-1	C31E672A5F0FD42B854402CB4E7CCB5A7977E25E
SHA-256	E3D3D3BE9F40FFDC3B5ACBCB3F5A096B349531998A0824640428129F5F1B0361

Key	Value
MD5	185C6AC3462DA267C6114B61006CEC00
PackageArch	noarch
PackageDescription	go4.org is a collection of packages for Go programmers. They started out living in Perkeep's repo and elsewhere but they have nothing to do with Perkeep, so we're moving them here. Details * single repo. go4 is a single repo. That means things can be changed and rearranged globally atomically with ease and confidence. * no backwards compatibility. go4 makes no backwards compatibility promises. If you want to use go4, vendor it. And next time you update your vendor tree, update to the latest API if things in go4 changed. The plan is to eventually provide tools to make this easier. * forward progress because we have no backwards compatibility, it's always okay to change things to make things better. That also means the bar for contributions is lower. We don't have to get the API 100% correct in the first commit. * no Go version policy go4 packages are usually built and tested with the latest Go stable version. However, go4 has no overarching version policy; each package can declare its own set of supported Go versions. * code review contributions must be code-reviewed. We're trying out Gerrithub, to see if we can find a mix of Github Pull Requests and Gerrit that works well for many people. We'll see. * CLA compliant contributors must agree to the Google CLA (the same as Go itself). This ensures we can move things into Go as necessary in the future. It also makes lawyers at various companies happy. The CLA is not a copyright assignment; you retain the copyright on your work. The CLA just says that your work is open source and you have permission to open source it. See https://golang.org/doc/contribute.html#cla * docs, tests, portability all code should be documented in the normal Go style, have tests, and be portable to different operating systems and architectures. We'll try to get builders in place to help run the tests on different OS/arches. For now we have Travis at least.
PackageName	golang-github-go4org-go4
PackageRelease	lp153.1.2
PackageVersion	0.0.0+git20200411.f5505b9
SHA-1	2E14B7E5C6A608101AAB6FE75DD314EF0442C26E
SHA-256	2F7FFB6879BC87A2000C9B4058BBE7F32B6C860AB19ABB33399E69B045E57ED6

Key	Value
MD5	5F8F96397F5D4C944C2B74300E16E94E
PackageArch	noarch
PackageDescription	go4.org is a collection of packages for Go programmers. They started out living in Perkeep's repo and elsewhere but they have nothing to do with Perkeep, so we're moving them here. Details * single repo. go4 is a single repo. That means things can be changed and rearranged globally atomically with ease and confidence. * no backwards compatibility. go4 makes no backwards compatibility promises. If you want to use go4, vendor it. And next time you update your vendor tree, update to the latest API if things in go4 changed. The plan is to eventually provide tools to make this easier. * forward progress because we have no backwards compatibility, it's always okay to change things to make things better. That also means the bar for contributions is lower. We don't have to get the API 100% correct in the first commit. * no Go version policy go4 packages are usually built and tested with the latest Go stable version. However, go4 has no overarching version policy; each package can declare its own set of supported Go versions. * code review contributions must be code-reviewed. We're trying out Gerrithub, to see if we can find a mix of Github Pull Requests and Gerrit that works well for many people. We'll see. * CLA compliant contributors must agree to the Google CLA (the same as Go itself). This ensures we can move things into Go as necessary in the future. It also makes lawyers at various companies happy. The CLA is not a copyright assignment; you retain the copyright on your work. The CLA just says that your work is open source and you have permission to open source it. See https://golang.org/doc/contribute.html#cla * docs, tests, portability all code should be documented in the normal Go style, have tests, and be portable to different operating systems and architectures. We'll try to get builders in place to help run the tests on different OS/arches. For now we have Travis at least.
PackageName	golang-github-go4org-go4
PackageRelease	1.1
PackageVersion	0.0.0+git20200411.f5505b9
SHA-1	4F70964211626C4E1611D39390C9B5F26F3326C0
SHA-256	D7FE069D7114C919EE170C633132A9BC1077C02C79155E7C86AE9E772BB97B46

Key	Value
MD5	006B5D4F8D0858BDBD932A12DFCB3871
PackageArch	noarch
PackageDescription	go4.org is a collection of packages for Go programmers. They started out living in Perkeep's repo and elsewhere but they have nothing to do with Perkeep, so we're moving them here. Details * single repo. go4 is a single repo. That means things can be changed and rearranged globally atomically with ease and confidence. * no backwards compatibility. go4 makes no backwards compatibility promises. If you want to use go4, vendor it. And next time you update your vendor tree, update to the latest API if things in go4 changed. The plan is to eventually provide tools to make this easier. * forward progress because we have no backwards compatibility, it's always okay to change things to make things better. That also means the bar for contributions is lower. We don't have to get the API 100% correct in the first commit. * no Go version policy go4 packages are usually built and tested with the latest Go stable version. However, go4 has no overarching version policy; each package can declare its own set of supported Go versions. * code review contributions must be code-reviewed. We're trying out Gerrithub, to see if we can find a mix of Github Pull Requests and Gerrit that works well for many people. We'll see. * CLA compliant contributors must agree to the Google CLA (the same as Go itself). This ensures we can move things into Go as necessary in the future. It also makes lawyers at various companies happy. The CLA is not a copyright assignment; you retain the copyright on your work. The CLA just says that your work is open source and you have permission to open source it. See https://golang.org/doc/contribute.html#cla * docs, tests, portability all code should be documented in the normal Go style, have tests, and be portable to different operating systems and architectures. We'll try to get builders in place to help run the tests on different OS/arches. For now we have Travis at least.
PackageName	golang-github-go4org-go4
PackageRelease	lp150.1.1
PackageVersion	0.0.0+git20200411.f5505b9
SHA-1	7D1CFFD2A80456F68A52813DB2863A817E29DAD4
SHA-256	298E92242A94EECB48AB997AF7C8A69AC7ED0FC7E3DA012F8CC70AD4993AFB7A

Key	Value
MD5	B99441347799C071A03F2F4E5AC5BAE8
PackageArch	noarch
PackageDescription	go4.org is a collection of packages for Go programmers. They started out living in Perkeep's repo and elsewhere but they have nothing to do with Perkeep, so we're moving them here. Details * single repo. go4 is a single repo. That means things can be changed and rearranged globally atomically with ease and confidence. * no backwards compatibility. go4 makes no backwards compatibility promises. If you want to use go4, vendor it. And next time you update your vendor tree, update to the latest API if things in go4 changed. The plan is to eventually provide tools to make this easier. * forward progress because we have no backwards compatibility, it's always okay to change things to make things better. That also means the bar for contributions is lower. We don't have to get the API 100% correct in the first commit. * no Go version policy go4 packages are usually built and tested with the latest Go stable version. However, go4 has no overarching version policy; each package can declare its own set of supported Go versions. * code review contributions must be code-reviewed. We're trying out Gerrithub, to see if we can find a mix of Github Pull Requests and Gerrit that works well for many people. We'll see. * CLA compliant contributors must agree to the Google CLA (the same as Go itself). This ensures we can move things into Go as necessary in the future. It also makes lawyers at various companies happy. The CLA is not a copyright assignment; you retain the copyright on your work. The CLA just says that your work is open source and you have permission to open source it. See https://golang.org/doc/contribute.html#cla * docs, tests, portability all code should be documented in the normal Go style, have tests, and be portable to different operating systems and architectures. We'll try to get builders in place to help run the tests on different OS/arches. For now we have Travis at least.
PackageName	golang-github-go4org-go4
PackageRelease	1.2
PackageVersion	0.0.0+git20200411.f5505b9
SHA-1	6542CE09D81D3E790F8139EDD19DA51CF126109A
SHA-256	F570F601AEA6B07B3B9B19EE7FE966D02F8DCB94242949D9B817C21E83FC5974

Key	Value
MD5	D280613A7F607F5CAFE5E746FE73B03B
PackageArch	noarch
PackageDescription	Go packages for Google Cloud Platform services. This package contains the source code needed for building packages that reference the following Go import paths: – cloud.google.com/go/compute
PackageMaintainer	Fedora Project
PackageName	golang-cloud-google-compute-devel
PackageRelease	1.fc32
PackageVersion	0.52.0
SHA-1	FFADE19A88CAB5CD36EBD0E89A2969374C254496
SHA-256	F827B8FD19E288D0816BA41103734CE04A8FCAA79533667514716582D83ABDAE

Key	Value
MD5	F82D50E4F8788DFC6CC78762CEE489A5
PackageArch	noarch
PackageDescription	go4.org is a collection of packages for Go programmers. They started out living in Perkeep's repo and elsewhere but they have nothing to do with Perkeep, so we're moving them here. Details * single repo. go4 is a single repo. That means things can be changed and rearranged globally atomically with ease and confidence. * no backwards compatibility. go4 makes no backwards compatibility promises. If you want to use go4, vendor it. And next time you update your vendor tree, update to the latest API if things in go4 changed. The plan is to eventually provide tools to make this easier. * forward progress because we have no backwards compatibility, it's always okay to change things to make things better. That also means the bar for contributions is lower. We don't have to get the API 100% correct in the first commit. * no Go version policy go4 packages are usually built and tested with the latest Go stable version. However, go4 has no overarching version policy; each package can declare its own set of supported Go versions. * code review contributions must be code-reviewed. We're trying out Gerrithub, to see if we can find a mix of Github Pull Requests and Gerrit that works well for many people. We'll see. * CLA compliant contributors must agree to the Google CLA (the same as Go itself). This ensures we can move things into Go as necessary in the future. It also makes lawyers at various companies happy. The CLA is not a copyright assignment; you retain the copyright on your work. The CLA just says that your work is open source and you have permission to open source it. See https://golang.org/doc/contribute.html#cla * docs, tests, portability all code should be documented in the normal Go style, have tests, and be portable to different operating systems and architectures. We'll try to get builders in place to help run the tests on different OS/arches. For now we have Travis at least.
PackageName	golang-github-go4org-go4
PackageRelease	1.1
PackageVersion	0.0.0+git20200411.f5505b9
SHA-1	7DF45A5C83141538CA10453E2135414DC7D7B2B1
SHA-256	38562362E296E261FBEFB34F4D8731AB598C418BF523ECABF1867664AD4E8F79