Add custom upload type for package meta-data
Bug #595038 reported by
Julian Edwards
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Julian Edwards |
Bug Description
For the Software Center, we need to take an additional custom upload file during upload that will store a package's meta-data for display in the SC. The format of this file is irrelevant to Soyuz, it will simply be published somewhere, like translations files.
Related branches
lp:~julian-edwards/launchpad/metadata-type-bug-595038
- Jelmer Vernooij (community): Approve (code)
-
Diff: 179 lines (+133/-0)5 files modifiedlib/lp/archivepublisher/tests/publishing-meta-data-files.txt (+65/-0)
lib/lp/archiveuploader/nascentuploadfile.py (+2/-0)
lib/lp/archiveuploader/tests/meta-data-custom-files.txt (+21/-0)
lib/lp/soyuz/interfaces/queue.py (+18/-0)
lib/lp/soyuz/model/queue.py (+27/-0)
lp:~julian-edwards/launchpad/metadata-fix2-bug-595038
- Jonathan Lange (community): Approve
-
Diff: 25 lines (+2/-2)2 files modifiedlib/lp/archiveuploader/nascentuploadfile.py (+1/-1)
lib/lp/archiveuploader/tests/meta-data-custom-files.txt (+1/-1)
Changed in soyuz: | |
status: | Triaged → In Progress |
Changed in soyuz: | |
status: | In Progress → Fix Committed |
tags: | added: qa-ok |
tags: |
added: qa-ok removed: qa-needstesting |
tags: |
added: qa-ok removed: qa-needstesting |
Changed in soyuz: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
The current thought is to publish the meta data file(s) in a location like:
https:/ /private- ppa.launchpad. net/soyuz- team/meta/<ppa_name> /<meta- data-file- name>
When the Software Centre queries Launchpad to get a list of commercial PPAs, we'll make sure there's also a way of discovering the file meta-data names (although it always has the option of a directory listing).