On Monday, August 12, 2013 11:53 CEST, Landry Breuil <lan...@rhaalovely.net> wrote: > On Mon, Aug 12, 2013 at 11:32:46AM +0200, Sebastian Reitenbach wrote: > > Hi, > > > > long story: > > Jean-Gérard Pailloncy reported to me that www/sogo package is broken on > > 5.4, or with the current snapshots. > > On startup, there are unresolved symbols seen. I checked and found that the > > security fix done after ports lock > > did not caused it, the version before without the patch also has same > > problem. But that was in the ports tree for > > a long time, when updating to the 2.0.5 version I'm sure the problem was > > not there, and also giovanni did not > > saw it, otherwise he would have told me. Something else in between must > > have caused it, and the problem went > > unnoticed. I recognized it when I sent the upgrade to 2.0.6 including a fix > > for it, but I thought its a problem only on > > the new version. That update was sent too late before the ports lock to get > > in :( > > > > short story: > > www/sope is unusable on 5.4. The fix below that should go in 5.4 branch. > > Works for me, initial reporter, and also works and OK giovanni@ > > Is it OK to apply it 5.4 branch? > > I think the 5.4 branch is only open to commits once the actual release > has been made... but i might be mistaken.
I was unsure about that, therefore asking before I get slapped because of doing something stupid ;) If nobody tells me otherwise, I'll keep that patch and ask again in November, and for -current looking into getting the 2.0.7 update patch ready. thanks, Sebastian > > Landry >
