> This was fixed A LONG time ago, so you are basically arguing over outdated code.
I did say that we can cherry-pick the fix once it is upstream. If someone can volunteer to provide a fix for that, we can land the fix both development and stable releases of Ubuntu and the problem will be permanently gone.
> In my strict personal opinion, in this case the bug is a showstopper for users, so a package rebuild is appropriate.
No, a cherry-pick of the actual proper fix is appropriate.
There's no point arguing over anything. The route to a proper fix is clear and I described it many comments ago. If someone can volunteer to prepare that, then great.
> This was fixed A LONG time ago, so you are basically arguing over outdated code.
I did say that we can cherry-pick the fix once it is upstream. If someone can volunteer to provide a fix for that, we can land the fix both development and stable releases of Ubuntu and the problem will be permanently gone.
> In my strict personal opinion, in this case the bug is a showstopper for users, so a package rebuild is appropriate.
No, a cherry-pick of the actual proper fix is appropriate.
There's no point arguing over anything. The route to a proper fix is clear and I described it many comments ago. If someone can volunteer to prepare that, then great.