Add xz-compressed archive indexes
Bug #1517510 reported by
Colin Watson
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Colin Watson |
Bug Description
We currently only provide {Packages,
Related branches
lp:~cjwatson/charms/trusty/ubuntu-repository-cache/xz-indexes
- Review Queue (community): Needs Fixing (automated testing)
- James Page: Needs Resubmitting
-
Diff: 12 lines (+1/-1)1 file modifiedtemplates/apache2/archive_ubuntu_com.conf (+1/-1)
lp:~cjwatson/launchpad/xz-indexes
- William Grant (community): Approve (code)
-
Diff: 1108 lines (+318/-50)15 files modifiedlib/lp/archivepublisher/model/ftparchive.py (+19/-6)
lib/lp/archivepublisher/publishing.py (+7/-5)
lib/lp/archivepublisher/tests/apt-data/apt.conf (+90/-3)
lib/lp/archivepublisher/tests/apt-data/apt_conf_single_empty_suite_test (+15/-3)
lib/lp/archivepublisher/tests/test_ftparchive.py (+1/-1)
lib/lp/archivepublisher/tests/test_publisher.py (+44/-8)
lib/lp/archivepublisher/tests/test_repositoryindexfile.py (+41/-10)
lib/lp/archivepublisher/utils.py (+32/-10)
lib/lp/registry/configure.zcml (+2/-1)
lib/lp/registry/interfaces/distroseries.py (+10/-1)
lib/lp/registry/model/distroseries.py (+25/-0)
lib/lp/registry/tests/test_distroseries.py (+15/-1)
lib/lp/soyuz/enums.py (+15/-1)
setup.py (+1/-0)
versions.cfg (+1/-0)
tags: | added: feature soyuz-publish |
Changed in launchpad: | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → Colin Watson (cjwatson) |
To post a comment you must log in.
I've proposed merges to (I believe) all the relevant bits of infrastructure which need to be changed first. The relevant internal RT ticket is https:/ /portal. admin.canonical .com/86477.
We should also think about whether this applies to old series, or just >= xenial; my instinct is the latter, not least because we'd want to drop .bz2 fairly soon afterwards and that seems excessively intrusive for old series. But continuing to widen DistroSeries with even more boolean columns seems messy. How about perhaps adding a publishing_options (or similar) JSON column? We could then turn backports_ not_automatic and include_ long_descriptio ns into properties using that; those are only used by the DistroSeries webservice export, InitializeDistr oSeries, and the publisher, and there's no need for them to be indexed or anything. That would make it easy to configure this kind of feature for this case and for the future.