fail to build git version of freeswitch
https://bugzilla.redhat.com/show_bug.cgi?id=667529 Patch utlity do not allow to modify files in parent directories anymore. These patch solve this poblem. cat mod_shout.patch --- src/mod/formats/mod_shout/Makefile.orig 2012-02-27 22:47:13.721919787 +0400 +++ src/mod/formats/mod_shout/Makefile 2012-02-27 22:47:42.562919843 +0400 @@ -49,7 +49,7 @@ $(SHOUT_DIR): $(GETLIB) $(SHOUT).tar.gz - patch -p0 -i hack_out_ogg.diff + patch -p 6 -d ../../../../libs/libshout-2.2.2 < hack_out_ogg.diff $(SHOUT_BUILDDIR)/Makefile: $(SHOUT_DIR) mkdir -p $(SHOUT_BUILDDIR)
bug reports go to jira please... Also include all the good information there On 2/27/12 6:03 AM, "Lubimov Alexey" <avlubimov@gmail.com> wrote:
https://bugzilla.redhat.com/show_bug.cgi?id=667529
Patch utlity do not allow to modify files in parent directories anymore.
These patch solve this poblem.
cat mod_shout.patch --- src/mod/formats/mod_shout/Makefile.orig 2012-02-27 22:47:13.721919787 +0400 +++ src/mod/formats/mod_shout/Makefile 2012-02-27 22:47:42.562919843 +0400 @@ -49,7 +49,7 @@
$(SHOUT_DIR): $(GETLIB) $(SHOUT).tar.gz - patch -p0 -i hack_out_ogg.diff + patch -p 6 -d ../../../../libs/libshout-2.2.2 < hack_out_ogg.diff
$(SHOUT_BUILDDIR)/Makefile: $(SHOUT_DIR) mkdir -p $(SHOUT_BUILDDIR)
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
fyi http://jira.freeswitch.org/browse/FS-3711 -- View this message in context: http://freeswitch-users.2379917.n2.nabble.com/fail-to-build-git-version-of-f... Sent from the freeswitch-users mailing list archive at Nabble.com.
Lubimov Alexey, would you attach that patch to the Jira as a git diff please? -- View this message in context: http://freeswitch-users.2379917.n2.nabble.com/fail-to-build-git-version-of-f... Sent from the freeswitch-users mailing list archive at Nabble.com.
bug reports go to jira please... Also include all the good information there
Well, may I remind you that I've raised exactly the same bug myself more than a week ago, proposing a very similar patch as a solution and posted all of this on JIRA (http://jira.freeswitch.org/browse/FS-3923, created on 19 Feb 2012). In addition, I've emailed you directly with the same - twice, if I am not mistaken, as well as raising a few other issues I encountered as part of building FS myself (and proposed a solution to the majority of those). Unfortunately, I've received no response in either of these cases (the issue raised on JIRA is still sitting there gathering dust, with the grand total of 0 votes and 0 comments) and it looks as though you have completely ignored my emails, which is a pity, but to be honest, I couldn't care less really...if the FS devs can't be arsed why should I?
On Mon, Feb 27, 2012 at 2:05 PM, Josh <mojo1736@privatedemail.net> wrote:
bug reports go to jira please... Also include all the good information there
Well, may I remind you that I've raised exactly the same bug myself more than a week ago, proposing a very similar patch as a solution and posted all of this on JIRA (http://jira.freeswitch.org/browse/FS-3923, created on 19 Feb 2012).
In addition, I've emailed you directly with the same - twice, if I am not mistaken, as well as raising a few other issues I encountered as part of building FS myself (and proposed a solution to the majority of those).
Unfortunately, I've received no response in either of these cases (the issue raised on JIRA is still sitting there gathering dust, with the grand total of 0 votes and 0 comments) and it looks as though you have completely ignored my emails, which is a pity, but to be honest, I couldn't care less really...if the FS devs can't be arsed why should I?
Perhaps it would be better to keep this aspect of the thread off the mailing list and instead keep it in the comments section of the relevant Jira tickets. If you have a difference of opinion with a specific person that's fine, but airing the laundry in public will just divert time and energy away from the task of fixing the issue in question. Thanks gents, Michael
Perhaps it would be better to keep this aspect of the thread off the mailing list and instead keep it in the comments section of the relevant Jira tickets. If you have a difference of opinion with a specific person that's fine, but airing the laundry in public will just divert time and energy away from the task of fixing the issue in question. Well, I thought "the issue in question" is a particular bug, which, as it turns out, was raised by no less than 3 individuals within the last month or so and it seems to have been duly ignored by the FS devs. What good is it to have JIRA if whatever is raised there is ignored?
I have no "issues" with Ken at all (or anyone else from the FS devs for that matter). What I do have an issue with, is that one of the FS developers is banging on about "raising issues in JIRA" when those issues have been completely ignored - that is what I have a problem with. As for the "not airing the laundry in public" bit above - if something needs to be said, I'll just say it - the last time I checked, this is a public forum and not Nazi Germany, or have I made the wrong turn somewhere?
No, I just have other priorities at this point, and fedora is not high on the list... I cant speak for the other developers, but I'm sure they all have their own priorities too... See also http://jira.freeswitch.org/browse/FS-3711 this is already opened and developers have already been looking at it On 2/27/12 4:05 PM, "Josh" <mojo1736@privatedemail.net> wrote:
bug reports go to jira please... Also include all the good information there
Well, may I remind you that I've raised exactly the same bug myself more than a week ago, proposing a very similar patch as a solution and posted all of this on JIRA (http://jira.freeswitch.org/browse/FS-3923, created on 19 Feb 2012).
In addition, I've emailed you directly with the same - twice, if I am not mistaken, as well as raising a few other issues I encountered as part of building FS myself (and proposed a solution to the majority of those).
Unfortunately, I've received no response in either of these cases (the issue raised on JIRA is still sitting there gathering dust, with the grand total of 0 votes and 0 comments) and it looks as though you have completely ignored my emails, which is a pity, but to be honest, I couldn't care less really...if the FS devs can't be arsed why should I?
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
No, I just have other priorities at this point, and fedora is not high on the list...
The issue I raised had nothing whatsoever to do with Fedora.
I cant speak for the other developers, but I'm sure they all have their own priorities too...
I am sure they do, but a simple acknowledgement (even if it is a one-liner) would suffice - we are all very busy.
Please be patient with these types of issues(build related) and Jira. We do appreciate that you filed this problem but its very easy for these issues to be missed or overlooked for periods of time do to priority(I'm sure you can understand how difficult a large project can be accross many platforms) but they will not be lost which is the important part. Combining duplicate issues is also difficult, like with this issue I happened to remember that I saw an issue last fall that resembled this one so I went and hunted it down and posted the reference to this list but I missed yours which of course was not intentional. Thanks for the help and your patience. -- View this message in context: http://freeswitch-users.2379917.n2.nabble.com/fail-to-build-git-version-of-f... Sent from the freeswitch-users mailing list archive at Nabble.com.
Please be patient with these types of issues(build related) and Jira. We do appreciate that you filed this problem but its very easy for these issues to be missed or overlooked for periods of time do to priority(I'm sure you can understand how difficult a large project can be accross many platforms) but they will not be lost which is the important part. Combining duplicate issues is also difficult, like with this issue I happened to remember that I saw an issue last fall that resembled this one so I went and hunted it down and posted the reference to this list but I missed yours which of course was not intentional.
All of the above are fair points, but what I can't really get my head around is that this particular issue has been gathering dust for the best part of a month and at the same time at least two of the people raising it (myself and Alexsey) proposed a ready-made solution, which is very easy to implement and integrate into the source tree - all that needs to be done is for the path of the original patch to be changed and the appropriate "patch" command line executable to be amended - that is all there is to this, not really rocket science is it? If you do not believe me, look at what I suggested (and attached as a correction patch) in http://jira.freeswitch.org/browse/FS-3923
Josh, Please test the patch at http://jira.freeswitch.org/browse/FS-3711 testpatch.txt which is provided by Alexey. -- View this message in context: http://freeswitch-users.2379917.n2.nabble.com/fail-to-build-git-version-of-f... Sent from the freeswitch-users mailing list archive at Nabble.com.
Josh, Please test the patch at
http://jira.freeswitch.org/browse/FS-3711
testpatch.txt
which is provided by Alexey.
I don't want to act like a smug idiot, but I like my version of the patch better for (at least) 2 reasons: 1. The original patch modifications (hack_out_ogg.diff) made by my patch no longer use "relative" paths (i.e. "../../") and thus comply with any version of the patch used. 2. My modifications made to the appropriate mod_shout Makefile are much better, because they use SHOUT_BUILDDIR, which is already defined in that Makefile, and do not rely on some hard-coded path ("../../../../" for example). In other words, I think: patch -d $(SHOUT_BUILDDIR) -p1 < hack_out_ogg.diff (which is what my patch proposes) is much better than: patch -p 6 -d ../../../../libs/libshout-2.2.2 < hack_out_ogg.diff (which is what Alexsey have proposed)
I don't want to act like a smug idiot... You are.
but I like my version of the patch better for (at least) 2 reasons:
1. The original patch modifications (hack_out_ogg.diff) made by my patch no longer use "relative" paths (i.e. "../../") and thus comply with any version of the patch used.
Move to the JIRA.
2. My modifications made to the appropriate mod_shout Makefile are much better, because they use SHOUT_BUILDDIR, which is already defined in that Makefile, and do not rely on some hard-coded path ("../../../../" for example). In other words, I think:
Move to the JIRA.
patch -d $(SHOUT_BUILDDIR) -p1 < hack_out_ogg.diff (which is what my patch proposes) is much better than: patch -p 6 -d ../../../../libs/libshout-2.2.2 < hack_out_ogg.diff (which is what Alexsey have proposed)
Move to the JIRA. Seriously. This has already been mentioned several times. This stuff DOES NOT BELONG HERE. Bugs are to be reported in one place, http://jira.freeswitch.org. That's it. No if's. and's, or but's. You're complaining that the developers are ignoring you, and at the same time you are making it HARDER for them to help you by posting information in two (possibly more) different places. Seems like there's already duplicate bug reports for this, those probably need to be merged as well. Move to the JIRA. -BDF
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
This message contains confidential information and is intended for those listed in the "To:", "CC:", and/or "BCC:" fields of the message header.If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version.
I don't want to act like a smug idiot...
You are.
It takes one to know one.
1. The original patch modifications (hack_out_ogg.diff) made by my patch no longer use "relative" paths (i.e. "../../") and thus comply with any version of the patch used.
Move to the JIRA.
Already there - http://jira.freeswitch.org/browse/FS-3923
2. My modifications made to the appropriate mod_shout Makefile are much better, because they use SHOUT_BUILDDIR, which is already defined in that Makefile, and do not rely on some hard-coded path ("../../../../" for example). In other words, I think:
Move to the JIRA.
Already there - http://jira.freeswitch.org/browse/FS-3923
patch -d $(SHOUT_BUILDDIR) -p1 < hack_out_ogg.diff (which is what my patch proposes) is much better than: patch -p 6 -d ../../../../libs/libshout-2.2.2 < hack_out_ogg.diff (which is what Alexsey have proposed)
Move to the JIRA. Seriously. This has already been mentioned several times. This stuff DOES NOT BELONG HERE. Bugs are to be reported in one place, http://jira.freeswitch.org. That's it. No if's. and's, or but's.
Are you blind or just stupid? For the last time - I HAVE ALREADY REPORTED THIS ON JIRA OVER 10 DAYS AGO - OTHERS HAVE DONE THE SAME 4 MONTHS AGO! Get it?
That's my point. No need to bring it on to the mailing list, where now you are spreading information on a specific bug report in several different places. Now devs have to spend MORE time trying to fit all the pieces together. Get it? On Wed, Feb 29, 2012 at 11:37 AM, Josh <mojo1736@privatedemail.net> wrote:
I don't want to act like a smug idiot...
You are.
It takes one to know one.
1. The original patch modifications (hack_out_ogg.diff) made by my patch no longer use "relative" paths (i.e. "../../") and thus comply with any version of the patch used.
Move to the JIRA.
Already there - http://jira.freeswitch.org/browse/FS-3923
2. My modifications made to the appropriate mod_shout Makefile are much better, because they use SHOUT_BUILDDIR, which is already defined in that Makefile, and do not rely on some hard-coded path
("../../../../"
for example). In other words, I think:
Move to the JIRA.
Already there - http://jira.freeswitch.org/browse/FS-3923
patch -d $(SHOUT_BUILDDIR) -p1 < hack_out_ogg.diff (which is what my patch proposes) is much better than: patch -p 6 -d ../../../../libs/libshout-2.2.2 < hack_out_ogg.diff (which is what Alexsey have proposed)
Move to the JIRA. Seriously. This has already been mentioned several times. This stuff DOES NOT BELONG HERE. Bugs are to be reported in one place, http://jira.freeswitch.org. That's it. No if's. and's, or but's.
Are you blind or just stupid? For the last time - I HAVE ALREADY REPORTED THIS ON JIRA OVER 10 DAYS AGO - OTHERS HAVE DONE THE SAME 4 MONTHS AGO! Get it?
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
-- Brian D. Foster Endigo Computer LLC Email: bdfoster@endigotech.com Phone: 317-429-1069 Indianapolis, Indiana, USA This message contains confidential information and is intended for those listed in the "To:", "CC:", and/or "BCC:" fields of the message header.If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version.
I'm going to interrupt here: FS-3923 has been marked as a duplicate of FS-3711 FS-3711 has been closed as resolved. End of line. There should be no reason to continue this discussion here. On 29 February 2012 16:39, Brian Foster <bdfoster@endigotech.com> wrote:
That's my point. No need to bring it on to the mailing list, where now you are spreading information on a specific bug report in several different places. Now devs have to spend MORE time trying to fit all the pieces together. Get it?
On Wed, Feb 29, 2012 at 11:37 AM, Josh <mojo1736@privatedemail.net> wrote:
I don't want to act like a smug idiot...
You are.
It takes one to know one.
1. The original patch modifications (hack_out_ogg.diff) made by my patch no longer use "relative" paths (i.e. "../../") and thus comply with any version of the patch used.
Move to the JIRA.
Already there - http://jira.freeswitch.org/browse/FS-3923
2. My modifications made to the appropriate mod_shout Makefile are much better, because they use SHOUT_BUILDDIR, which is already defined in that Makefile, and do not rely on some hard-coded path
("../../../../"
for example). In other words, I think:
Move to the JIRA.
Already there - http://jira.freeswitch.org/browse/FS-3923
patch -d $(SHOUT_BUILDDIR) -p1 < hack_out_ogg.diff (which is what my patch proposes) is much better than: patch -p 6 -d ../../../../libs/libshout-2.2.2 < hack_out_ogg.diff (which is what Alexsey have proposed)
Move to the JIRA. Seriously. This has already been mentioned several times. This stuff DOES NOT BELONG HERE. Bugs are to be reported in one place, http://jira.freeswitch.org. That's it. No if's. and's, or but's.
Are you blind or just stupid? For the last time - I HAVE ALREADY REPORTED THIS ON JIRA OVER 10 DAYS AGO - OTHERS HAVE DONE THE SAME 4 MONTHS AGO! Get it?
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
-- Brian D. Foster Endigo Computer LLC Email: bdfoster@endigotech.com Phone: 317-429-1069 Indianapolis, Indiana, USA
This message contains confidential information and is intended for those listed in the "To:", "CC:", and/or "BCC:" fields of the message header.If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version.
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
-- Andrew Cassidy BSc (Hons) MBCS Managing Director; Cassidy Web Services Ltd T: 03300 100 960 F: 03300 100 961 E: andrew@cassidywebservices.co.uk W: www.cassidywebservices.co.uk
That's my point. No need to bring it on to the mailing list, where now you are spreading information on a specific bug report in several different places. Now devs have to spend MORE time trying to fit all the pieces together. Get it? The FS devs don't need to piece anything "together from several different places" simply because all the information they need to make a decision is already there - on JIRA, and has been since November 2011 by the look of things. If this issue was resolved in a timely manner, then there won't be multiple reports of it and it is a dead cert I won't be wasting any of my time on this here with you.
As for using the ML for issues like these - if it wasn't for the ML and the people contributing in it making you, the FS devs, aware of it, I bet that same issue would still be gathering dust sitting "unresolved" on JIRA!
On Wed, Feb 29, 2012 at 12:00 PM, Josh <mojo1736@privatedemail.net> wrote:
That's my point. No need to bring it on to the mailing list, where now you are spreading information on a specific bug report in several different places. Now devs have to spend MORE time trying to fit all the pieces together. Get it? The FS devs don't need to piece anything "together from several different places" simply because all the information they need to make a decision is already there - on JIRA, and has been since November 2011 by the look of things. If this issue was resolved in a timely manner, then there won't be multiple reports of it and it is a dead cert I won't be wasting any of my time on this here with you.
As Ken stated, mod_shout is on it's way out.
As for using the ML for issues like these - if it wasn't for the ML and the people contributing in it making you, the FS devs, aware of it, I bet that same issue would still be gathering dust sitting "unresolved" on JIRA!
Did you get Andrew's message? He seemed pretty clear about the whole thing. FS-3923 has been marked as a duplicate of FS-3711. FS-3711 has been marked resolved and subsequently closed. Your replies are no longer valid, and weren't really valid in the first place. So that you and I are clear, I litterally just repeated the info that was posted earlier. Here's another thing that gets repeated more often than not on this thread. Bugs go in JIRA. End of story.
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
-- Brian D. Foster Endigo Computer LLC Email: bdfoster@endigotech.com Phone: 317-429-1069 Indianapolis, Indiana, USA This message contains confidential information and is intended for those listed in the "To:", "CC:", and/or "BCC:" fields of the message header.If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version.
Something else I forgot to mention, freeswitch devs are fixing bugs and making enhancements to the project and don't get paid for doing so. You are not their customer. Quit acting like one. On Wed, Feb 29, 2012 at 12:38 PM, Brian Foster <bdfoster@endigotech.com>wrote:
On Wed, Feb 29, 2012 at 12:00 PM, Josh <mojo1736@privatedemail.net> wrote:
That's my point. No need to bring it on to the mailing list, where now you are spreading information on a specific bug report in several different places. Now devs have to spend MORE time trying to fit all the pieces together. Get it? The FS devs don't need to piece anything "together from several different places" simply because all the information they need to make a decision is already there - on JIRA, and has been since November 2011 by the look of things. If this issue was resolved in a timely manner, then there won't be multiple reports of it and it is a dead cert I won't be wasting any of my time on this here with you.
As Ken stated, mod_shout is on it's way out.
As for using the ML for issues like these - if it wasn't for the ML and the people contributing in it making you, the FS devs, aware of it, I bet that same issue would still be gathering dust sitting "unresolved" on JIRA!
Did you get Andrew's message? He seemed pretty clear about the whole thing. FS-3923 has been marked as a duplicate of FS-3711. FS-3711 has been marked resolved and subsequently closed. Your replies are no longer valid, and weren't really valid in the first place.
So that you and I are clear, I litterally just repeated the info that was posted earlier.
Here's another thing that gets repeated more often than not on this thread. Bugs go in JIRA. End of story.
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
-- Brian D. Foster Endigo Computer LLC Email: bdfoster@endigotech.com Phone: 317-429-1069 Indianapolis, Indiana, USA
This message contains confidential information and is intended for those listed in the "To:", "CC:", and/or "BCC:" fields of the message header.If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version.
-- Brian D. Foster Endigo Computer LLC Email: bdfoster@endigotech.com Phone: 317-429-1069 Indianapolis, Indiana, USA This message contains confidential information and is intended for those listed in the "To:", "CC:", and/or "BCC:" fields of the message header.If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version.
On 29-02-12 18:00, Josh wrote:
That's my point. No need to bring it on to the mailing list, where now you are spreading information on a specific bug report in several different places. Now devs have to spend MORE time trying to fit all the pieces together. Get it? The FS devs don't need to piece anything "together from several different places" simply because all the information they need to make a decision is already there - on JIRA, and has been since November 2011 by the look of things. If this issue was resolved in a timely manner, then there won't be multiple reports of it and it is a dead cert I won't be wasting any of my time on this here with you.
Would you mind toning it done a bit and be a bit more courteous? Frankly I perceive your comments as increasingly rude, especially since you have paid ZERO for this fabulous piece of software and yet you feel it is appropriate to mention again and again that - in your opinion - the developers are slow and don't move forward as fast as you seem to demand they should. You can always ask your money back and write your own FreeSWITCH... Regards, Patrick
This message thread has been closed. Please continue any other technical discussion of this issue on jira. Mike On Feb 29, 2012, at 1:46 PM, Patrick Lists wrote:
On 29-02-12 18:00, Josh wrote:
That's my point. No need to bring it on to the mailing list, where now you are spreading information on a specific bug report in several different places. Now devs have to spend MORE time trying to fit all the pieces together. Get it? The FS devs don't need to piece anything "together from several different places" simply because all the information they need to make a decision is already there - on JIRA, and has been since November 2011 by the look of things. If this issue was resolved in a timely manner, then there won't be multiple reports of it and it is a dead cert I won't be wasting any of my time on this here with you.
Would you mind toning it done a bit and be a bit more courteous? Frankly I perceive your comments as increasingly rude, especially since you have paid ZERO for this fabulous piece of software and yet you feel it is appropriate to mention again and again that - in your opinion - the developers are slow and don't move forward as fast as you seem to demand they should. You can always ask your money back and write your own FreeSWITCH...
Regards, Patrick
mod_shout is on its way out so this is pretty much dead horse... No the functionality isnt going away there is just a better module coming to replace it... (see mod_vlc) The mod will remain for a bit, but going forward this code will end up going to the attic K On 2/29/12 9:44 AM, "Josh" <mojo1736@privatedemail.net> wrote:
Josh, Please test the patch at
http://jira.freeswitch.org/browse/FS-3711
testpatch.txt
which is provided by Alexey.
I don't want to act like a smug idiot, but I like my version of the patch better for (at least) 2 reasons:
1. The original patch modifications (hack_out_ogg.diff) made by my patch no longer use "relative" paths (i.e. "../../") and thus comply with any version of the patch used.
2. My modifications made to the appropriate mod_shout Makefile are much better, because they use SHOUT_BUILDDIR, which is already defined in that Makefile, and do not rely on some hard-coded path ("../../../../" for example). In other words, I think:
patch -d $(SHOUT_BUILDDIR) -p1 < hack_out_ogg.diff (which is what my patch proposes) is much better than: patch -p 6 -d ../../../../libs/libshout-2.2.2 < hack_out_ogg.diff (which is what Alexsey have proposed)
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
mod_shout is on its way out so this is pretty much dead horse...
No the functionality isnt going away there is just a better module coming to replace it... (see mod_vlc)
The mod will remain for a bit, but going forward this code will end up going to the attic
Yeah, I gathered as much by looking at that code and a few of the comments left there.
participants (9)
-
Andrew Cassidy
-
Brian Foster
-
Jeff Lenk
-
Josh
-
Ken Rice
-
Lubimov Alexey
-
Michael Collins
-
Michael Jerris
-
Patrick Lists