Hi, the problem was caused by two things: a) propel introduced a regression b) I released symfony 1.2.3 while the regression was not fixed in propel
the problem for us was that we have had an svn:external to the head version of propel, because we needed bugfixes from them which were not in any tagged version. But we forgot to restrict it to a specific version. As of today I fixed this, so propel updates will never backfire on symfony. Carstens symfony is working again because he is using svn version, which updated itself the moment as Propel fixed the problem. The pear package however contains a snapshot of the time it was created, so it of course contains the bug. I will release 1.2.4 shortly to fix this. Sorry for the inconvenience Fabian On Feb 3, 2009, at 2:11 PM, David Herrmann wrote: > > Hi Carsten, > > Carsten Schumann wrote: >> The issue is only relevant for users who use the svn version of >> symfony >> and have updated their svn between Friday and yesterday. It can be >> solved by updating symfony again. > > I definitely cannot confirm this. I'm using symfony through Pear and > just uninstalled and reinstalled 1.2.3 (pear install > symfony/symfony-1.2.3) and BasePeer.php includes the bug again. > > I suppose the Pear package has not been updated yet... > > Thanks for the reply though! > > David > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---
