Derived Distros Testing

You need four roles/users:

1. A distro owner
2. A distro driver
3. A distro uploader
4. A distro archive admin

The distro owner needs to add the archive admin to the QUEUE_ADMIN users using the API call IArchive.newQueueAdmin(), and add the uploader using either newComponentUploader() or newPackageUploader()

Initialisation

[1] Single parent

• [1] New distro/series. Single parent from Ubuntu, i386, any packagesets, copy binaries.
• [2] Existing series. Keep existing parents/architectures. No packagesets selected. Copy Binaries. (This is the Ubuntu use case)
• [3] Existing series. Change parent. Same architectures. No packagesets selected. Copy Binaries.
• [4] New distro/series. Single parent from Ubuntu, i386, one small packageset, rebuild binaries.

[2] Multi-parents

Don't use 2 parents from the same distro, you need to make a new distro for each parent.

• [1] New distro/series. Multi parents, i386, different packagesets from each parent, copy binaries.
• [1] New distro/series. Multi parents, i386, choose packagesets from each parent that have common packages, copy binaries.
• [2] Existing series. Keep existing parents/arches/packagesets, copy binaries.
• [3] Existing series. Change parents. Same arches/packagesets. copy binaries

Visualisation

[3] Single parent

• [1] Check the distroseries page for each of the new distroseries in [1][1-4] above - make sure the new portlet is accurate and other info on the page.
• [2] Check each of +localpackagediffs, +missingpackages and +uniquepackages for each of [1] and [2] above.
• [3] As a normal user, you should not see the checkboxes on the left and the sync button at the bottom. When logged in as someone who can upload any package, you should see those.

[4] Multi-parents

• [1] Check the distroseries page for each of the new distroseries in [2][1-3] above. It should mention each parent.
• [2] Check each of the diff pages. Packages only in one parent will have a "resolved" entry in +localpackagediffs and another entry for the other parent in +uniquepackages.

[5] General

• [1] Filter on a packageset name using the text box
• [2] Filter on a packageset name using the table header
• [3] Filter on package changed-by
• [4] Use the API to find differences (IDistroSeries.getDifferencesTo() method)
• [5] Comment on a difference
• [6] Change a difference's "ignored" status.
• [7] Use the API to download comments. (left as an exercise to find out how to do this)
• [8] Get debdiffs from the last common version.

[6] Syncing

• [1] Find a package in +localpackagediffs and click "sync selected packages ..." at the bottom. Check that "Synchronizing" appears next to the package name.
• [2] When the copy job runs expect that:
  • The package is pending publication in the child series
  • An email is sent to the person who synced
  • An email is sent to the changes list, with the From: as the person who synced
  • "Synchronizing..." changes to "Updating ..."
• [3] Find a package in +missingpackages and click "sync selected packages ..." at the bottom. When the copy job runs expect that:
  • The package waits in the NEW queue
• [4] Approve the package in the NEW queue and wait for the package copy copy to re-run.
  • The package should now be in DONE
  • The package should be pending publication
  • The package should be on +localpackagediffs as a resolved difference (eventually)
• [5] Repeat [3] but this time set overrides before accepting. Check that the package is published with the overridden details (component/section).
• [6] Repeat [3] but reject the package. Make sure the queue item moves to REJECTED and the diffs page does not show the "Synchronizing..." any more. Check that the package is not copied to the distroseries.
• [7] Sync a package using the IArchive.copyPackage() API call. Expect the same results as in [6][2]
• [8] Sync a package using the IArchive.copyPackages() API call. A mass sync will occur and no emails are sent.