Launchpad itself

Copy from PPA with binaries evades NEW and puts new packages in their default component

Bug #993120 reported by Martin Pitt on 2012-05-02
16
This bug affects 1 person
Affects Status Importance Assigned to Milestone
​ Launchpad itself
In Progress
High
Colin Watson
Also affects project (?) Also affects distribution/package Nominate for series

Bug Description

We regularly copy kernels from the kernel team PPA to -proposed. Whenever there is an ABI bump, i. e. the source packages build binary packages with a new name, these new packages are technically binary NEW for Ubuntu. But the syncs generated by

  ubuntu.getArchive(name='primary').copyPackage(from_archive=kernel_ppa, ...)

only land in unapproved, and all binaries are automatically accepted into universe. It would be better if these syncs would land in NEW, from where any archive admin or SRU team member could override them to main. Right now we require a person who can ssh to cocoplum to run change-override.py to move the binaries from universe to main.

Related branches

lp:~cjwatson/launchpad/copies-respect-new
On hold for merging into lp:launchpad
William Grant: Approve (code) on 2014-05-30
Diff: 146 lines (+67/-8)
3 files modified
lib/lp/soyuz/configure.zcml (+1/-2)
lib/lp/soyuz/model/packagecopyjob.py (+27/-6)
lib/lp/soyuz/tests/test_packagecopyjob.py (+39/-0)
Colin Watson (cjwatson) wrote :

I agree - I think NEWness should be determined relative to the archive you're copying into.

Laura Czajkowski (czajkowski) on 2012-05-02
Changed in launchpad:
status: New → Triaged
importance: Undecided → High
Julian Edwards (julian-edwards) on 2012-05-04
tags: added: derivation
William Grant (wgrant) on 2012-10-15
tags: added: package-copies
Colin Watson (cjwatson) on 2014-05-29
Changed in launchpad:
status: Triaged → In Progress
assignee: nobody → Colin Watson (cjwatson)
William Grant (wgrant) on 2014-07-22
tags: added: package-overrides
Adam Conrad (adconrad) wrote :

The "and puts packages in universe" part of this bug has been more or less fixed with binaries now defaulting to the component of their source. That said, copies bypassing binary NEW is still a bug.

summary: - Copy from PPA with binaries evades NEW and puts new packages into
- universe
+ Copy from PPA with binaries evades NEW and puts new packages in their
+ default component
Dmitry Shachnev (mitya57) wrote :

There is also an issue when in PPA, you can build a package from main against a package from universe, then binary copy both to archive, and both will be accepted.

A recent example is bug 1428162, which was noticed after the package was uploaded and accepted.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.
Subscribing...

Other bug subscribers