I added a ton of things, and there's always more that could be added, so it's about priorities. And frankly how I feel like, this is not my job and I don't use Chrome, either, so I can't say I feel motivated.
Also I don't think it's that trivial. We're currently using Synaptic for the manual refresh, and I don't think it can handle that error. So all we get back is the error message. Which I assume is localized and thus not easily usable. To even look into this further I guess I'd have to create a local repository to build a test case to see what exactly we get back. And then a GUI would have to be added to handle this, I'd have to figure out how to actually handle this (I don't think it can even be handled other than during a refresh because you need to be overwriting old repo info with the new one - so basically I'd either need to patch Synaptic or create my own refresh dialog). The GUI would need a bunch of new strings which all would need to get translated by other volunteers into all the supported languages (including Klingon and I don't know what because some people have too much time on their hands apparently
). And maybe we'd want to backport it to the 3 other supported releases, further increasing the work load.
So basically you can take your
rene wrote: ⤴
Sun Dec 02, 2018 2:24 pm
possible/trivial to do
and stick to you know where.