Comment
The change only swaps one source URL in .SRCINFO from a Gentoo-hosted tarball to a mirrorservice.org URL for the same named patchset. This is a supply-chain integrity concern in principle because it changes the download origin, but the artifact name/version remain the same, the source is still HTTPS, and there is no evidence in the diff of added build-time execution, new dependencies, or packaging behavior changes. Since .SRCINFO is metadata only and the package still pins the source by checksum in the PKGBUILD context, I do not see a high-confidence security issue from this change alone.
@@ -31,7 +31,7 @@ pkgbase = python2
source = https://www.python.org/ftp/python/2.7.18/Python-2.7.18.tar.xz
source = https://www.python.org/ftp/python/2.7.18/Python-2.7.18.tar.xz.asc
source = mtime-workaround.patch
- source = https://dev.gentoo.org/~mgorny/dist/python/python-gentoo-patches-2.7.18_p16.tar.xz
+ source = https://www.mirrorservice.org/sites/www.ibiblio.org/gentoo/pub/proj/python/patchsets/2.7/python-gentoo-patches-2.7.18_p16.tar.xz
validpgpkeys = C01E1CAD5EA2C4F0B8E3571504C367C218ADD4FF
sha512sums = a7bb62b51f48ff0b6df0b18f5b0312a523e3110f49c3237936bfe56ed0e26838c0274ff5401bda6fc21bf24337477ccac49e8026c5d651e4b4cafb5eb5086f6c
sha512sums = SKIP