SHARE
TWEET

Freedesktop.org says you must respect & love pedosexuals

a guest May 23rd, 2018 110 Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  1. MIME-Version: 1.0
  2. Received: by 2002:a17:90a:8c05:0:0:0:0 with HTTP; Wed, 23 May 2018 08:50:36 -0700 (PDT)
  3. Date: Wed, 23 May 2018 22:50:36 +0700
  4. Delivered-To: hojuruku@gmail.com
  5. Message-ID: <CAENjB=LqB51UsZLrNoqY=0XbYEbOYOk9aHHz0Ujkq9PLcTq+3Q@mail.gmail.com>
  6. Subject: banned from bugtracker for doing nothing wrong on bugtracker because I was trolled by a dev putting out 3x falsehoods
  7. From: Luke McKee <hojuruku@gmail.com>
  8. To: sitewranglers@lists.freedesktop.org
  9. Cc: ckoenig.leichtzumerken@gmail.com, daniel@fooishbar.org
  10. Content-Type: multipart/alternative; boundary="000000000000ee8257056ce17e72"
  11.  
  12. --000000000000ee8257056ce17e72
  13. Content-Type: text/plain; charset="UTF-8"
  14.  
  15. Where is the "Extremely hostile and prone to ranting about how people he
  16. doesn't like are 'LGBTI nut[s]', as well as about how LGBTI education
  17. programs are 'subverting [Australian] youth'. No idea how you got to that
  18. point from a discussion about licenses, but freedesktop.org welcomes anyone
  19. regardless of gender, sexuality, etc. I would recommend reviewing this:
  20. https://www.freedesktop.org/wiki/CodeOfConduct/ "
  21.  
  22. LGBTI stuff I put on the bugtracker? Why does leftists who look up my
  23. youtube channel try and ban me from bug trackers when I only talk ON TOPIC
  24. about mesa matters like here:
  25.  
  26. https://bugs.freedesktop.org/show_bug.cgi?id=106625
  27.  
  28. Here's the comment i would have made if I wasn't banned. Everything on that
  29. ticket was technical only and on topic. It doesn't deserve a ban for
  30. pointing out a dev was wrong on 3x counts.
  31.  
  32.  
  33. <hojuruku> you were wrong on 3 counts.. if you are a mesa developer for
  34. ubuntu (which I don't touch with 30 ft pole, though I'm going to try some
  35. your chromium patches shortly that's about it) then don't go putting
  36. falsehoods on tickets.
  37. <hojuruku> go for quality not quantity on bugtracker responses.
  38. <daniels> i left canonical in very early 2006, but ok
  39. <daniels> you can do what you like, but the 'LGBTI nut' and bizzare rant
  40. about 'pedophiles and their special gay police friends' has earned you a
  41. ban from bugzilla and the lists
  42. <daniels> you can review our code of conduct on the website if you like,
  43. which pretty clearly rules out abusing people based on their sexuality
  44. <daniels> (even if you do happen to be totally wrong about it)
  45. <daniels> have a good evening
  46. <hojuruku> so you trolled
  47. <hojuruku> and trolled
  48. <hojuruku> so what did I do wrong on bugzilla?
  49. <hojuruku> I proved you wrong?
  50. <hojuruku> and I get banned for only being right ?
  51. <daniels> literally not what you said, but no point discussing with someone
  52. who invents their own reality
  53.  
  54. Clearly we have a leftist nut troll who trolls people on IRC, and the bug
  55. tracker then bans for his ulterior motive. He knows me from 2003 slug.org.au
  56. / linux conf mailing list before I became a UNHCR confirmed political
  57. refugee from Australia.
  58.  
  59. Egomaniacs....
  60.  
  61. He said:
  62. 1) libomx-bellago was not LGPL
  63. 2) AMD doesn't distribute a binary gst-plugins-omx
  64. 3) and accused me all over IRC of reporting an GPL VIOLATION  (not a source
  65. code request)
  66.  
  67. Trolls me, and then get's me banned. Clearly those who are not politically
  68. correct outside the bugtracker needs to be banned on it for XYZ pride.
  69.  
  70.  
  71. Here's the IRC log that has nothing to do with the bugtracker.
  72.  
  73. I WAS FALSELY ACCUSED OF ACCUSING MESA OF A GPL/LGPL violation when I did
  74. no such thing.
  75.  
  76. And the other 2x falsehoods in the ticket. If you prove a dev wrong on tech
  77. facts you get banned? Please expalin.
  78. * jrmuizel (~jrmuizel@corp-nat.fw1.untrust.tor1.mozilla.com) has joined
  79. <daniels> hojuruku: glad you got your source, but please try to be less
  80. hostile about it in future. thanks.
  81. <hojuruku> https://bugs.freedesktop.org/show_bug.cgi?id=106625 not hostile
  82. mate. You were the one that was hostile that thought i was doing a LGPL
  83. source code request (not violation) against mesa - when it was to AMD from
  84. the onset.
  85. <hojuruku> well you thought i was hostile
  86. <imirkin_> as a (mostly) external observer, daniels seemed quite reasonable
  87. in his comments.
  88. <hojuruku> I was just trying to find out how to use a feature in Mesa that
  89. wasn't documented properly by anyone - and the source to activate that
  90. feature appeared to from the mesa driver source appear to be a patch to
  91. libomxil-bellago but in fact it was just a patch to gst-plugins-omx
  92. <hojuruku> Anyway I'm happy. i abused the freedesktop.org bugtracker to get
  93. a link to some source code from AMD and I got it. I'm happy. Mission
  94. accomplished and those who read the bug tracker will not that you can do
  95. h265 decoding from openmax now too, and how to do it.
  96. <imirkin_> then ask that, rather than go around claiming license violations.
  97. <hojuruku> (without using AMD's binary drivers)
  98. <hojuruku> (and modifying config for said binary drivers)
  99. <hojuruku> where did I claim a code violation?
  100. <imirkin_> that's how i read your original comment.
  101. <hojuruku> LGPL all you have to do is say where the source code  is
  102. <hojuruku> Bug 106625 - AMD HEVC support for for libomxil-bellagio /
  103. gst-plugins-omx
  104. <imirkin_> yes, that one.
  105. <hojuruku> it was opened as a feature request in the headline? where did it
  106. say LGPL VIolation (not source code request)
  107. <hojuruku> the headline was a feature request, or a documentation / example
  108. source code to use an existing feature request
  109. <hojuruku> "The patches are probably already floating AMD's [offices'], OMX
  110. HEVC support has found it's way into mesa but [not] to the libraries that
  111. use it."
  112. <hojuruku> that's what the ticket was about... it was always about the
  113. libraries that use the mesa gallim state tracker library / mesa dll drivers.
  114. * FRIGN has quit (Quit: Leaving)
  115. <hojuruku> "Can one use omx HEVC decode in the mesa state tracker without
  116. AMD's patch to libomxil-bellago [or plugin-gst-openmax - depending where
  117. they implemented the feature] ? Can you please release it?"
  118. <daniels> hojuruku: i'm super happy that the code is out there, that people
  119. can make use of it, and that they can reuse it for free drivers. but from a
  120. legal point of view, i'm less happy about people using mesa/fd.o as a base
  121. to throw claims of license violations at third parties.
  122. <hojuruku> can "you" being AMD devs on the readonsi section of mesa
  123. bugtracker.
  124. <hojuruku> Where was the claim of license violation.
  125. <hojuruku> please copy paste it please... It's only a GPL violation when
  126. AMD releases patched opensource libraries and DOESN'T link to the source /
  127. make the fork public
  128. <hojuruku> at which point you request the source from AMD it isn't a
  129. violation until amd says get stuffed we won't release our source to our
  130. fork of an opensource app under the LGPL.... so there never was a violation.
  131. <daniels> it's a waste of our time to go back and forth on it, but if you
  132. really want to, try comment two. (regardless of whether or not any changes
  133. are made whatsoever, any LGPL binary distribution must be accompanied by an
  134. offer of source code, full stop.)
  135. <daniels> all that i'm asking is that you tone it down a little bit. i'm
  136. not looking for a fight, but a lot of what you write comes across as over
  137. aggressive.
  138. <hojuruku> daniels imirkin_ ^^^ see above. Where exactly in that ticket did
  139. I say LGPL Violators bend down? No.. I said someone was dead wrong
  140. "Bellagio (and Mesa generally) are not licensed under the GPL," - So i link
  141. to the COPYING FILES for libomx-belligo / gst-plugins-omx and they both say
  142. LGPL oops..
  143. <hojuruku> daniels: in addition to being dead wrong about omix-bellagilo
  144. not being GPL ... there is this gem "
  145. <hojuruku> So for this to be enforceable under the GPL: AMD would need to
  146. have definitely written the code (it is not clear if this has even
  147. happened), and distributed binaries built from it (it seems clear this has
  148. not happened), and the code would need to be under (L)GPL (it isn't).
  149. <hojuruku> "
  150. <daniels> i understand what you're saying; i don't think you understand the
  151. severity of having mesa/fd.o tarnished by having people throw around words
  152. which could be interpreted by a reasonable observer (apparently there were
  153. at least two of us who read it the same way) as claiming a license
  154. violation.
  155. <hojuruku> Are you saying AMD is not distributing binaries from
  156. gst-plugins-openmax? Didn't I say they were in the Original post on the bug
  157. with a link to a download location?
  158. <hojuruku> So dead wrong x2
  159. <MrCooper> hojuruku: since you reported a bug in Mesa's bug tracker, we
  160. foolishly assumed it was related to Mesa, which isn't (L)GPL
  161. <hojuruku> daniels: waste of time to go backwards and forwards. No you stop
  162. being hostile. TELL ME WHERE I SAID GPL CODE VIOLATION? I didn't.  IT
  163. RELATED TO A FEATURE IN MESA that required libomxil-bellago and AS it
  164. happens A PATCHED gst-plugins-omx in order to use.
  165. * jsaa (jsaa@nat/intel/x-kixhgrcbiowbndct) has joined
  166. <daniels> hojuruku: if you re-read comment #6, you'll see that I realised
  167. what was going on. that you were using 'GPL' in relation to gst-omx (which
  168. is LGPL), but mostly just asking about the source for bellagio or a sample
  169. client (which are not LGPL).
  170. * headless (~headless@31.173.83.107) has joined
  171. <hojuruku> so you were wrong... and I was hostile for politely correcting,
  172. you. yeah let's not go backwards and forwards. it's all in the ticket.
  173. * Lyude has quit (Quit: WeeChat 2.0.1)
  174. <hojuruku> LGPL requires source to be released for forks of libraries
  175. distributed in binary form by corporations
  176. <daniels> hojuruku: if it's that important to you to prove that i was 'dead
  177. wrong', and i was right, then great, you can have that. all i'm asking is
  178. to stop shouting in upper case, stop demanding answers to the same question
  179. multiple times, etc. the way you communicate is very hostile.
  180. <imirkin_> you realize there's no upside for you here, right? you've
  181. exhausted any kind of good will that one by default gets around here...
  182. * Lyude (~lyudess@pool-98-118-43-90.bstnma.ftas.verizon.net) has joined
  183. <daniels> s/and i was right/and you were right/
  184. * udovdh (~udovdh@2001:981:a812:0:e2d5:5eff:fea3:6b35) has joined
  185. <udovdh> hello
  186. <udovdh> I found some error in dmesg:
  187. <udovdh> [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin
  188. framebuffer with error -12
  189. <hojuruku> I was asking for the patched source for libomx-bellagio (one
  190. place they could have implemented HEVC - patching the openmax-il
  191. impemention) or in amd's case they used unpatched openmax bellagio and a
  192. patched gst-plugins-openmax....
  193. <imirkin_> udovdh: sounds like something for #radeon
  194. <udovdh> and amdgpu 0000:09:00.0: 00000000805434a4 pin failed
  195. <udovdh> ok
  196. * amerel has quit (Remote host closed the connection)
  197. * fab_ (~fab@bellet.info) has joined
  198. * KishoreKadiyala has quit (Quit: Leaving.)
  199. <hojuruku> yeah just drop it, you probably know who I am and hate me
  200. because of the work I do at http://youtube.com/hojuruku - so enough said. I
  201. just had a video censored from my youtube channel on request from Drew West
  202. Press who makes videos praising how good it is to have child sex gateway
  203. dolls.  https://www.youtube.com/watch?v=QkbydZAzg3o That was the last
  204. person to complain to get a video censored my channel. Some people are used
  205. to being
  206. <hojuruku> trolled by nutters always trying to pick a fight because they
  207. don't like a certian politically correct minority group subverting our
  208. youth (kidsrights.org.au vs facebook.com/policeglbti) - I'm not going to
  209. engage trolls after me but when people say I'm wrong when I'm right I'll
  210. assertively stand my ground and say NO you are wrong if you are. And If I'm
  211. wrong likewise I'll admit that.
  212. <hojuruku> what I was saying is maybe you had an anterior motive for doing
  213. repeately making false claims of a LGPL violation when I never said it.
  214. Made false claims that the software mesa linked to wasn't LGPL when it was
  215. and made the false claim amd (who maintain the gallium radeon state
  216. tracker) weren't binary distributing said driver. Then still parroting on
  217. I'm wrong wrong wrong. I'm sorry. if the truth is on my side I'm going to
  218. say it end of
  219. <hojuruku> story. So move on and I don't care if I have to massage other
  220. peoples ego's jumping on bugtracker tickets acting hosting and publishing
  221. false info.
  222. <daniels> no, i had absolutely no idea you had a youtube channel about
  223. child sex dolls. i have many interests, but that's not one of them.
  224. <hojuruku> I don't have a youtube channel about child sex dolls. I have
  225. pedophiles after me and their special gay police friends.
  226. https://153news.net/watch_video.php?v=M8K996WOHNXD clearly you are trolling
  227. me with more strawmen false claims. If you saw my channel you wouldn't be
  228. saying that. Clearly you are trolling me here like you are trolling me on
  229. the freedesktop bugtracker. Ignored.
  230. * thuttu77 (~thuttu77@82-181-37-124.bb.dnainternet.fi) has joined
  231. <hojuruku> clearly you can't read English. Scroll up. Did I say it was my
  232. channel? No. This off topic discussion from the LGBTI nut who knows my nick
  233. and hates me is over. Done.
  234. * cwabbott (~cwabbott@c-24-61-133-212.hsd1.ct.comcast.net) has joined
  235. * murray has quit (Ping timeout: 252 seconds)
  236. * ChanServ gives channel operator status to ajax
  237. * ajax sets quiet on $a:hojuruku
  238. <imirkin_> i guess i missed out with the /ignore?
  239. * maelcum (~horst@dslb-088-075-239-153.088.075.pools.vodafone-ip.de) has
  240. joined
  241. <daniels> imirkin_: if not hearing rants about how I'm a 'LGBTI nut' allied
  242. with 'pedophiles and their special gay police friends' counts as 'missing
  243. out', then yeah
  244. <hojuruku> daniel knows me from slug.org.au / linux conf days in 2k3 no
  245. doubt. i'm a political refugee from Australia. Don't ask don't go there.
  246. Agree to disagree move on.
  247. * #dri-devel :Cannot send to channel
  248. <imirkin_> :)
  249. >daniels< i know you fuck, you went to slug.org.au / linux.conf in Australia
  250. >daniels< i know you from the slug mailing list way back, but I used a
  251. different nick then, just rack off you troll
  252. <danvet> ajax, thx, got distracted when I wanted to read up and figure out
  253. whether to ban or not
  254. * danvet approves
  255. <daniels> (i've extended this to bz as well)
  256. * medfly (~fly@141.226.161.149) has joined
  257. * glennk has quit (Ping timeout: 252 seconds)
  258. * glennk (~glenn@c-6042d854.010-226-6d6c6d10.bbcust.telenor.se) has joined
  259. * shadeslayer has quit (Ping timeout: 256 seconds)
RAW Paste Data
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy. OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!
 
Top