AFAICS, this will affect any (delayed) copy where the source package release component has been overridden from a component not in the distroseries.upload_components.
The issue is that, for delayed copies, the component is not yet overridden when the PackageUpload is accepted, as it does not yet have a publishing history. The check that is happening during acceptFromCopy() ends up at PackageUploadSource.checkComponentAndSection() which currently only considers the SourcePackageRelease.
So, I plan to add a caveat to PackageUploadSource.checkComponentAndSection() that will, for delayed copies, use the component from the (soon-to-be) ancestry, rather than the SPR.
Pre-implementation notes:
AFAICS, this will affect any (delayed) copy where the source package release component has been overridden from a component not in the distroseries. upload_ components.
The issue is that, for delayed copies, the component is not yet overridden when the PackageUpload is accepted, as it does not yet have a publishing history. The check that is happening during acceptFromCopy() ends up at PackageUploadSo urce.checkCompo nentAndSection( ) which currently only considers the SourcePackageRe lease.
So, I plan to add a caveat to PackageUploadSo urce.checkCompo nentAndSection( ) that will, for delayed copies, use the component from the (soon-to-be) ancestry, rather than the SPR.