At Wed, 5 Mar 2003 07:03:57 -0800, Jeff Bailey wrote: > > On Wed, Mar 05, 2003 at 05:32:28PM +0900, GOTO Masanori wrote: > > > I don't know why this conflict was introduced. It might be related > > with __libc_fork bug (see #170385). However, I introduced the patch > > to fix __libc_fork issue, so I think this conflicts becomes > > meaningless nowadays. > > > Jeff Bailey might know about it in detail. Jeff, could I remove > > conflicts: php4 and wine? > > I don't remember off hand about the php4 conflict. I'd like to see us > maintain the wine conflict because we will probably need to get rid of > the patch eventually and the conflict will be accurate then. The php4 > thing might be the same way. I can look it up a bit later if noone else > comments.
"The versions of php4 in stable and testing (4:4.1.2-X) don't exhibit this problem" is brought by glibc's __libc_fork ad-hoc patch. Broken usage of __libc_fork in php4 and wine should be fixed in sarge completely. Well, removing the patch about __libc_fork is after releasing sarge, and I agree we have to conflict it at the last. So I change my mind that it should keep to conflict. Adam, is it OK? Regards, -- gotom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
