HUGE linux problems. any ideas?

[Atanor]

also could you tell me which scripts aren\'t chmoded +x please? so that I can fix that.

[Tullisti]

the bigest problem is not having GLIBC 2.3.2 on debian sarge. how the h**l did you get glibc2.3.2 under sarge? Yeah, i could open up a pinhole and get it from sid, but i\'d rather not at this point in time...

under the source package the following items are not chmod +x, and should be:

configure
mkinstalldirs
 psclient
 psserver
pssetup
py-compile

there\'s probably a few more, but my question about glibc remains :-)

[Atanor]

psserver ? how did you compile psserver? It not in the source package!!!

now about glibc... I compiled my own one and hacked a lot of things to make it work... But i did that a long time ago. when I tested binaries, I did forget about.

PS: do not try to do the same thing than me, it will break half of packages  

[Tullisti]

maybe then on the website you shouild change \"tested with debian (sarge) to:

\"tested with debian (sid)\"...

anyway, i can\'t get it going *snif*

[Sharaz]

\"tested with debian (sid)\"...

I wouldn\'t do that either, at least not until 3.2.2 is actually IN sid
Sid uses 3.2.1 at the moment, so we\'ll have to see when 3.2.2 comes out.

But that doesn\'t change the fact that the source package should simply work.

It all comes down to some strange problem with AWS. All other problems can be fixed, as described in some of the other posts in this thread. So I\'d suggest focussing on that problem, so all  of us anxious Debian users can finally enter PS