Merge lp:~laney/ubuntu-archive-publishing/updates into lp:ubuntu-archive-publishing
Status: | Needs review |
---|---|
Proposed branch: | lp:~laney/ubuntu-archive-publishing/updates |
Merge into: | lp:ubuntu-archive-publishing |
Prerequisite: | lp:~laney/ubuntu-archive-publishing/more-options |
Diff against target: |
205 lines (+65/-23) 2 files modified
lib/scripts/generate_extra_overrides.py (+21/-9) tests/test_generate_extra_overrides.py (+44/-14) |
To merge this branch: | bzr merge lp:~laney/ubuntu-archive-publishing/updates |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Colin Watson | Pending | ||
Ubuntu Package Archive Administrators | Pending | ||
Review via email:
|
Description of the change
Run for -updates. I'm not really sure of all the consequences here, maybe consider this as a basis for discussion initially.
Unmerged revisions
- 116. By Iain Lane
-
generate_
extra_overrides : Germinate for stable releases too Currently we only generate for the release pocket of -devel releases.
This means that Task headers don't get updated for SRUs meaning that,
for example, it's not easily possible to add new packages to the live
seed (other seeds are OK because they get pulled in by Depends of the
metapackage).Germinate for -updates, and for stable releases. When generating
overrides for stable releases, write overrides to -updates.This is not a full solution. The immutable nature of release pockets
means that some things can't work properly, for example- dependencies of the new package which aren't in -updates won't get
Task entries
- *dropping* things from seeds can't work properly, at least not
without care from consuming code to have -updates dominate release;
a simple grep-dctrl will not do
I support this change. How to best test this?