Package: reportbug
Severity: wishlist
I have been working on an enhancement[1] to reportbug that would allow
interactive selection of port/arch usertags[2] and automatically set
them in code paths that currently already ask for an architecture.
I could use some design advice around the data for this.
Currently the canonical definitions of the tags is the wiki page. The
reportbug patchset has a function to convert the wiki page to Python
objects. Then the reportbug code has a copy of the autogenerated Python
objects. However, in keeping with the spirit of what I wrote on [3],
I intend to switch that to storing a full copy of the raw source for
the wiki page in the reportbug source and then doing the conversion
at build time. There is similar data needed from [4] and [5].
Since the copy of the data in reportbug would get outdated, I was
thinking to download new copies when in online mode, cache them locally
and then use them in preference to the copy in the reportbug package.
This would happen only for code paths that do arch selection of course.
Does this feature and approach to data caching sound reasonable?
1. https://salsa.debian.org/pabs/reportbug/-
/compare?from=master&to=arch-usertags
2. https://wiki.debian.org/Teams/Debbugs/ArchitectureTags
3. https://wiki.debian.org/AutoGeneratedFiles
4. https://salsa.debian.org/webmaster-team/webwml/-
/raw/master/english/releases/arches.data
5. The 'vancouvered' column in the buildd database, currently only
at postgresql://udd-mirror:udd-mirror@udd-mirror.debian.net/udd
--
bye, pabs https://wiki.debian.org/PaulWise
Attachment:
signature.asc
Description: This is a digitally signed message part