Am Mittwoch, den 17.02.2021, 15:21 -0500 schrieb Robert Edmonds: > Markus Koschany wrote: [...] > > Please feel free to reassign and/or adjust the bug report as necessary. > > I get the following error message from the BTS. Do I need to do > "reassign 982671 unbound1.9" instead? I also got some error messages but it seems the bug reports are now reassigned to src:unbound1.9. The errors are probably related to the fact that the source package only and ever existed in Stretch > OK. I understand the src:unbound1.9 package in stretch does not support > the Python bindings. Does LTS intend to continue supporting the embedded > Python scripting support in the src:unbound1.9 package's daemon? I'd prefer to not change anything of the existing src:unbound1.9 package. So if users want to create their own python modules we don't need to remove the -- with-pythonmodule configuration option because this should not conflict with existing packages in my opinion. But since we can't foresee all possible corner cases, then I would say, use this feature at your own risk. Currently only the unbound daemon as it is shipped by upstream is our main support goal. Regards, Markus
Attachment:
signature.asc
Description: This is a digitally signed message part