On Thu, Mar 03, 2005 at 06:38:33AM +1100, Adam Conrad wrote: > Theodore Ts'o said:
> > My system (currently running unstable, but it from the your description > > it sounds like it may be happening on sarge as well) has an > > apache2/mysql/php4 combination which blows up the moment you try to open > > a connection to a mysql database. > Are you sure you're note experiencing the bugs listed in #295998 and > #296694, which are fixed in 4.3.10-8 in unstable?... If not, then I guess > the transition has started with some packages and not others, and we need > to resolve that ASAP. It was stalled for a bit pending some license > issues, but Steve and I got that resolved upstream recently. > Steve, should we be going ahead with the push to make this transition > occur as soon as we can, now that the license mess is sorted? Yes, now that the license issue has been sorted out and we've finally gotten the PHP4 ABI change/security fixes into testing, I think it's time at last to get moving on the libmysqlclient transition. The timing is rotten for me to do anything here until probably the middle of next week; but if maintainers can use the weekend for uploading packages built against libmysqlclient12, I'll follow through with the rest of the original bug filing/NMUing plan on Wednesday. (My own maintainer uploads will most likely have to wait until then as well.) Please refer to <http://lists.debian.org/debian-devel/2005/01/msg01757.html> if you need a reminder of what needs to happen. The adjusted timeline will be as follows: - Maintainer uploads to transition to libmysqlclient12 will begin this weekend. This will most likely not include myodbc, but may include php4 if I rope Adam into it. - On Wednesday, Mar 9 I will file grave bus on any remaining packages from the original list that have not been relinked against libmysqlclient12. - On Saturday, Mar 12 I will begin NMUing any packages from that list which have not been fixed. Thanks, -- Steve Langasek postmodern programmer
signature.asc
Description: Digital signature
