Re: Sixth Release Candidate Up

Sascha Schumann wrote: > On Thu, 14 Dec 2000, Ron Chmara wrote: > > Derick Rethans wrote: > > > there is some bug in the libmcrypt extension. I'll check it out > > > tonight. I don't think it's a showstopper, but it caused > > > phpinfo(); to crash for me > > Er.. phpinfo() is a pretty standard user-space tool for their > > own debugging. I would say not having this function running would > > be a Horrendously Bad Thing. Expecially because it's one of the *very > > first things* most tutorials recommend doing to confirm an install.... > > ....and the support q's from the newbies are always the most difficult > > to work with (IMNSHO, of course). > Well, if you feel so strongly about it, I'd suggest that you > provide a fix to us for consideration. Well, the fastest "fix" would be to rollback any recent changes. :-) Looking at it though, it seems odd that this wouldn't have been noticed sooner (the 4.0.4 mcrypt tree hasn't been touched for 3 weeks). > FYI, I installed the latest libmcrypt and it worked out of > the box. Good. That means it's been somewhat isolated. Do we generally assume that for new releases, it's acceptable to request our users update? (I'm not being sarcastic, updating to current versions is something I usually do as part of every compile, and I havn't seen this issue discussed on php-dev). Can the fix be as simple as adding a requirement for the latest libmcrypt? Derick, does the latest libmcrypt work for you? (I'm also trying to see if I can replicate this here). -Ronabop -- Personal: ron@opus1.com, 520-326-6109, http://www.opus1.com/ron/ Work: rchmara@pnsinc.com, 520-546-8993, http://www.pnsinc.com/ The opinions expressed in this email are not neccesarrily those of myself, my employers, or any of the other little voices in my head.