On Fri, Oct 31, 2008 at 03:52:31PM +0100, Andreas Barth wrote:
> 1. Currently, the submitter claims that the bug is serious, the
> maintainer don't think so, and there is no decision by the release team
> yet. So the current state of the bug isn't serious, but important.
ie, the views (on serious severity) are prioritised as:
- submitter's (default)
- maintainer's (can override submitter, and in this case does)
- release team's (can override maintainer and submitter)
- tech-ctte (can override all three of the above)
- general resolution (likewise)
> 2. As per constitution, we (the tech ctte) only makes decision as last
> resort. So currently, the next step would be for anyone who disagrees
> with this bug not being release critical to ask the release team to
> review the decision and maybe overrule it.
I'm not sure I'd want the release team to be able to stop the tech-ctte
from being involved simply by not making a decision, so I'm not sure I
agree with this precisely. But in the general case, yes, I'd rather see
the release team making the call on this.
> tech ctte members, any opinion from you on that?
Basically, +1.
On a technical level, it seems to me there's two aspects:
(1) can a package in main include a script that gets stuff from some
random website really be considered DFSG-free/policy-compliant?
(2) should we make sure that the stuff on the random website is also
available from somewhere in Debian, in case the random website gets
shut down, etc?
(1) seems to be resolved as per Andi's comments, but I kind-of think
(2) is actually the more important issue, and that the stuff getting
downloaded should probably be packaged for non-free and possibly volatile,
in order to remove the external dependency. The package in main would
then get a "Suggests: foo2zjs-nonfree-drivers", and if the script gets
moved to contrib, that could then become "Suggests: foo2zjs-nf-d |
foo2zj-nf-d-getter-script". That assumes someones willing to do the
legwork of packaging the drivers, of course, which might require
negotiating permission to redistribute them from whoever owns them.
Cheers,
aj
Attachment:
signature.asc
Description: Digital signature