30.04.2015 08:03, Joao Luis Meloni Assirati wrote: > On 30-04-2015 01:29, Michael Tokarev wrote: > >> I don't have brazillian keyboard, I don't have a way to verify this. > > This is no excuse.
I don't ask for an excuse really, thank you. >> The best way to go from here is to let upstream to accept the needed >> change, this way it will be in debian automatically. > > Well, it is certainly the best way for someone. It is not the best way for me > and all brazilian users, as we have been applying this patch for years: It is the best way for everyone, to finally stop people applying local patches. I don't see what you're arguing against. > Upstream acknowledges this bug since 2012: > https://bugs.launchpad.net/qemu/+bug/1038136 A bugreport filed against upstream does not mean upstream acknowleges it or that upstream ever seen it. No one from qemu team made any comment in there. But it doesn't matter, I merely corrected your claim, it does not change the fact that the problem exists. Note that I know well enough everything you quoted, because it was me who changed attributes of your duplicate bugreport to point to the upstream bugtracker. > but does not solve this 1 (one) line problem. On the other hand, Debian > usually applies patches to solve bugs that eventually are adopted by upstream > so I do not see why this could not be the case given that Jessie was just > released and we will have two years of Debian unstable development from now. And before applying, I need to hear reaction from someone who actually understands how the table which is being patches is used, and why it is used this way. We had enough "fixes" which broke some other setups, or plain wrong features rejected by upstream for good reason but which we had to support for years because users relied on them. The best info about this prob is present at http://blog.nielshorn.net/2011/03/qemu-and-brazilian-keyboards/ , and that post talks about several issues there, while the patch you're talking about addresses only one. This is exactly why I said the best is to talk with the upstream. Apparently it is not as good for you as whining at debian maintainers. And this is exactly what I actually did, pinging the developers after you submitted this bug report, effectively reminding me about this problem again, http://thread.gmane.org/gmane.comp.emulators.qemu/333402 . I don't want wrong or half-backed or even broken solutions. And I don't need any excuses for that. Thank you, /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
