Parents (Total: 5)

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

Key	Value
MD5	7ED02643408C80C6B87C55933F3BF4FD
PackageArch	noarch
PackageDescription	This package contains code which implements the Kubernetes "apply" operation. This package contains the source code needed for building packages that reference the following Go import paths: – sigs.k8s.io/structured-merge-diff
PackageMaintainer	umeabot <umeabot>
PackageName	golang-sigs-k8s-structured-merge-diff-devel
PackageRelease	2.mga9
PackageVersion	4.2.1
SHA-1	80DE8AB1A93FE9D31CCD014395B43E9D698BC05B
SHA-256	25465089A96CBECDD456B80FD3CED095BA753FF34BB888992DCC757B37735A70

Key	Value
FileSize	116408
MD5	55239887437239F513E120E21BDE0454
PackageDescription	implementation for "server-side apply" (library) What is the apply operation? . It models resources in a control plane as having multiple "managers". Each manager is typically trying to manage only one aspect of a resource. The goal is to make it easy for disparate managers to make the changes they need without messing up the things that other managers are doing. In this system, both humans and machines (aka "controllers") act as managers. . To do this, it explicitly tracks (using the fieldset data structure) which fields each manager is currently managing. . Now, there are two basic mechanisms by which one modifies an object. . PUT/PATCH: This is a write command that says: "Make the object look EXACTLY like X". . APPLY: This is a write command that says: "The fields I manage should now look exactly like this (but I don't care about other fields)". . For PUT/PATCH, it deduces which fields will be managed based on what is changing. For APPLY, the user is explicitly stating which fields they wish to manage (and therefore requesting deletion of any fields that they used to manage but stop mentioning). . Any time a manager begins managing some new field, that field is removed from all other managers. If the manager is using the APPLY command, it calls these conflicts, and will not proceed unless the user passes the "force" option. This prevents accidentally setting fields which some other entity is managing. . PUT/PATCH always "force". They are mostly used by automated systems, which won't do anything productive with a new error type.
PackageMaintainer	Debian Go Packaging Team <team+pkg-go@tracker.debian.org>
PackageName	golang-k8s-sigs-structured-merge-diff-dev
PackageSection	devel
PackageVersion	4.0.2+ds1-2
SHA-1	C6BA04E321760C2D10F5C3D220FD7573F18600A3
SHA-256	871B2DD766A472B69D3F5871578633B1FF72E9A13246BE487C6AFF8C561FB04F

Key	Value
MD5	199675B74DD5F7EEA8EDC18975E01ADC
PackageArch	noarch
PackageDescription	This package contains code which implements the Kubernetes "apply" operation. This package contains the source code needed for building packages that reference the following Go import paths: – sigs.k8s.io/structured-merge-diff
PackageMaintainer	Fedora Project
PackageName	golang-sigs-k8s-structured-merge-diff-devel
PackageRelease	2.fc34
PackageVersion	4.0.2
SHA-1	5B48EC7DC82AB322BC581C7E01F69DAC86B0A77B
SHA-256	E9875435CBB429656EAACA3A0F319CBB12BAE46A54C46108F051CD7293FAE490

Key	Value
FileSize	121920
MD5	8EA5CEF057336C28C9616EDED71B9E5C
PackageDescription	implementation for "server-side apply" (library) What is the apply operation? . It models resources in a control plane as having multiple "managers". Each manager is typically trying to manage only one aspect of a resource. The goal is to make it easy for disparate managers to make the changes they need without messing up the things that other managers are doing. In this system, both humans and machines (aka "controllers") act as managers. . To do this, it explicitly tracks (using the fieldset data structure) which fields each manager is currently managing. . Now, there are two basic mechanisms by which one modifies an object. . PUT/PATCH: This is a write command that says: "Make the object look EXACTLY like X". . APPLY: This is a write command that says: "The fields I manage should now look exactly like this (but I don't care about other fields)". . For PUT/PATCH, it deduces which fields will be managed based on what is changing. For APPLY, the user is explicitly stating which fields they wish to manage (and therefore requesting deletion of any fields that they used to manage but stop mentioning). . Any time a manager begins managing some new field, that field is removed from all other managers. If the manager is using the APPLY command, it calls these conflicts, and will not proceed unless the user passes the "force" option. This prevents accidentally setting fields which some other entity is managing. . PUT/PATCH always "force". They are mostly used by automated systems, which won't do anything productive with a new error type.
PackageMaintainer	Debian Go Packaging Team <team+pkg-go@tracker.debian.org>
PackageName	golang-k8s-sigs-structured-merge-diff-dev
PackageSection	devel
PackageVersion	4.1.2+ds1-1
SHA-1	3B9CEF2188175AABC2822A8286ACFAAB1AF7B8BC
SHA-256	22F38F870A63BFAED0686C9F37652D420C195231ECDBD97B076567705659FD90

Key	Value
FileSize	116452
MD5	D6082ED60CC1DC4409149F47943926E4
PackageDescription	implementation for "server-side apply" (library) What is the apply operation? . It models resources in a control plane as having multiple "managers". Each manager is typically trying to manage only one aspect of a resource. The goal is to make it easy for disparate managers to make the changes they need without messing up the things that other managers are doing. In this system, both humans and machines (aka "controllers") act as managers. . To do this, it explicitly tracks (using the fieldset data structure) which fields each manager is currently managing. . Now, there are two basic mechanisms by which one modifies an object. . PUT/PATCH: This is a write command that says: "Make the object look EXACTLY like X". . APPLY: This is a write command that says: "The fields I manage should now look exactly like this (but I don't care about other fields)". . For PUT/PATCH, it deduces which fields will be managed based on what is changing. For APPLY, the user is explicitly stating which fields they wish to manage (and therefore requesting deletion of any fields that they used to manage but stop mentioning). . Any time a manager begins managing some new field, that field is removed from all other managers. If the manager is using the APPLY command, it calls these conflicts, and will not proceed unless the user passes the "force" option. This prevents accidentally setting fields which some other entity is managing. . PUT/PATCH always "force". They are mostly used by automated systems, which won't do anything productive with a new error type.
PackageMaintainer	Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageName	golang-k8s-sigs-structured-merge-diff-dev
PackageSection	devel
PackageVersion	4.0.2+ds1-2
SHA-1	83602751405893F9FB378AEC58AD38528AC0ED7F
SHA-256	6C8E8BE703229C5CDCB0E8FF81397F9F55B964C85DAAEA8EF9A75F64AD68569D