Hi all,

I had been debugging a reported issue for blue that turned out to be an issue specific to 64-bit Linux. I finally found the resolution today, and it turned out that Csound interfaces, at least for Java, require swig 2.0.x. The latest in Debian stable is 1.3.0. If you use apt-get build-dep with Csound it will not download 1.3.0. I ended up adding Debian back ports repo to install swig 2.0 and had to symlink swig2.0 to swig in /usr/bin. Suffice to say, I don't know if the Csound interface packages in Debian 64-bit will work unless they are built with newer swig.

Thought it worth mentioning, thanks!
Steven

Hi Felipe,

I'm not sure about all the details about how the debian package is
built, but it seems to me to be a packaging/building issue.  In CS6, I
just modified the swig finder to be:

FIND_PACKAGE(SWIG 2.0)

to force 2.0 as a minimum. If this is added to CS5, would that then
build in Debian's build systems if swig 2.0 isn't in stable?

Thanks!
steven

On Thu, Dec 20, 2012 at 12:43 AM, Felipe Sateler  wrote:
> Is that for building newer csound? Or for stock debian csound?
>
>
> On Wed, Dec 19, 2012 at 9:03 PM, Steven Yi  wrote:
>>
>> Hi all,
>>
>> I had been debugging a reported issue for blue that turned out to be an
>> issue specific to 64-bit Linux. I finally found the resolution today, and it
>> turned out that Csound interfaces, at least for Java, require swig 2.0.x.
>> The latest in Debian stable is 1.3.0. If you use apt-get build-dep with
>> Csound it will not download 1.3.0. I ended up adding Debian back ports repo
>> to install swig 2.0 and had to symlink swig2.0 to swig in /usr/bin. Suffice
>> to say, I don't know if the Csound interface packages in Debian 64-bit will
>> work unless they are built with newer swig.
>>
>> Thought it worth mentioning, thanks!
>> Steven
>
>
>
>
> --
>
> Saludos,
> Felipe Sateler
>
> ------------------------------------------------------------------------------
> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
> Remotely access PCs and mobile devices and provide instant support
> Improve your efficiency, and focus on delivering more value-add services
> Discover what IT Professionals Know. Rescue delivers
> http://p.sf.net/sfu/logmein_12329d2d
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

If you put that in cs5 branch then it wouldn't build in debian stable.

But my question was another: Csound used to build with swig 1.x. At
some point, csound started requiring swig 2.x. I was wondering when
was that?. If csound 5.12 (what was shipped with debian squeeze) works
with swig 1.x then everything is OK from debian's point of view (it's
just old software building with old software). If newer csounds
require newer software to build than is available in debian stable,
then there is not much we can do (except telling the user it won't
work and disable it when building).

In other words, my concern is whether the csnd-java package shipped by
debian is broken or not.

On Thu, Dec 20, 2012 at 9:50 AM, Steven Yi  wrote:
> Hi Felipe,
>
> I'm not sure about all the details about how the debian package is
> built, but it seems to me to be a packaging/building issue.  In CS6, I
> just modified the swig finder to be:
>
> FIND_PACKAGE(SWIG 2.0)
>
> to force 2.0 as a minimum. If this is added to CS5, would that then
> build in Debian's build systems if swig 2.0 isn't in stable?
>
> Thanks!
> steven
>
> On Thu, Dec 20, 2012 at 12:43 AM, Felipe Sateler  wrote:
>> Is that for building newer csound? Or for stock debian csound?
>>
>>
>> On Wed, Dec 19, 2012 at 9:03 PM, Steven Yi  wrote:
>>>
>>> Hi all,
>>>
>>> I had been debugging a reported issue for blue that turned out to be an
>>> issue specific to 64-bit Linux. I finally found the resolution today, and it
>>> turned out that Csound interfaces, at least for Java, require swig 2.0.x.
>>> The latest in Debian stable is 1.3.0. If you use apt-get build-dep with
>>> Csound it will not download 1.3.0. I ended up adding Debian back ports repo
>>> to install swig 2.0 and had to symlink swig2.0 to swig in /usr/bin. Suffice
>>> to say, I don't know if the Csound interface packages in Debian 64-bit will
>>> work unless they are built with newer swig.
>>>
>>> Thought it worth mentioning, thanks!
>>> Steven
>>
>>
>>
>>
>> --
>>
>> Saludos,
>> Felipe Sateler
>>
>> ------------------------------------------------------------------------------
>> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
>> Remotely access PCs and mobile devices and provide instant support
>> Improve your efficiency, and focus on delivering more value-add services
>> Discover what IT Professionals Know. Rescue delivers
>> http://p.sf.net/sfu/logmein_12329d2d
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
> ------------------------------------------------------------------------------
> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
> Remotely access PCs and mobile devices and provide instant support
> Improve your efficiency, and focus on delivering more value-add services
> Discover what IT Professionals Know. Rescue delivers
> http://p.sf.net/sfu/logmein_12329d2d
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel



--

Saludos,
Felipe Sateler

------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Well, the thing is, it will build just fine with older swig, it just
doesn't work for setting MYFLT pointers and CsoundMYFLTArray(with Java
at least)  I don't have a 32-bit install of debian stable here so I'm
not sure if the Swig issue affects 32-bit. I have a 64-bit debian and
32-bit ubuntu (and 32-bit fedora and 64-bit suse).  I can install
32-bit debian and see what happens if you need.

On Thu, Dec 20, 2012 at 2:23 PM, Felipe Sateler  wrote:
> If you put that in cs5 branch then it wouldn't build in debian stable.
>
> But my question was another: Csound used to build with swig 1.x. At
> some point, csound started requiring swig 2.x. I was wondering when
> was that?. If csound 5.12 (what was shipped with debian squeeze) works
> with swig 1.x then everything is OK from debian's point of view (it's
> just old software building with old software). If newer csounds
> require newer software to build than is available in debian stable,
> then there is not much we can do (except telling the user it won't
> work and disable it when building).
>
> In other words, my concern is whether the csnd-java package shipped by
> debian is broken or not.
>
> On Thu, Dec 20, 2012 at 9:50 AM, Steven Yi  wrote:
>> Hi Felipe,
>>
>> I'm not sure about all the details about how the debian package is
>> built, but it seems to me to be a packaging/building issue.  In CS6, I
>> just modified the swig finder to be:
>>
>> FIND_PACKAGE(SWIG 2.0)
>>
>> to force 2.0 as a minimum. If this is added to CS5, would that then
>> build in Debian's build systems if swig 2.0 isn't in stable?
>>
>> Thanks!
>> steven
>>
>> On Thu, Dec 20, 2012 at 12:43 AM, Felipe Sateler  wrote:
>>> Is that for building newer csound? Or for stock debian csound?
>>>
>>>
>>> On Wed, Dec 19, 2012 at 9:03 PM, Steven Yi  wrote:
>>>>
>>>> Hi all,
>>>>
>>>> I had been debugging a reported issue for blue that turned out to be an
>>>> issue specific to 64-bit Linux. I finally found the resolution today, and it
>>>> turned out that Csound interfaces, at least for Java, require swig 2.0.x.
>>>> The latest in Debian stable is 1.3.0. If you use apt-get build-dep with
>>>> Csound it will not download 1.3.0. I ended up adding Debian back ports repo
>>>> to install swig 2.0 and had to symlink swig2.0 to swig in /usr/bin. Suffice
>>>> to say, I don't know if the Csound interface packages in Debian 64-bit will
>>>> work unless they are built with newer swig.
>>>>
>>>> Thought it worth mentioning, thanks!
>>>> Steven
>>>
>>>
>>>
>>>
>>> --
>>>
>>> Saludos,
>>> Felipe Sateler
>>>
>>> ------------------------------------------------------------------------------
>>> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
>>> Remotely access PCs and mobile devices and provide instant support
>>> Improve your efficiency, and focus on delivering more value-add services
>>> Discover what IT Professionals Know. Rescue delivers
>>> http://p.sf.net/sfu/logmein_12329d2d
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>
>> ------------------------------------------------------------------------------
>> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
>> Remotely access PCs and mobile devices and provide instant support
>> Improve your efficiency, and focus on delivering more value-add services
>> Discover what IT Professionals Know. Rescue delivers
>> http://p.sf.net/sfu/logmein_12329d2d
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
>
> --
>
> Saludos,
> Felipe Sateler
>
> ------------------------------------------------------------------------------
> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
> Remotely access PCs and mobile devices and provide instant support
> Improve your efficiency, and focus on delivering more value-add services
> Discover what IT Professionals Know. Rescue delivers
> http://p.sf.net/sfu/logmein_12329d2d
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

But is the problem with stock debian software? Or only when building
newer csound?

The csound version currently in stable is over 2 years old now, I'd be
very suprised if it didn't work (either that or nobody really used the
java bindings!) as shipped by debian.


On Thu, Dec 20, 2012 at 11:44 AM, Steven Yi  wrote:
> Well, the thing is, it will build just fine with older swig, it just
> doesn't work for setting MYFLT pointers and CsoundMYFLTArray(with Java
> at least)  I don't have a 32-bit install of debian stable here so I'm
> not sure if the Swig issue affects 32-bit. I have a 64-bit debian and
> 32-bit ubuntu (and 32-bit fedora and 64-bit suse).  I can install
> 32-bit debian and see what happens if you need.
>
> On Thu, Dec 20, 2012 at 2:23 PM, Felipe Sateler  wrote:
>> If you put that in cs5 branch then it wouldn't build in debian stable.
>>
>> But my question was another: Csound used to build with swig 1.x. At
>> some point, csound started requiring swig 2.x. I was wondering when
>> was that?. If csound 5.12 (what was shipped with debian squeeze) works
>> with swig 1.x then everything is OK from debian's point of view (it's
>> just old software building with old software). If newer csounds
>> require newer software to build than is available in debian stable,
>> then there is not much we can do (except telling the user it won't
>> work and disable it when building).
>>
>> In other words, my concern is whether the csnd-java package shipped by
>> debian is broken or not.
>>
>> On Thu, Dec 20, 2012 at 9:50 AM, Steven Yi  wrote:
>>> Hi Felipe,
>>>
>>> I'm not sure about all the details about how the debian package is
>>> built, but it seems to me to be a packaging/building issue.  In CS6, I
>>> just modified the swig finder to be:
>>>
>>> FIND_PACKAGE(SWIG 2.0)
>>>
>>> to force 2.0 as a minimum. If this is added to CS5, would that then
>>> build in Debian's build systems if swig 2.0 isn't in stable?
>>>
>>> Thanks!
>>> steven
>>>
>>> On Thu, Dec 20, 2012 at 12:43 AM, Felipe Sateler  wrote:
>>>> Is that for building newer csound? Or for stock debian csound?
>>>>
>>>>
>>>> On Wed, Dec 19, 2012 at 9:03 PM, Steven Yi  wrote:
>>>>>
>>>>> Hi all,
>>>>>
>>>>> I had been debugging a reported issue for blue that turned out to be an
>>>>> issue specific to 64-bit Linux. I finally found the resolution today, and it
>>>>> turned out that Csound interfaces, at least for Java, require swig 2.0.x.
>>>>> The latest in Debian stable is 1.3.0. If you use apt-get build-dep with
>>>>> Csound it will not download 1.3.0. I ended up adding Debian back ports repo
>>>>> to install swig 2.0 and had to symlink swig2.0 to swig in /usr/bin. Suffice
>>>>> to say, I don't know if the Csound interface packages in Debian 64-bit will
>>>>> work unless they are built with newer swig.
>>>>>
>>>>> Thought it worth mentioning, thanks!
>>>>> Steven
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Saludos,
>>>> Felipe Sateler
>>>>
>>>> ------------------------------------------------------------------------------
>>>> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
>>>> Remotely access PCs and mobile devices and provide instant support
>>>> Improve your efficiency, and focus on delivering more value-add services
>>>> Discover what IT Professionals Know. Rescue delivers
>>>> http://p.sf.net/sfu/logmein_12329d2d
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>
>>>
>>> ------------------------------------------------------------------------------
>>> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
>>> Remotely access PCs and mobile devices and provide instant support
>>> Improve your efficiency, and focus on delivering more value-add services
>>> Discover what IT Professionals Know. Rescue delivers
>>> http://p.sf.net/sfu/logmein_12329d2d
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>>
>> --
>>
>> Saludos,
>> Felipe Sateler
>>
>> ------------------------------------------------------------------------------
>> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
>> Remotely access PCs and mobile devices and provide instant support
>> Improve your efficiency, and focus on delivering more value-add services
>> Discover what IT Professionals Know. Rescue delivers
>> http://p.sf.net/sfu/logmein_12329d2d
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
> ------------------------------------------------------------------------------
> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
> Remotely access PCs and mobile devices and provide instant support
> Improve your efficiency, and focus on delivering more value-add services
> Discover what IT Professionals Know. Rescue delivers
> http://p.sf.net/sfu/logmein_12329d2d
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel



-- 

Saludos,
Felipe Sateler

------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

> Well, the thing is, it will build just fine with older swig, it just
> doesn't work for setting MYFLT pointers and CsoundMYFLTArray(with Java
> at least)  I don't have a 32-bit install of debian stable here so I'm
> not sure if the Swig issue affects 32-bit. I have a 64-bit debian and
> 32-bit ubuntu (and 32-bit fedora and 64-bit suse).  I can install
> 32-bit debian and see what happens if you need.
>

Not sure if this relates but for a long time the swig on my 64bit Linux
was plain broken, and I had to edit the swig output every time to make it
valid C.  Related to va_args.  Never *quite* got to write the automated
script to fix the C but I did bitch about it at the time on this list

==John ff


------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Ah, I see what you're saying.  I'm installing csound here from apt-get
to check.  The issue originally arose that a previous version of blue
worked but the newer ones didn't, and the change I isolated it to was
setting of channel values via SetChannel rather than caching the MYFLT
pointer which I moved to for efficiency reasons.  It might very well
be that no one had use that aspect of the Java binding until that, so
at the time it worked fine.

Update: Just tested with 5.12 from apt-get.  It did not work in the
same way as compiling with swig 1.3.  So that is broken IMO for
64-bit.  (Did not test on 32-bit).

I don't know when stable gets updated for Debian; for now, most blue
users on Linux are savvy enough to compile csound I think, but it'd be
nicer if what is available is up to date and working. I know you had
pushed an updated Csound package to testing (for that interface
generation bug via cmake).  Does that package have a requirement for
swig 2.0+?

Thanks!
steven

On Thu, Dec 20, 2012 at 3:07 PM, Felipe Sateler  wrote:
> But is the problem with stock debian software? Or only when building
> newer csound?
>
> The csound version currently in stable is over 2 years old now, I'd be
> very suprised if it didn't work (either that or nobody really used the
> java bindings!) as shipped by debian.
>
>
> On Thu, Dec 20, 2012 at 11:44 AM, Steven Yi  wrote:
>> Well, the thing is, it will build just fine with older swig, it just
>> doesn't work for setting MYFLT pointers and CsoundMYFLTArray(with Java
>> at least)  I don't have a 32-bit install of debian stable here so I'm
>> not sure if the Swig issue affects 32-bit. I have a 64-bit debian and
>> 32-bit ubuntu (and 32-bit fedora and 64-bit suse).  I can install
>> 32-bit debian and see what happens if you need.
>>
>> On Thu, Dec 20, 2012 at 2:23 PM, Felipe Sateler  wrote:
>>> If you put that in cs5 branch then it wouldn't build in debian stable.
>>>
>>> But my question was another: Csound used to build with swig 1.x. At
>>> some point, csound started requiring swig 2.x. I was wondering when
>>> was that?. If csound 5.12 (what was shipped with debian squeeze) works
>>> with swig 1.x then everything is OK from debian's point of view (it's
>>> just old software building with old software). If newer csounds
>>> require newer software to build than is available in debian stable,
>>> then there is not much we can do (except telling the user it won't
>>> work and disable it when building).
>>>
>>> In other words, my concern is whether the csnd-java package shipped by
>>> debian is broken or not.
>>>
>>> On Thu, Dec 20, 2012 at 9:50 AM, Steven Yi  wrote:
>>>> Hi Felipe,
>>>>
>>>> I'm not sure about all the details about how the debian package is
>>>> built, but it seems to me to be a packaging/building issue.  In CS6, I
>>>> just modified the swig finder to be:
>>>>
>>>> FIND_PACKAGE(SWIG 2.0)
>>>>
>>>> to force 2.0 as a minimum. If this is added to CS5, would that then
>>>> build in Debian's build systems if swig 2.0 isn't in stable?
>>>>
>>>> Thanks!
>>>> steven
>>>>
>>>> On Thu, Dec 20, 2012 at 12:43 AM, Felipe Sateler  wrote:
>>>>> Is that for building newer csound? Or for stock debian csound?
>>>>>
>>>>>
>>>>> On Wed, Dec 19, 2012 at 9:03 PM, Steven Yi  wrote:
>>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> I had been debugging a reported issue for blue that turned out to be an
>>>>>> issue specific to 64-bit Linux. I finally found the resolution today, and it
>>>>>> turned out that Csound interfaces, at least for Java, require swig 2.0.x.
>>>>>> The latest in Debian stable is 1.3.0. If you use apt-get build-dep with
>>>>>> Csound it will not download 1.3.0. I ended up adding Debian back ports repo
>>>>>> to install swig 2.0 and had to symlink swig2.0 to swig in /usr/bin. Suffice
>>>>>> to say, I don't know if the Csound interface packages in Debian 64-bit will
>>>>>> work unless they are built with newer swig.
>>>>>>
>>>>>> Thought it worth mentioning, thanks!
>>>>>> Steven
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> Saludos,
>>>>> Felipe Sateler
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
>>>>> Remotely access PCs and mobile devices and provide instant support
>>>>> Improve your efficiency, and focus on delivering more value-add services
>>>>> Discover what IT Professionals Know. Rescue delivers
>>>>> http://p.sf.net/sfu/logmein_12329d2d
>>>>> _______________________________________________
>>>>> Csound-devel mailing list
>>>>> Csound-devel@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
>>>> Remotely access PCs and mobile devices and provide instant support
>>>> Improve your efficiency, and focus on delivering more value-add services
>>>> Discover what IT Professionals Know. Rescue delivers
>>>> http://p.sf.net/sfu/logmein_12329d2d
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>>
>>>
>>> --
>>>
>>> Saludos,
>>> Felipe Sateler
>>>
>>> ------------------------------------------------------------------------------
>>> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
>>> Remotely access PCs and mobile devices and provide instant support
>>> Improve your efficiency, and focus on delivering more value-add services
>>> Discover what IT Professionals Know. Rescue delivers
>>> http://p.sf.net/sfu/logmein_12329d2d
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>> ------------------------------------------------------------------------------
>> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
>> Remotely access PCs and mobile devices and provide instant support
>> Improve your efficiency, and focus on delivering more value-add services
>> Discover what IT Professionals Know. Rescue delivers
>> http://p.sf.net/sfu/logmein_12329d2d
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
>
> --
>
> Saludos,
> Felipe Sateler
>
> ------------------------------------------------------------------------------
> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
> Remotely access PCs and mobile devices and provide instant support
> Improve your efficiency, and focus on delivering more value-add services
> Discover what IT Professionals Know. Rescue delivers
> http://p.sf.net/sfu/logmein_12329d2d
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Hmm, so we have a buggy package in stable...

The problem here is really that swig is buggy at version 1.x. Stable
updates are as minimal as possible. This means that updating to swig
2.x is off the table. This in turn means the only real option is to
remove the libcsnd-java package[1], or ignore the bug. I'm not quite
sure which is preferable, given that the main user of the package
fails with this version.

For testing, csound is already built with swig 2.x. There is no
requirement, though, it just happens that swig is now at version 2 in
the archive (so the version in testing should not have this bug).

[1] The debian release managers consider bugs at a distribution-wide
scale. From that point of view, it is (1) better to not provide a
package than to provide a broken one, and (2) better to remove a
package than risk breaking others in order to fix a bug. Specially if
the package in question is relatively little used.

On Thu, Dec 20, 2012 at 1:15 PM, Steven Yi  wrote:
> Ah, I see what you're saying.  I'm installing csound here from apt-get
> to check.  The issue originally arose that a previous version of blue
> worked but the newer ones didn't, and the change I isolated it to was
> setting of channel values via SetChannel rather than caching the MYFLT
> pointer which I moved to for efficiency reasons.  It might very well
> be that no one had use that aspect of the Java binding until that, so
> at the time it worked fine.
>
> Update: Just tested with 5.12 from apt-get.  It did not work in the
> same way as compiling with swig 1.3.  So that is broken IMO for
> 64-bit.  (Did not test on 32-bit).
>
> I don't know when stable gets updated for Debian; for now, most blue
> users on Linux are savvy enough to compile csound I think, but it'd be
> nicer if what is available is up to date and working. I know you had
> pushed an updated Csound package to testing (for that interface
> generation bug via cmake).  Does that package have a requirement for
> swig 2.0+?
>
> Thanks!
> steven
>
> On Thu, Dec 20, 2012 at 3:07 PM, Felipe Sateler  wrote:
>> But is the problem with stock debian software? Or only when building
>> newer csound?
>>
>> The csound version currently in stable is over 2 years old now, I'd be
>> very suprised if it didn't work (either that or nobody really used the
>> java bindings!) as shipped by debian.
>>
>>
>> On Thu, Dec 20, 2012 at 11:44 AM, Steven Yi  wrote:
>>> Well, the thing is, it will build just fine with older swig, it just
>>> doesn't work for setting MYFLT pointers and CsoundMYFLTArray(with Java
>>> at least)  I don't have a 32-bit install of debian stable here so I'm
>>> not sure if the Swig issue affects 32-bit. I have a 64-bit debian and
>>> 32-bit ubuntu (and 32-bit fedora and 64-bit suse).  I can install
>>> 32-bit debian and see what happens if you need.
>>>
>>> On Thu, Dec 20, 2012 at 2:23 PM, Felipe Sateler  wrote:
>>>> If you put that in cs5 branch then it wouldn't build in debian stable.
>>>>
>>>> But my question was another: Csound used to build with swig 1.x. At
>>>> some point, csound started requiring swig 2.x. I was wondering when
>>>> was that?. If csound 5.12 (what was shipped with debian squeeze) works
>>>> with swig 1.x then everything is OK from debian's point of view (it's
>>>> just old software building with old software). If newer csounds
>>>> require newer software to build than is available in debian stable,
>>>> then there is not much we can do (except telling the user it won't
>>>> work and disable it when building).
>>>>
>>>> In other words, my concern is whether the csnd-java package shipped by
>>>> debian is broken or not.
>>>>
>>>> On Thu, Dec 20, 2012 at 9:50 AM, Steven Yi  wrote:
>>>>> Hi Felipe,
>>>>>
>>>>> I'm not sure about all the details about how the debian package is
>>>>> built, but it seems to me to be a packaging/building issue.  In CS6, I
>>>>> just modified the swig finder to be:
>>>>>
>>>>> FIND_PACKAGE(SWIG 2.0)
>>>>>
>>>>> to force 2.0 as a minimum. If this is added to CS5, would that then
>>>>> build in Debian's build systems if swig 2.0 isn't in stable?
>>>>>
>>>>> Thanks!
>>>>> steven
>>>>>
>>>>> On Thu, Dec 20, 2012 at 12:43 AM, Felipe Sateler  wrote:
>>>>>> Is that for building newer csound? Or for stock debian csound?
>>>>>>
>>>>>>
>>>>>> On Wed, Dec 19, 2012 at 9:03 PM, Steven Yi  wrote:
>>>>>>>
>>>>>>> Hi all,
>>>>>>>
>>>>>>> I had been debugging a reported issue for blue that turned out to be an
>>>>>>> issue specific to 64-bit Linux. I finally found the resolution today, and it
>>>>>>> turned out that Csound interfaces, at least for Java, require swig 2.0.x.
>>>>>>> The latest in Debian stable is 1.3.0. If you use apt-get build-dep with
>>>>>>> Csound it will not download 1.3.0. I ended up adding Debian back ports repo
>>>>>>> to install swig 2.0 and had to symlink swig2.0 to swig in /usr/bin. Suffice
>>>>>>> to say, I don't know if the Csound interface packages in Debian 64-bit will
>>>>>>> work unless they are built with newer swig.
>>>>>>>
>>>>>>> Thought it worth mentioning, thanks!
>>>>>>> Steven
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>> Saludos,
>>>>>> Felipe Sateler
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
>>>>>> Remotely access PCs and mobile devices and provide instant support
>>>>>> Improve your efficiency, and focus on delivering more value-add services
>>>>>> Discover what IT Professionals Know. Rescue delivers
>>>>>> http://p.sf.net/sfu/logmein_12329d2d
>>>>>> _______________________________________________
>>>>>> Csound-devel mailing list
>>>>>> Csound-devel@lists.sourceforge.net
>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
>>>>> Remotely access PCs and mobile devices and provide instant support
>>>>> Improve your efficiency, and focus on delivering more value-add services
>>>>> Discover what IT Professionals Know. Rescue delivers
>>>>> http://p.sf.net/sfu/logmein_12329d2d
>>>>> _______________________________________________
>>>>> Csound-devel mailing list
>>>>> Csound-devel@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Saludos,
>>>> Felipe Sateler
>>>>
>>>> ------------------------------------------------------------------------------
>>>> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
>>>> Remotely access PCs and mobile devices and provide instant support
>>>> Improve your efficiency, and focus on delivering more value-add services
>>>> Discover what IT Professionals Know. Rescue delivers
>>>> http://p.sf.net/sfu/logmein_12329d2d
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>> ------------------------------------------------------------------------------
>>> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
>>> Remotely access PCs and mobile devices and provide instant support
>>> Improve your efficiency, and focus on delivering more value-add services
>>> Discover what IT Professionals Know. Rescue delivers
>>> http://p.sf.net/sfu/logmein_12329d2d
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>>
>> --
>>
>> Saludos,
>> Felipe Sateler
>>
>> ------------------------------------------------------------------------------
>> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
>> Remotely access PCs and mobile devices and provide instant support
>> Improve your efficiency, and focus on delivering more value-add services
>> Discover what IT Professionals Know. Rescue delivers
>> http://p.sf.net/sfu/logmein_12329d2d
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
> ------------------------------------------------------------------------------
> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
> Remotely access PCs and mobile devices and provide instant support
> Improve your efficiency, and focus on delivering more value-add services
> Discover what IT Professionals Know. Rescue delivers
> http://p.sf.net/sfu/logmein_12329d2d
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel



-- 

Saludos,
Felipe Sateler

------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Hi Felipe,

I think we can ignore it then if testing as testing using swig 2.0. As
long as I have a workaround for a known issue, then it should be
alright. There may be other projects which do not use CsoundMYFLTArray
but do use Java, so this may be fine.  I'd just like to make sure that
this is being accounted for in future releases.  Can we make an
explicit dependency on swig 2.0+ for future builds?  Also, I noticed
that using build-dep with debian stable did not bring in flex/bison.
I assume this is because it is using a much older Csound before the
new parser became the standard.  Do the testing builds explicitly add
flex and bison, and if not, can we add that?

Thanks!
steven

On Thu, Dec 20, 2012 at 12:51 PM, Felipe Sateler  wrote:
> Hmm, so we have a buggy package in stable...
>
> The problem here is really that swig is buggy at version 1.x. Stable
> updates are as minimal as possible. This means that updating to swig
> 2.x is off the table. This in turn means the only real option is to
> remove the libcsnd-java package[1], or ignore the bug. I'm not quite
> sure which is preferable, given that the main user of the package
> fails with this version.
>
> For testing, csound is already built with swig 2.x. There is no
> requirement, though, it just happens that swig is now at version 2 in
> the archive (so the version in testing should not have this bug).
>
> [1] The debian release managers consider bugs at a distribution-wide
> scale. From that point of view, it is (1) better to not provide a
> package than to provide a broken one, and (2) better to remove a
> package than risk breaking others in order to fix a bug. Specially if
> the package in question is relatively little used.
>
> On Thu, Dec 20, 2012 at 1:15 PM, Steven Yi  wrote:
>> Ah, I see what you're saying.  I'm installing csound here from apt-get
>> to check.  The issue originally arose that a previous version of blue
>> worked but the newer ones didn't, and the change I isolated it to was
>> setting of channel values via SetChannel rather than caching the MYFLT
>> pointer which I moved to for efficiency reasons.  It might very well
>> be that no one had use that aspect of the Java binding until that, so
>> at the time it worked fine.
>>
>> Update: Just tested with 5.12 from apt-get.  It did not work in the
>> same way as compiling with swig 1.3.  So that is broken IMO for
>> 64-bit.  (Did not test on 32-bit).
>>
>> I don't know when stable gets updated for Debian; for now, most blue
>> users on Linux are savvy enough to compile csound I think, but it'd be
>> nicer if what is available is up to date and working. I know you had
>> pushed an updated Csound package to testing (for that interface
>> generation bug via cmake).  Does that package have a requirement for
>> swig 2.0+?
>>
>> Thanks!
>> steven
>>
>> On Thu, Dec 20, 2012 at 3:07 PM, Felipe Sateler  wrote:
>>> But is the problem with stock debian software? Or only when building
>>> newer csound?
>>>
>>> The csound version currently in stable is over 2 years old now, I'd be
>>> very suprised if it didn't work (either that or nobody really used the
>>> java bindings!) as shipped by debian.
>>>
>>>
>>> On Thu, Dec 20, 2012 at 11:44 AM, Steven Yi  wrote:
>>>> Well, the thing is, it will build just fine with older swig, it just
>>>> doesn't work for setting MYFLT pointers and CsoundMYFLTArray(with Java
>>>> at least)  I don't have a 32-bit install of debian stable here so I'm
>>>> not sure if the Swig issue affects 32-bit. I have a 64-bit debian and
>>>> 32-bit ubuntu (and 32-bit fedora and 64-bit suse).  I can install
>>>> 32-bit debian and see what happens if you need.
>>>>
>>>> On Thu, Dec 20, 2012 at 2:23 PM, Felipe Sateler  wrote:
>>>>> If you put that in cs5 branch then it wouldn't build in debian stable.
>>>>>
>>>>> But my question was another: Csound used to build with swig 1.x. At
>>>>> some point, csound started requiring swig 2.x. I was wondering when
>>>>> was that?. If csound 5.12 (what was shipped with debian squeeze) works
>>>>> with swig 1.x then everything is OK from debian's point of view (it's
>>>>> just old software building with old software). If newer csounds
>>>>> require newer software to build than is available in debian stable,
>>>>> then there is not much we can do (except telling the user it won't
>>>>> work and disable it when building).
>>>>>
>>>>> In other words, my concern is whether the csnd-java package shipped by
>>>>> debian is broken or not.
>>>>>
>>>>> On Thu, Dec 20, 2012 at 9:50 AM, Steven Yi  wrote:
>>>>>> Hi Felipe,
>>>>>>
>>>>>> I'm not sure about all the details about how the debian package is
>>>>>> built, but it seems to me to be a packaging/building issue.  In CS6, I
>>>>>> just modified the swig finder to be:
>>>>>>
>>>>>> FIND_PACKAGE(SWIG 2.0)
>>>>>>
>>>>>> to force 2.0 as a minimum. If this is added to CS5, would that then
>>>>>> build in Debian's build systems if swig 2.0 isn't in stable?
>>>>>>
>>>>>> Thanks!
>>>>>> steven
>>>>>>
>>>>>> On Thu, Dec 20, 2012 at 12:43 AM, Felipe Sateler  wrote:
>>>>>>> Is that for building newer csound? Or for stock debian csound?
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Dec 19, 2012 at 9:03 PM, Steven Yi  wrote:
>>>>>>>>
>>>>>>>> Hi all,
>>>>>>>>
>>>>>>>> I had been debugging a reported issue for blue that turned out to be an
>>>>>>>> issue specific to 64-bit Linux. I finally found the resolution today, and it
>>>>>>>> turned out that Csound interfaces, at least for Java, require swig 2.0.x.
>>>>>>>> The latest in Debian stable is 1.3.0. If you use apt-get build-dep with
>>>>>>>> Csound it will not download 1.3.0. I ended up adding Debian back ports repo
>>>>>>>> to install swig 2.0 and had to symlink swig2.0 to swig in /usr/bin. Suffice
>>>>>>>> to say, I don't know if the Csound interface packages in Debian 64-bit will
>>>>>>>> work unless they are built with newer swig.
>>>>>>>>
>>>>>>>> Thought it worth mentioning, thanks!
>>>>>>>> Steven
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>>
>>>>>>> Saludos,
>>>>>>> Felipe Sateler
>>>>>>>
>>>>>>> ------------------------------------------------------------------------------
>>>>>>> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
>>>>>>> Remotely access PCs and mobile devices and provide instant support
>>>>>>> Improve your efficiency, and focus on delivering more value-add services
>>>>>>> Discover what IT Professionals Know. Rescue delivers
>>>>>>> http://p.sf.net/sfu/logmein_12329d2d
>>>>>>> _______________________________________________
>>>>>>> Csound-devel mailing list
>>>>>>> Csound-devel@lists.sourceforge.net
>>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>>>
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
>>>>>> Remotely access PCs and mobile devices and provide instant support
>>>>>> Improve your efficiency, and focus on delivering more value-add services
>>>>>> Discover what IT Professionals Know. Rescue delivers
>>>>>> http://p.sf.net/sfu/logmein_12329d2d
>>>>>> _______________________________________________
>>>>>> Csound-devel mailing list
>>>>>> Csound-devel@lists.sourceforge.net
>>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> Saludos,
>>>>> Felipe Sateler
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
>>>>> Remotely access PCs and mobile devices and provide instant support
>>>>> Improve your efficiency, and focus on delivering more value-add services
>>>>> Discover what IT Professionals Know. Rescue delivers
>>>>> http://p.sf.net/sfu/logmein_12329d2d
>>>>> _______________________________________________
>>>>> Csound-devel mailing list
>>>>> Csound-devel@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>
>>>> ------------------------------------------------------------------------------
>>>> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
>>>> Remotely access PCs and mobile devices and provide instant support
>>>> Improve your efficiency, and focus on delivering more value-add services
>>>> Discover what IT Professionals Know. Rescue delivers
>>>> http://p.sf.net/sfu/logmein_12329d2d
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>>
>>>
>>> --
>>>
>>> Saludos,
>>> Felipe Sateler
>>>
>>> ------------------------------------------------------------------------------
>>> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
>>> Remotely access PCs and mobile devices and provide instant support
>>> Improve your efficiency, and focus on delivering more value-add services
>>> Discover what IT Professionals Know. Rescue delivers
>>> http://p.sf.net/sfu/logmein_12329d2d
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>> ------------------------------------------------------------------------------
>> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
>> Remotely access PCs and mobile devices and provide instant support
>> Improve your efficiency, and focus on delivering more value-add services
>> Discover what IT Professionals Know. Rescue delivers
>> http://p.sf.net/sfu/logmein_12329d2d
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
>
> --
>
> Saludos,
> Felipe Sateler
>
> ------------------------------------------------------------------------------
> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
> Remotely access PCs and mobile devices and provide instant support
> Improve your efficiency, and focus on delivering more value-add services
> Discover what IT Professionals Know. Rescue delivers
> http://p.sf.net/sfu/logmein_12329d2d
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Hi Steven,

On Fri, Dec 21, 2012 at 1:48 AM, Steven Yi  wrote:
> Hi Felipe,
>
> I think we can ignore it then if testing as testing using swig 2.0. As
> long as I have a workaround for a known issue, then it should be
> alright. There may be other projects which do not use CsoundMYFLTArray
> but do use Java, so this may be fine.

OK, lets leave it like that, then.

> I'd just like to make sure that
> this is being accounted for in future releases.  Can we make an
> explicit dependency on swig 2.0+ for future builds?

We could, but it is not really necessary: the debian package swig
(which is what csound build-deps on) pulls in version 2 of swig in
testing and unstable.

> Also, I noticed
> that using build-dep with debian stable did not bring in flex/bison.
> I assume this is because it is using a much older Csound before the
> new parser became the standard.  Do the testing builds explicitly add
> flex and bison, and if not, can we add that?

Indeed, stable's version is too old, and the current version in
testing does pull flex and bison, and enables the new parser.

--

Saludos,
Felipe Sateler

------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Okay, all sounds good.  Just out of curiosity, as I'm not a normal
Debian user, do most people use stable, or, should I ask, is it common
that users use testing or unstable?  Also, do you know how often
stable gets updated?  I assume we can expect it to be quite a while
until a newer csound can get pulled in?

Thanks!
steven

On Fri, Dec 21, 2012 at 9:19 AM, Felipe Sateler  wrote:
> Hi Steven,
>
> On Fri, Dec 21, 2012 at 1:48 AM, Steven Yi  wrote:
>> Hi Felipe,
>>
>> I think we can ignore it then if testing as testing using swig 2.0. As
>> long as I have a workaround for a known issue, then it should be
>> alright. There may be other projects which do not use CsoundMYFLTArray
>> but do use Java, so this may be fine.
>
> OK, lets leave it like that, then.
>
>> I'd just like to make sure that
>> this is being accounted for in future releases.  Can we make an
>> explicit dependency on swig 2.0+ for future builds?
>
> We could, but it is not really necessary: the debian package swig
> (which is what csound build-deps on) pulls in version 2 of swig in
> testing and unstable.
>
>> Also, I noticed
>> that using build-dep with debian stable did not bring in flex/bison.
>> I assume this is because it is using a much older Csound before the
>> new parser became the standard.  Do the testing builds explicitly add
>> flex and bison, and if not, can we add that?
>
> Indeed, stable's version is too old, and the current version in
> testing does pull flex and bison, and enables the new parser.
>
> --
>
> Saludos,
> Felipe Sateler
>
> ------------------------------------------------------------------------------
> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
> Remotely access PCs and mobile devices and provide instant support
> Improve your efficiency, and focus on delivering more value-add services
> Discover what IT Professionals Know. Rescue delivers
> http://p.sf.net/sfu/logmein_12329d2d
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

On Fri, Dec 21, 2012 at 11:26 AM, Steven Yi  wrote:
> Okay, all sounds good.  Just out of curiosity, as I'm not a normal
> Debian user, do most people use stable, or, should I ask, is it common
> that users use testing or unstable?

Interesting question. I don't think there is a way to really answer
this question, but fortunately I have a proxy. In the testing version
of csound, there is a csound-data package which is depended upon by
the csound package. Also, there is no such csound-data package in
stable.

The link below shows that about half of the people with the csound
package installed have csound-data installed, which should mean that
about half the people who use csound use stable and the other half
testing+unstable.


http://qa.debian.org/popcon-graph.php?packages=csound%2Ccsound-data&show_installed=on&want_legend=on&want_ticks=on&from_date=&to_date=&hlght_date=&date_fmt=%25Y-%25m&beenhere=1

> Also, do you know how often
> stable gets updated?  I assume we can expect it to be quite a while
> until a newer csound can get pulled in?

It depends on what you mean by updated. Debian stable has constant
security fixes. Also, every few months major bugs can get fixed by
point releases. However, new versions of packages are never accepted
in a current stable release.

Newer stable releases are created by taking a snapshot of testing at a
time when the release managers deem it fit. This is why updates to
testing are restricted in the months before a release. This in turn
means that csound will ship already outdated, because the freeze
started about 5 months ago, so 5.18 couldn't make it.

In a sense, a debian release is never updated with newer versions of
software, but it gets replaced by a newer debian release.


--

Saludos,
Felipe Sateler

------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Hi Felipe,

Thanks for explaining things.  I think it makes sense why people got
into Ubuntu as a more up to date version of Debian. :P  Thanks too for
checking into the newer builds pulling in flex/bison/newer swig!  I
think I'll add some information to the blue manual about this for the
future and can direct users to using pulling testing or unstable as a
work around.

Thanks!
steven

On Fri, Dec 21, 2012 at 10:00 AM, Felipe Sateler  wrote:
> On Fri, Dec 21, 2012 at 11:26 AM, Steven Yi  wrote:
>> Okay, all sounds good.  Just out of curiosity, as I'm not a normal
>> Debian user, do most people use stable, or, should I ask, is it common
>> that users use testing or unstable?
>
> Interesting question. I don't think there is a way to really answer
> this question, but fortunately I have a proxy. In the testing version
> of csound, there is a csound-data package which is depended upon by
> the csound package. Also, there is no such csound-data package in
> stable.
>
> The link below shows that about half of the people with the csound
> package installed have csound-data installed, which should mean that
> about half the people who use csound use stable and the other half
> testing+unstable.
>
>
> http://qa.debian.org/popcon-graph.php?packages=csound%2Ccsound-data&show_installed=on&want_legend=on&want_ticks=on&from_date=&to_date=&hlght_date=&date_fmt=%25Y-%25m&beenhere=1
>
>> Also, do you know how often
>> stable gets updated?  I assume we can expect it to be quite a while
>> until a newer csound can get pulled in?
>
> It depends on what you mean by updated. Debian stable has constant
> security fixes. Also, every few months major bugs can get fixed by
> point releases. However, new versions of packages are never accepted
> in a current stable release.
>
> Newer stable releases are created by taking a snapshot of testing at a
> time when the release managers deem it fit. This is why updates to
> testing are restricted in the months before a release. This in turn
> means that csound will ship already outdated, because the freeze
> started about 5 months ago, so 5.18 couldn't make it.
>
> In a sense, a debian release is never updated with newer versions of
> software, but it gets replaced by a newer debian release.
>
>
> --
>
> Saludos,
> Felipe Sateler
>
> ------------------------------------------------------------------------------
> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
> Remotely access PCs and mobile devices and provide instant support
> Improve your efficiency, and focus on delivering more value-add services
> Discover what IT Professionals Know. Rescue delivers
> http://p.sf.net/sfu/logmein_12329d2d
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Hi Felipe,

Thanks for looking into that. Yeah, I'm not sure how one might package
it for debian to be honest, or any Linux.  Build it is quite easy when
using Netbeans (just checkout, open in NB, then do build to run or
release). I'm largely alright with releasing as a zip, and sometime in
the coming months I'll be investigating using the autoupdate system of
the Netbeans platform, which should make keeping releases up to date
easy.

Thanks!
steven

On Sun, Dec 23, 2012 at 10:14 PM, Felipe Sateler  wrote:
> No problem.
>
> BTW, I once looked into packaging blue for debian, but there were way too
> many needed libraries that were not already in debian...
>
>
> On Sat, Dec 22, 2012 at 11:31 AM, Steven Yi  wrote:
>>
>> Hi Felipe,
>>
>> Thanks for explaining things.  I think it makes sense why people got
>> into Ubuntu as a more up to date version of Debian. :P  Thanks too for
>> checking into the newer builds pulling in flex/bison/newer swig!  I
>> think I'll add some information to the blue manual about this for the
>> future and can direct users to using pulling testing or unstable as a
>> work around.
>>
>> Thanks!
>> steven
>>
>> On Fri, Dec 21, 2012 at 10:00 AM, Felipe Sateler 
>> wrote:
>> > On Fri, Dec 21, 2012 at 11:26 AM, Steven Yi  wrote:
>> >> Okay, all sounds good.  Just out of curiosity, as I'm not a normal
>> >> Debian user, do most people use stable, or, should I ask, is it common
>> >> that users use testing or unstable?
>> >
>> > Interesting question. I don't think there is a way to really answer
>> > this question, but fortunately I have a proxy. In the testing version
>> > of csound, there is a csound-data package which is depended upon by
>> > the csound package. Also, there is no such csound-data package in
>> > stable.
>> >
>> > The link below shows that about half of the people with the csound
>> > package installed have csound-data installed, which should mean that
>> > about half the people who use csound use stable and the other half
>> > testing+unstable.
>> >
>> >
>> >
>> > http://qa.debian.org/popcon-graph.php?packages=csound%2Ccsound-data&show_installed=on&want_legend=on&want_ticks=on&from_date=&to_date=&hlght_date=&date_fmt=%25Y-%25m&beenhere=1
>> >
>> >> Also, do you know how often
>> >> stable gets updated?  I assume we can expect it to be quite a while
>> >> until a newer csound can get pulled in?
>> >
>> > It depends on what you mean by updated. Debian stable has constant
>> > security fixes. Also, every few months major bugs can get fixed by
>> > point releases. However, new versions of packages are never accepted
>> > in a current stable release.
>> >
>> > Newer stable releases are created by taking a snapshot of testing at a
>> > time when the release managers deem it fit. This is why updates to
>> > testing are restricted in the months before a release. This in turn
>> > means that csound will ship already outdated, because the freeze
>> > started about 5 months ago, so 5.18 couldn't make it.
>> >
>> > In a sense, a debian release is never updated with newer versions of
>> > software, but it gets replaced by a newer debian release.
>> >
>> >
>> > --
>> >
>> > Saludos,
>> > Felipe Sateler
>> >
>> >
>> > ------------------------------------------------------------------------------
>> > LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
>> > Remotely access PCs and mobile devices and provide instant support
>> > Improve your efficiency, and focus on delivering more value-add services
>> > Discover what IT Professionals Know. Rescue delivers
>> > http://p.sf.net/sfu/logmein_12329d2d
>> > _______________________________________________
>> > Csound-devel mailing list
>> > Csound-devel@lists.sourceforge.net
>> > https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>> ------------------------------------------------------------------------------
>> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
>> Remotely access PCs and mobile devices and provide instant support
>> Improve your efficiency, and focus on delivering more value-add services
>> Discover what IT Professionals Know. Rescue delivers
>> http://p.sf.net/sfu/logmein_12329d2d
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
>
>
> --
>
> Saludos,
> Felipe Sateler
>
> ------------------------------------------------------------------------------
> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
> Remotely access PCs and mobile devices and provide instant support
> Improve your efficiency, and focus on delivering more value-add services
> Discover what IT Professionals Know. Rescue delivers
> http://p.sf.net/sfu/logmein_12329d2d
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net