<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jan 2, 2015 at 2:32 PM, paul g <span dir="ltr"><<a href="mailto:pj.world@hotmail.com" target="_blank">pj.world@hotmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div dir="ltr">1. Would this issue that Ryan was having with SpamAssassin be a legit bug report situation? Ryan obviously figured out the problem without the need to file a bug report and therefore was able to install the software.<br></div></div></blockquote><div><br></div><div>Yes, since it is an opportunity to improve the software.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div dir="ltr"><br>2. Now, if this is a legit bug report situation and Ryan had needed or wanted to file a bug report what would be the 'correct' avenue to do so would he start with the SpamAssassin development team or Ubuntu or Debian upstream maintainers? <br></div></div></blockquote><div><br></div><div>Most likely Spam Assassin -- given that he was compiling, it is unlikely he was compiling from Ubuntu-provided source code. Most of the time you compile, you are doing so to get a newer version than what is provided by your distro (or want to change the defaults). Even if it was provided by Ubuntu/Debian, unless the error is due to a change made by Ubuntu/Debian, why would you report the issue to them?<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div dir="ltr"><br>This to me is a good question to learn on because it would help me in the future if I needed to file a bug report. Pointing to where best and most appropriate to 'ask the question/duplicate the situation' to the proper area. As far as bug reports are concerned.<br><br>Thanks for taking your time to respond. <br><br>Happy New Year <img src="https://a.gfx.ms/Emoji_1F60A.png" alt="Emoji"><br><br><br></div></div></blockquote><div><br></div><div>You report the bug to whomever created the bug, typically. <br></div><div><br> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div dir="ltr"><br><div><hr>Date: Fri, 2 Jan 2015 12:42:13 -0600<br>From: <a href="mailto:chapinjeff@gmail.com" target="_blank">chapinjeff@gmail.com</a><div><div class="h5"><br>To: <a href="mailto:tclug-list@mn-linux.org" target="_blank">tclug-list@mn-linux.org</a><br>Subject: Re: [tclug-list] SpamAssassin compiling error - any ideas?<br><br><div dir="ltr">I'll correct myself here -- in my last email, I made the assumption that we were talking about bug reports that are properly filed with the correct project. I feel like that needed to be clarified based on Andrew's reply.<br></div><div><br><div>On Fri, Jan 2, 2015 at 12:39 PM, Jeff Chapin <span dir="ltr"><<a href="mailto:chapinjeff@gmail.com" target="_blank">chapinjeff@gmail.com</a>></span> wrote:<br><blockquote style="border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div><br><div><span>On Fri, Jan 2, 2015 at 11:33 AM, paul g <span dir="ltr"><<a href="mailto:pj.world@hotmail.com" target="_blank">pj.world@hotmail.com</a>></span> wrote:<br><blockquote style="border-left:1px #ccc solid;padding-left:1ex">
<div><div dir="ltr">That is kinda really actually interesting. So how long if you file a proper bug report would it perhaps take to get into the hands of the programmer</div></div></blockquote><div><br></div></span><div>With most open source projects, the bug reports go straight to the interested devs.<br></div><span><div><br> </div><blockquote style="border-left:1px #ccc solid;padding-left:1ex"><div><div dir="ltr"> and then sent down the pike as patched as in a new package? </div></div></blockquote><div><br></div></span><div>Depends on how much the programmers care, and how many people it impacts, and how long it takes to code a fix. In some cases minutes, in some, the bugs linger around for years because no one cares enough to devote the time to fix it.<br></div><span><div><br> </div><blockquote style="border-left:1px #ccc solid;padding-left:1ex"><div><div dir="ltr">I was reading that with Arch it can happen within a week. That's one thing about Debian as I have started to perhaps understand a little more is time it may take to get bugs fixed.</div></div></blockquote><div><br></div></span><div>This is mostly due to the number of architectures Debian supports. The fixes don't always take a long time, compiling and testing the fixes on multiple architectures sometimes does.<br></div><span><div> </div><blockquote style="border-left:1px #ccc solid;padding-left:1ex"><div><div dir="ltr"> I do understand that Spam Assassin is a program not a part of Debian or Ubuntu in any way.<span><br><br><img src="https://a.gfx.ms/Emoji_1F608.png" alt="Emoji"> - Happy New Year<br><br></span><div><hr>From: <a href="mailto:ryan.coleman@cwis.biz" target="_blank">ryan.coleman@cwis.biz</a><br>Date: Fri, 2 Jan 2015 11:28:38 -0600<span><br>To: <a href="mailto:tclug-list@mn-linux.org" target="_blank">tclug-list@mn-linux.org</a><br>Subject: Re: [tclug-list] SpamAssassin compiling error - any ideas?<br><br></span><div><div>Unlikely.<div><br><div><blockquote><div>On Jan 2, 2015, at 11:19 AM, paul g <<a href="mailto:pj.world@hotmail.com" target="_blank">pj.world@hotmail.com</a>> wrote:</div><br><div><div dir="ltr" style="font-family:Calibri;font-size:16px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">Does this mean that possibly no one has actually ever compiled Spam Assassin on Ubuntu 14.04.1 before?<span> </span><br><br><img src="https://a.gfx.ms/Emoji_1F608.png" alt="Emoji"><span> </span>- Happy New Year<br></div></div></blockquote></div><br></div><div><br></div><br></div></div><span>_______________________________________________
TCLUG Mailing List - Minneapolis/St. Paul, Minnesota
<a href="mailto:tclug-list@mn-linux.org" target="_blank">tclug-list@mn-linux.org</a>
<a href="http://mailman.mn-linux.org/mailman/listinfo/tclug-list" target="_blank">http://mailman.mn-linux.org/mailman/listinfo/tclug-list</a></span></div> </div></div>
<br>_______________________________________________<br>
TCLUG Mailing List - Minneapolis/St. Paul, Minnesota<br>
<a href="mailto:tclug-list@mn-linux.org" target="_blank">tclug-list@mn-linux.org</a><br>
<a href="http://mailman.mn-linux.org/mailman/listinfo/tclug-list" target="_blank">http://mailman.mn-linux.org/mailman/listinfo/tclug-list</a><br>
<br></blockquote></span></div><span><font color="#888888"><br><br clear="all"><br>-- <br><div>Jeff Chapin<br>President, CedarLug, retired<br>President, UNIPC, "I'll get around to it"<br>President, UNI Scuba Club<br>Senator, NISG, retired</div>
</font></span></div></div>
</blockquote></div><br><br clear="all"><br>-- <br><div>Jeff Chapin<br>President, CedarLug, retired<br>President, UNIPC, "I'll get around to it"<br>President, UNI Scuba Club<br>Senator, NISG, retired</div>
</div>
<br>_______________________________________________
TCLUG Mailing List - Minneapolis/St. Paul, Minnesota
<a href="mailto:tclug-list@mn-linux.org" target="_blank">tclug-list@mn-linux.org</a>
<a href="http://mailman.mn-linux.org/mailman/listinfo/tclug-list" target="_blank">http://mailman.mn-linux.org/mailman/listinfo/tclug-list</a></div></div></div> </div></div>
<br>_______________________________________________<br>
TCLUG Mailing List - Minneapolis/St. Paul, Minnesota<br>
<a href="mailto:tclug-list@mn-linux.org">tclug-list@mn-linux.org</a><br>
<a href="http://mailman.mn-linux.org/mailman/listinfo/tclug-list" target="_blank">http://mailman.mn-linux.org/mailman/listinfo/tclug-list</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature">Jeff Chapin<br>President, CedarLug, retired<br>President, UNIPC, "I'll get around to it"<br>President, UNI Scuba Club<br>Senator, NISG, retired</div>
</div></div>