Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Cause: Using the errata.clone() api to clone a specific errata to a cloned/custom channel would create a search through all packages belonging to an errata from all channels. Consequence: The correct packages would be added, as well as packages from different channels with the same name and architecture as the ones from the cloned channel. Fix: The search no longer looks through unrelated channels Result: Only the correct packages are added
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -4,4 +4,7 @@ Fix: The search no longer looks through unrelated channels -Result: Only the correct packages are added+Result: Only the correct packages are added + + +Using the errata.clone() API to clone a specific errata to a cloned or custom channel would create a search through all packages belonging to the errata from all channels. In this case, the correct packages would be added, as well as packages from different channels with the same name and architecture as the ones from the cloned channel. The search no longer looks through unrelated channels, and only the correct packages are added.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,10 +1,3 @@ -Cause: Using the errata.clone() api to clone a specific errata to a cloned/custom channel would create a search through all packages belonging to an errata from all channels. +Using the errata.clone() API to clone a specific errata to a cloned or custom channel would create a search through all packages belonging to the errata from all channels. In this case, the correct packages would be added, as well as packages from different channels with the same name and architecture as the ones from the cloned channel. The search no longer looks through unrelated channels, and only the correct packages are added. -Consequence: The correct packages would be added, as well as packages from different channels with the same name and architecture as the ones from the cloned channel. +Revision 0-4- -Fix: The search no longer looks through unrelated channels - -Result: Only the correct packages are added - - -Using the errata.clone() API to clone a specific errata to a cloned or custom channel would create a search through all packages belonging to the errata from all channels. In this case, the correct packages would be added, as well as packages from different channels with the same name and architecture as the ones from the cloned channel. The search no longer looks through unrelated channels, and only the correct packages are added.