Fair point -- I missed that part. I read the 'compiling' part and skimmed
over the rest.

On Fri, Jan 2, 2015 at 5:25 PM, Ryan Coleman <ryan.coleman at cwis.biz> wrote:

>
> On Jan 2, 2015, at 2:37 PM, Jeff Chapin <chapinjeff at gmail.com> wrote:
>
>
>
> On Fri, Jan 2, 2015 at 2:32 PM, paul g <pj.world at hotmail.com> wrote:
>
>> 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.
>>
>
> Yes, since it is an opportunity to improve the software.
>
>
>>
>> 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?
>>
>
> 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?
>
>
>
> I was doing *apt-get install spamassassin --reinstall  *though, so you
> tell me? I’ll end up reporting the bug eventually, but I have no idea how
> to fix it, I just found a work-around.
>
>
>> 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.
>>
>> Thanks for taking your time to respond.
>>
>> Happy New Year [image: Emoji]
>>
>>
>>
> You report the bug to whomever created the bug, typically.
>
>
>
>>
>> ------------------------------
>> Date: Fri, 2 Jan 2015 12:42:13 -0600
>> From: chapinjeff at gmail.com
>>
>> To: tclug-list at mn-linux.org
>> Subject: Re: [tclug-list] SpamAssassin compiling error - any ideas?
>>
>> 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.
>>
>> On Fri, Jan 2, 2015 at 12:39 PM, Jeff Chapin <chapinjeff at gmail.com>
>> wrote:
>>
>>
>>
>> On Fri, Jan 2, 2015 at 11:33 AM, paul g <pj.world at hotmail.com> wrote:
>>
>> 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
>>
>>
>> With most open source projects, the bug reports go straight to the
>> interested devs.
>>
>>
>>
>> and then sent down the pike as patched as in a new package?
>>
>>
>> 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.
>>
>>
>>
>> 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.
>>
>>
>> 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.
>>
>>
>> I do understand that Spam Assassin is a program not a part of Debian or
>> Ubuntu in any way.
>>
>> [image: Emoji] - Happy New Year
>>
>> ------------------------------
>> From: ryan.coleman at cwis.biz
>> Date: Fri, 2 Jan 2015 11:28:38 -0600
>> To: tclug-list at mn-linux.org
>> Subject: Re: [tclug-list] SpamAssassin compiling error - any ideas?
>>
>> Unlikely.
>>
>> On Jan 2, 2015, at 11:19 AM, paul g <pj.world at hotmail.com> wrote:
>>
>> Does this mean that possibly no one has actually ever compiled Spam
>> Assassin on Ubuntu 14.04.1 before?
>>
>> [image: Emoji] - Happy New Year
>>
>>
>>
>>
>> _______________________________________________ TCLUG Mailing List -
>> Minneapolis/St. Paul, Minnesota tclug-list at mn-linux.org
>> http://mailman.mn-linux.org/mailman/listinfo/tclug-list
>>
>> _______________________________________________
>> TCLUG Mailing List - Minneapolis/St. Paul, Minnesota
>> tclug-list at mn-linux.org
>> http://mailman.mn-linux.org/mailman/listinfo/tclug-list
>>
>>
>>
>>
>> --
>> Jeff Chapin
>> President, CedarLug, retired
>> President, UNIPC, "I'll get around to it"
>> President, UNI Scuba Club
>> Senator, NISG, retired
>>
>>
>>
>>
>> --
>> Jeff Chapin
>> President, CedarLug, retired
>> President, UNIPC, "I'll get around to it"
>> President, UNI Scuba Club
>> Senator, NISG, retired
>>
>> _______________________________________________ TCLUG Mailing List -
>> Minneapolis/St. Paul, Minnesota tclug-list at mn-linux.org
>> http://mailman.mn-linux.org/mailman/listinfo/tclug-list
>>
>> _______________________________________________
>> TCLUG Mailing List - Minneapolis/St. Paul, Minnesota
>> tclug-list at mn-linux.org
>> http://mailman.mn-linux.org/mailman/listinfo/tclug-list
>>
>>
>
>
> --
> Jeff Chapin
> President, CedarLug, retired
> President, UNIPC, "I'll get around to it"
> President, UNI Scuba Club
> Senator, NISG, retired
> _______________________________________________
> TCLUG Mailing List - Minneapolis/St. Paul, Minnesota
> tclug-list at mn-linux.org
> http://mailman.mn-linux.org/mailman/listinfo/tclug-list
>
>
>
> _______________________________________________
> TCLUG Mailing List - Minneapolis/St. Paul, Minnesota
> tclug-list at mn-linux.org
> http://mailman.mn-linux.org/mailman/listinfo/tclug-list
>
>


-- 
Jeff Chapin
President, CedarLug, retired
President, UNIPC, "I'll get around to it"
President, UNI Scuba Club
Senator, NISG, retired
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.mn-linux.org/pipermail/tclug-list/attachments/20150102/c37d066f/attachment.html>