Copy from PPA with binaries evades NEW and puts new packages in their default component
Bug #993120 reported by
Martin Pitt
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
In Progress
|
High
|
Colin Watson |
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.
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
- William Grant (community): Approve (code)
-
Diff: 146 lines (+67/-8)3 files modifiedlib/lp/soyuz/configure.zcml (+1/-2)
lib/lp/soyuz/model/packagecopyjob.py (+27/-6)
lib/lp/soyuz/tests/test_packagecopyjob.py (+39/-0)
Changed in launchpad: | |
status: | New → Triaged |
importance: | Undecided → High |
tags: | added: derivation |
tags: | added: package-copies |
Changed in launchpad: | |
status: | Triaged → In Progress |
assignee: | nobody → Colin Watson (cjwatson) |
tags: | added: package-overrides |
To post a comment you must log in.
I agree - I think NEWness should be determined relative to the archive you're copying into.