ETA Slack 13.2

volkerdi · 12-06-2010, 03:26 PM

There's nothing wrong with libxml2, as I explained previously.

You know, we still haven't used the 13.37 version number. ;-)

hitest · 12-06-2010, 03:29 PM

Quote:

Originally Posted by volkerdi

There's nothing wrong with libxml2, as I explained previously.

You know, we still haven't used the 13.37 version number. ;-)

That would be awesome!

mlangdn · 12-06-2010, 03:30 PM

You could always fore go a number and give it a name instead.

hitest · 12-06-2010, 03:34 PM

Quote:

Originally Posted by mlangdn

You could always fore go a number and give it a name instead.

Ye Gods......not that!!!

brianL · 12-06-2010, 04:13 PM

Quote:

Originally Posted by volkerdi

You know, we still haven't used the 13.37 version number. ;-)

I wish I'd thought of that.

eumyang · 12-06-2010, 04:19 PM

LOL, the OP asked a similar question not long before 13.1 was released:
http://www.linuxquestions.org/questi...13-1-a-802054/
... and he lists "Slackware 12.2" as his distribution in his profile.

2handband · 12-06-2010, 04:20 PM

Quote:

Originally Posted by volkerdi

There's nothing wrong with libxml2, as I explained previously.

You know, we still haven't used the 13.37 version number. ;-)

oops, did i get 'em mixed up again?

sycamorex · 12-06-2010, 04:21 PM

Quote:

Originally Posted by brianL

I wish I'd thought of that.

Who would have thought of 13.37?! Ok, 13.32 or 13.54 are obvious choices, but 13.37?!!!
I haven't been using Slackware long enough to come up with that

2handband · 12-06-2010, 04:25 PM

Quote:

Originally Posted by rworkman

What's wrong with libxml?

I don't pretend to understand it (and obviously I don't, as was just pointed out)... but there's something screwy in the interaction between zlibs and libxml2. I don't know what else it does, but it makes Ardour so unstable as to be useless.

rworkman · 12-06-2010, 05:09 PM

An older version of libxml2 was using the zlib API incorrectly, and that caused quite a few things to be "screwy," but that should be fixed now.

Does ardour statically link libxml2, and if so, was it built before -current was bumped to libxml2-2.7.7?

2handband · 12-06-2010, 05:31 PM

Quote:

Originally Posted by rworkman

An older version of libxml2 was using the zlib API incorrectly, and that caused quite a few things to be "screwy," but that should be fixed now.

Does ardour statically link libxml2, and if so, was it built before -current was bumped to libxml2-2.7.7?

Are you suggesting I rebuild Ardour? I can do that...

volkerdi · 12-06-2010, 06:03 PM

There is a newer libxml2, and while it doesn't claim to address any zlib issues it probably wouldn't hurt to bump that again.

2handband · 12-06-2010, 06:18 PM

Quote:

Originally Posted by volkerdi

There is a newer libxml2, and while it doesn't claim to address any zlib issues it probably wouldn't hurt to bump that again.

I'll let you know what happens after I rebuild Ardour. I REALLY want to get Ardour working on the desktop machine; it's got a lot more horespower than either of the laptops.

brianL · 12-07-2010, 07:01 AM

Quote:

Originally Posted by mlangdn

You could always fore go a number and give it a name instead.

No no no no no no no no no no no no no no no no no no no no!!!
No alliterative animals!
No Pixar personalities!

sycamorex · 12-07-2010, 07:04 AM

Quote:

Originally Posted by brianL

No no no no no no no no no no no no no no no no no no no no!!!
No alliterative animals!
No Pixar personalities!

Even if it was: Slackware Brave Brian? LOL

I agree number versions are more interesting.