I have QA'd this on dogfood by creating a new distroseries for Ubuntu, called nobby, and after doing some surgery on maverick (emptying queues, and disabling pending builds), I ran 'scripts/ftpmaster-tools/initialise-from-parent.py -a i386,amd64,powerpc,sparc nobby'.
The initialise-from-parent script no longer copies PARTNER packages either.
With one small database permission caveat that I have prepared a branch for, everything looks to have been copied fine.
Looking at the nobby distroseries page after initialisation showed me that the packaging links had been copied. After running 'cronscripts/update-pkgcache.py', the nobby distroseries page showed package counts and everything else expected.
I have verified that source packages, binary packages, packagesets and their related archivepermissions have been copied from maverick to nobby via SQL.
I have also had Julian check the new distroseries, and he agrees it has been initialised correctly.
I have QA'd this on dogfood by creating a new distroseries for Ubuntu, called nobby, and after doing some surgery on maverick (emptying queues, and disabling pending builds), I ran 'scripts/ ftpmaster- tools/initialis e-from- parent. py -a i386,amd64, powerpc, sparc nobby'.
The initialise- from-parent script no longer copies PARTNER packages either.
With one small database permission caveat that I have prepared a branch for, everything looks to have been copied fine.
Looking at the nobby distroseries page after initialisation showed me that the packaging links had been copied. After running 'cronscripts/ update- pkgcache. py', the nobby distroseries page showed package counts and everything else expected.
I have verified that source packages, binary packages, packagesets and their related archivepermissions have been copied from maverick to nobby via SQL.
I have also had Julian check the new distroseries, and he agrees it has been initialised correctly.