Le 02/09/2016 à 12:05, John Paul Adrian Glaubitz a écrit : > Yes, this is *exactly* what you are supposed to do before filing a > bug report, especially when using *unstable*. If that is too much for > you, please refrain from using *unstable* which is not targeted at > regular end users but primarily developers, in particular people who > develop Debian. You can search the bug tracker with Google, after > all. So I don't really think asking for some research before filing a > new bug report is too much asked for, really. I do that all the > time.
Oh, I am a "regular end user" now ? What on earth makes you think that I use unstable only for the "pleasure" of having bleeding-edge versions of my software ? Why is it so far fetched from your point of view that I, too, also might develop Debian packages (personal *and* official ones), and need the latest versions of devscripts, git-buildpackage, lintian, et al on my development machine ? This was exactly the whole point of the last sentence in my initial bug report (which I also tried to hint in my initial reply to your harsh response) but apparently your ego prevented you to get the message. > People like you constantly ignore the fact that at the other end of > the bug tracker you will find people which are receiving all these > bug report mails and I can tell you that if you get more than half a > dozen bug reports describing the same problem over and over again you > will loose your patience and tamper as well. "People like me" ? What exactly do you mean by that ? Also, please remind me when I showed to "constantly ignore" that Debian developers get a lot of e-mail traffic due to bug reports. Don't you think I already know that after using Debian for seventeen years ? Please show me a bug that I reported that was already (or that I didn't merge by myself very quickly after realizing it). I honestly take kindly to learn from my mistakes. > No, not really. The pinpointing is done *upstream*. As I have > explained many many times, this is the Debian bug tracker which > tracks Debian-specific bugs. The bug you are seeing is an upstream > bug and therefore affects all distributions and therefore belongs to > the upstream bug tracker where it will reach the people who can fix > the actual code. Reporting your bug upstream will dramatically > increase the bug fixing process and also mean less burden and stress > for downstream. It also makes sure all distributions are receiving > the fix as quickly as possible. That's not what the Debian documentation says (I mean the official Debian documentation, not the wiki): > Don't file bugs upstream > > If you file a bug in Debian, don't send a copy to the upstream > software maintainers yourself, as it is possible that the bug exists > only in Debian. If necessary, the maintainer of the package will > forward the bug upstream. (Source: https://www.debian.org/Bugs/Reporting.en.html, so it can't even be a translation error) It means that I should report the bug to Debian first, and that *you* decide afterwards if it should be forwarded upstream. Ironically, this is *especially true* in this particular case, since upstream still uses GTK2 by default, and building the whole MATE desktop against GTK3 was a decision made solely by the Debian maintainers (and, IMHO, not a very clever one, since the Gnome devs, who took over GTK a long time ago, are notorious for being oblivious to anything non-Gnome - especially other desktop environments, which they see as competitors to their "brand" (I quote) - and happily (or is it purposefully ? I may be a bit paranoid here, but who knows) break GTK every six months). I gladly admit that I forgot to add the "upstream" tag, but you can't seriously blame me for reporting bugs in the Debian BTS only because they come from upstream, whereas the official Debian documentation explicitly says otherwise. > Thank you. My advise would also be to use another distribution > altogether, I advise using something other than a development > release, then you won't be bothered anymore by things being broken > during *development*. I would also suggest learning the difference > between upstream and distribution downstream and understanding when > to report bugs upstream and when to report them downstream. For both points, see above. > PS: The bug you are seeing is because of a change in GTK3, not MATE, > so you're actually also yelling at the wrong people when you > complain about things being broken this time. I didn't "yell" at anyone, you did (and in an incredibly condescending tone, I might add). Regards, -- Raphaël Halimi
signature.asc
Description: OpenPGP digital signature
