http://people.canonical.com/~ubuntu-archive/pending-sru.html indicates there is allegedly a regression in svn. Last build is here: https://jenkins.qa.ubuntu.com/job/trusty-adt- subversion/lastBuild/ARCH=amd64,label=adt/ and indeed the build log shows a failure here: https://jenkins.qa.ubuntu.com/job/trusty-adt- subversion/lastBuild/ARCH=amd64,label=adt/artifact/results/log
cjwatson suggested on #ubuntu-devel: "This might just mean that the fix for https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1393832 needs to be cherry-picked as well, but I'm not sure. Perhaps rbasak can investigate." I tried replicating this with adt locally, but can't get it to fail the test either before OR after the change. I'd suggest that the test suite running would have failed both before and after this change. If this is indeed https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1393832 it will need someone to propose an SRU for it. My feeling is however that it is unrelated to this change. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1366174 Title: apache2 SEGV with multiple SSL sites To manage notifications about this bug go to: https://bugs.launchpad.net/apache2/+bug/1366174/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs