1 |
On Wed, 2 Sep 2015 01:55:00 -0400 Fernando Rodriguez <frodriguez.developer@×××××××.com> wrote: |
2 |
|
3 |
> On Wednesday, September 02, 2015 12:57:37 PM wraeth wrote: |
4 |
> > On 02/09/15 12:23, Fernando Rodriguez wrote: |
5 |
> > > On Tuesday, September 01, 2015 9:22:44 PM Alec Ten Harmsel wrote: |
6 |
> > >> On Tue, Sep 01, 2015 at 05:05:09PM -0600, thelma@×××××××××××.com |
7 |
> > >> wrote: |
8 |
> > >>> On 09/01/2015 04:55 PM, Fernando Rodriguez wrote: |
9 |
> > >>>> Since you're too stupid to follow advice, you need to rebuild |
10 |
> > >>>> |
11 |
> > > *EVERYTHING* |
12 |
> > >>>> that linked against libjpeg (in this case x11-libs/wxGTK). |
13 |
> > >>> |
14 |
> > >>> This kind of language does not belong here. If you can not |
15 |
> > >>> refrain yourself making sarcastic remarks don't make any |
16 |
> > >>> comments. |
17 |
> > >> |
18 |
> > >> This language occasionally belongs on this list. |
19 |
> > >> |
20 |
> > >>> I would appreciate you stop reading my posts at all. I don't |
21 |
> > >>> belong to Gentoo community. |
22 |
> > >> |
23 |
> > >> OK. Maybe we all got off on the wrong foot here. When you ask for |
24 |
> > >> help, can you please provide: |
25 |
> > >> |
26 |
> > >> * the *exact* command you ran * the output of `emerge --info' * |
27 |
> > >> the whole error, not just the part you think is relevant |
28 |
> > >> |
29 |
> > >> It is incredibly difficult for us to help when we only get a |
30 |
> > >> small piece of what's going on with your system. |
31 |
> > >> |
32 |
> > >> Alec |
33 |
> > >> |
34 |
> > > |
35 |
> > > He was told what the problem was on his first post about |
36 |
> > > libjpeg-turbo, he didn't just ignore it but posted the wrong |
37 |
> > > solution with a big SOLVED on the subject that only serves to |
38 |
> > > mislead future users of this list. On his last post about this same |
39 |
> > > error (different package) I politely told him to go back and follow |
40 |
> > > the advise on that post, again he ignored it and posted a bogus |
41 |
> > > solution (it worked because he rebuilt tiff, perl had nothing to do |
42 |
> > > with it). revdep-rebuild may (or may not) fix it now, but the right |
43 |
> > > solution is to remove or fix the obsolete package to depend on |
44 |
> > > virtual/jpeg, update world properly, and then revdep-rebuild to |
45 |
> > > undo this mess. |
46 |
> > |
47 |
> > So someone posted an issue(s), then marked it solved when they got a |
48 |
> > workaround which may not resolve the actual issue but got them past |
49 |
> > their initial problem(s). |
50 |
> > |
51 |
> > Your argument to that is that their "false solution" will mislead |
52 |
> > future readers of the list. Doesn't the same apply to insulting |
53 |
> > participants of the list? Not to mention this comes shortly after a |
54 |
> > discussion about attracting new blood into the Gentoo community. |
55 |
> > |
56 |
> > You don't have to participate in this thread. You could also simply |
57 |
> > say "I said in your previous posts that you need to do /this/." |
58 |
> > |
59 |
> > We should never resort to insults and name calling if we want this to |
60 |
> > be a productive list. If there's a problem with someone, either stop |
61 |
> > replying to their messages, take it up with them directly (and |
62 |
> > diplomatically), or bring it up with the list owner [1,2]. |
63 |
> |
64 |
> I have no excuse for name calling, that was wrong and I should've handled it |
65 |
> better. Hopefully s/he'll get over it. |
66 |
> |
67 |
> It's arguable if that makes the list less productive, but certainly posting a |
68 |
> new thread every few hours about the same issue will make it less productive. |
69 |
|
70 |
Agree with the last phrase: "posting a new thread every few hours about |
71 |
the same issue" should be avoided." |
72 |
|
73 |
> > 1: http://www.ietf.org/rfc/rfc1855.txt |
74 |
> > 2: gentoo-user+owner@l.g.o |
75 |
> > |
76 |
> > -- |
77 |
> > wraeth <wraeth@×××××××××.au> |
78 |
> > GnuPG Key: B2D9F759 |
79 |
> > |
80 |
> |