Microsoft Teams App
Hi, I am looking for the developer who created the Microsoft Teams App. We have some changes coming up and I need some help from your team to keep Subversion up-to-date. Best Regards, Leana [cid:image001.jpg@01D4B4B3.2E338120]
Re: wc-queries-test test failure with -DSQLITE_ENABLE_STMT_SCANSTATUS
On 2019/01/22 21:18:54, Thomas Deutschmann wrote: > Hi,> > > in Gentoo Linux, wc-queries-test test is failing (verified> > against v1.9.7-1.11.1:> > > > START: wc-queries-test> > > DBG: Using Sqlite 3.25.3> > > PASS: wc-queries-test 1: sqlite up-to-date> > > PASS: wc-queries-test 2: queries are parsable> > > DBG: Unhandled sqlite operation 'CORRELATED' in explanation> > > DBG: Unhandled sqlite operation 'CORRELATED' in explanation> > > DBG: Unhandled sqlite operation 'CORRELATED' in explanation> > > DBG: Unhandled sqlite operation 'CORRELATED' in explanation> > > DBG: Unhandled sqlite operation 'CORRELATED' in explanation> > > DBG: Unhandled sqlite operation 'CORRELATED' in explanation> > > DBG: Unhandled sqlite operation 'CORRELATED' in explanation> > > DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation> > > DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation> > > DBG: Unhandled sqlite operation 'MERGE' in explanation> > > DBG: Unhandled sqlite operation 'LEFT' in explanation> > > DBG: Unhandled sqlite operation 'RIGHT' in explanation> > > DBG: Unhandled sqlite operation 'CORRELATED' in explanation> > > DBG: Unhandled sqlite operation 'CORRELATED' in explanation> > > DBG: Expected 'SUBQUERIES', got 'QUERY' in 'COMPOUND QUERY'> > > DBG: Unhandled sqlite operation 'LEFT-MOST' in explanation> > > DBG: Unhandled sqlite operation 'UNION' in explanation> > > DBG: Unhandled sqlite operation 'CORRELATED' in explanation> > > DBG: Unhandled sqlite operation 'SCALAR' in explanation> > > DBG: Unhandled sqlite operation 'SCALAR' in explanation> > > DBG: Unhandled sqlite operation 'SCALAR' in explanation> > > DBG: Unhandled sqlite operation 'SCALAR' in explanation> > > DBG: Expected 'SUBQUERIES', got 'QUERY' in 'COMPOUND QUERY'> > > DBG: Unhandled sqlite operation 'LEFT-MOST' in explanation> > > DBG: Unhandled sqlite operation 'UNION' in explanation> > > DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation> > > DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation> > > DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation> > > DBG: Unhandled sqlite operation 'SCALAR' in explanation> > > DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation> > > DBG: Unhandled sqlite operation 'CORRELATED' in explanation> > > DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation> > > DBG: Unhandled sqlite operation 'CORRELATED' in explanation> > > DBG: Unhandled sqlite operation 'CORRELATED' in explanation> > > DBG: Unhandled sqlite operation 'CORRELATED' in explanation> > > DBG: Unhandled sqlite operation 'CORRELATED' in explanation> > > DBG: Unhandled sqlite operation 'CORRELATED' in explanation> > > DBG: Unhandled sqlite operation 'CORRELATED' in explanation> > > DBG: Unhandled sqlite operation 'CORRELATED' in explanation> > > DBG: Unhandled sqlite operation 'CORRELATED' in explanation> > > DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation> > > DBG: Unhandled sqlite operation 'SCALAR' in explanation> > > DBG: Unhandled sqlite operation 'SCALAR' in explanation> > > DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation> > > DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation> > > DBG: Unhandled sqlite operation 'SCALAR' in explanation> > > DBG: Unhandled sqlite operation 'CORRELATED' in explanation> > > DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation> > > DBG: Unhandled sqlite operation 'CORRELATED' in explanation> > > DBG: Unhandled sqlite operation 'CORRELATED' in explanation> > > DBG: Unhandled sqlite operation 'CORRELATED' in explanation> > > DBG: Unhandled sqlite operation 'CORRELATED' in explanation> > > DBG: Unhandled sqlite operation 'CORRELATED' in explanation> > > DBG: Unhandled sqlite operation 'CORRELATED' in explanation> > > DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation> > > DBG: Expected 'SUBQUERIES', got 'QUERY' in 'COMPOUND QUERY'> > > DBG: Unhandled sqlite operation 'LEFT-MOST' in explanation> > > DBG: Unhandled sqlite operation 'CORRELATED' in explanation> > > DBG: Unhandled sqlite operation 'UNION' in explanation> > > DBG: Unhandled sqlite operation 'SCALAR' in explanation> > > DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation> > > DBG: Unhandled sqlite operation 'CORRELATED' in explanation> > > DBG: Unhandled sqlite operation 'MULTI-INDEX' in explanation> > > DBG: Unhandled sqlite operation 'CORRELATED' in explanation> > > DBG: Unhandled sqlite operation 'SCALAR' in explanation> > > DBG: Unhandled sqlite operation 'MERGE' in explanation> > > DBG: Unhandled sqlite operation 'LEFT' in explanation> > > DBG: Unhandled sqlite operation 'RIGHT' in explanation> > > DBG: Unhandled sqlite operation 'SCALAR' in explanation> > > DBG: Unhandled sqlite operation 'MERGE' in explanation> > > DBG: Unhandled sqlite operation 'LEFT' in explanation> > > DBG: Unhandled sqlite operation 'RIGHT' in explanation> > > DBG: Unhandled sqlit
Re: [CVE-2018-11803] Apache Subversion Denial of Service Vulnerability
On 2019/01/23 03:55:14, Troy Curtis wrote: > This is a security notification for Apache Subversion HTTP Servers:> > > CVE-2018-11803> > Severity: Medium> > Affected Versions: Apache Subversion 1.11.0, 1.10.0 to 1.10.3> > > Subversion's mod_dav_svn Apache HTTPD module versions 1.11.0 and 1.10.0 > > to 1.10.3 will crash after dereferencing an uninitialized pointer if the > > client omits the root path in a recursive directory listing operation. > > This issue can be triggered by any client on Subversion repositories > > configured for anonymous read access. If read access requires > > authentication, a denial of service attack can only be performed by an > > authenticated user.> > > The Subversion releases 1.10.4 and 1.11.1 contain the fixes for this > > vulnerability and are available immediately at:> > > https://dist.apache.org/repos/dist/release/subversion/?p=32084> > > Additional details, including patches for 1.10.3 and 1.11.0 can be found at:> > > https://subversion.apache.org/security/CVE-2018-11803-advisory.txt> > > We encourage users of Subversion to upgrade to the latest appropriate > > version as soon as reasonable.> > > Thanks,> > - The Subversion Team> > Sent from my iPhone
Tree conflict when an update attempts to remove a directory with unversioned files
Hi all, When we upgraded from Subversion 1.8.17 to Subversion 1.9.7 we noticed a change in behaviour of svn update. This happens when the update pulls in a change that deletes a directory while this directory contains one or more unversioned files in your local working copy. What used to happen with svn 1.8 was the following: - The versioned files inside the removed directory are removed - Any unversioned files remain present What now happens with svn 1.9 is: - A tree conflict is signalled with the following details: > local dir edit, incoming dir delete or move upon update This subsequently requires action by the developer to resolve the conflict before he can use the working copy again. Furthermore, when resolved incorrectly, the deleted directory may (unintentially) be added again. In our archive we have the build generate files throughout the working copy (obj folders, files generated from template, output folders per sub-codebase, etc). We also regularly delete directories as part of refactoring, so the tree conflicts occur quite frequently and are considered an inconvenience by our developers. So we would like to know, is the new behaviour intentional or is it an accidental side-effect of another change? We did not see this change documented in the release notes. Kind regards, Erwin