PPA copy package ought to allow viewing multiple pages of results

This bug had a serious impact on me today. I was copying a large quantity of packages from a team's testing ppa to the team's release ppa. I selected all of the packages that came up on the copy page (thinking that it was listing all of them). I then proceeded to copy them to the team's release ppa. The issue was, not all of the packages in the ppa were copied (because they were not all displayed). This caused problems when people went to install the packages from the release ppa, because not all of the dependencies were available.

I later tried to go back and use the filter approach to copy the missing packages. This also caused an issue. I thought that Launchpad would remember which packages I had selected even if I updated the filter. It turns out that this was not the case. As a result, in order to get the remaining packages copied, I had to filter and copy them one by one to the other ppa.

Nathan,

ACK, this bug hits you hard on mass-copy operations. While we don't come with a solution for this you could try to use the launchpad API for copying multiple sources.

{{{
    ubuntu = launchpad.distributions['ubuntu']
    distroseries_name = 'intrepid'
    from_archive = launchpad.people[<from_ppa_ownername>].archive
    to_archive = launchpad.people[<to_ppa_ownername>].archive

    print 'Copying from %s in %s to %s' % (
        distroseries_name, from_archive.title, to_archive.title)

    copy_result = to_archive.syncSources(
        source_names=[<sourcename_one>, ...],
        from_archive=from_archive,
        to_pocket='release',
        to_series=distroseries_name,
        include_binaries=True,
        )

    print copy_result
}}}

I will copy the latest version of the sources listed from one PPA to another. Check the launchpad API docs at https://help.launchpad.net/API. It might help you to automate some of the work as well.

We sincerely apologize for the trouble this is issue is causing.

Err, ignore the 'ubuntu = ...' line in the code snippet. It's not necessary.

RF 7760.

Now the pages are batched. This fixes the original problem. Note, selections are not remembered across batches. We can add a JS warning when there is a selection made and the next/previous page-link is clicked. That may be the most practical solution at this point, to the subsequent issue experienced by Nathan?