Comment 5 for bug 1862764

Revision history for this message
Ashley Waite (phidaissi) wrote :

The 'signed-by' field is not supported in the python-apt classes that are used by add-apt-repository and the gui software-properties.

- When adding a new source there's no argument to provide 'signed-by' or 'trusted' options, so those cannot be added via add-apt-repository or the gui software-properties until that is corrected, and this omission appears to exist upstream:
https://git.launchpad.net/python-apt/tree/aptsources/sourceslist.py#n309

- Adding 'signed-by' to the output of the sources so it gets written to the sources list would be needed:
https://git.launchpad.net/python-apt/tree/aptsources/sourceslist.py#n232

- And then it'll get ignored when subsequently reading the sources list, as any option fields present other than 'arch' and 'trusted' result in the line being flagged as invalid, this results in the source not being listed in the software-properties sources list - and that's actually how I ended up here trying to work out if that failure to display had been reported as a bug yet.
So that too needs to be updated:
https://git.launchpad.net/python-apt/tree/aptsources/sourceslist.py#n196

These three changes all appear to be upstream, and navigating the debian site was not as straight forward as here, so I'm not really clear on where to submit a patch to make it happen, nor how easy it would be to pull back here, so I figured I could throw the details here for someone that's more familiar with that!