Re: Full text search
We have hound setup and it is nice but it only indexes the HEAD commit and so it isn’t useful for searching history. > On Nov 29, 2021, at 5:30 PM, Mark Phippard wrote: > > On Mon, Nov 29, 2021 at 10:19 AM Luke Mauldin wrote: >> >> I saw the —search argument but that only searches commit metadata. I would >> like to do a search of the changed text of the files in the commit. > > Ah, I missed that in your original post. I would suggest using a code > search tool like OpenGrok or Hound: > > https://github.com/oracle/opengrok/wiki/How-to-setup-OpenGrok > https://github.com/hound-search/hound > > Mark
Re: Full text search
On Mon, Nov 29, 2021 at 10:19 AM Luke Mauldin wrote: > > I saw the —search argument but that only searches commit metadata. I would > like to do a search of the changed text of the files in the commit. Ah, I missed that in your original post. I would suggest using a code search tool like OpenGrok or Hound: https://github.com/oracle/opengrok/wiki/How-to-setup-OpenGrok https://github.com/hound-search/hound Mark
Re: Full text search
On Mon, Nov 29, 2021 at 10:10 AM Luke Mauldin wrote: > Is there a recommended way to do a full text search of commits that > include changed text. For example if I wanted “svn log” to show me all of > that commits that have an added or deleted line that contains “foo”, is > that possible? Git has similar functionality in “git log -S foo” > Using “svn diff -r:HEAD | grep foo” gets me close but that just gives me > the lines that changed and not the commit that they changed. 'svn log' has a --diff option. Together with a revision range, that will output commit log together with the changes in that commit (though be aware if server access is slow and you request a large range it could be slow). Perhaps 'svn blame' will be helpful in addition or instead? Nathan
Re: Full text search
I think he wants to search for file content, not for a commit message. So for example "Was our supersecret password ever commited to code anywhere?" I do not think svn has a build in function to do that easily/fast. You can write a script that counts up, gets the diff from svn for that revision and run grep or awk on it. Might take ages. There are (paid) thirdparty tools whicht can index your repository and provide fast search (fisheye for example) Building an index also can take ages. Best regards, Thorsten Am 29/11/2021 um 16:10 schrieb Luke Mauldin: Is there a recommended way to do a full text search of commits that include changed text. For example if I wanted “svn log” to show me all of that commits that have an added or deleted line that contains “foo”, is that possible? Git has similar functionality in “git log -S foo” Using “svn diff -r:HEAD | grep foo” gets me close but that just gives me the lines that changed and not the commit that they changed.
Re: Full text search
I saw the —search argument but that only searches commit metadata. I would like to do a search of the changed text of the files in the commit. > On Nov 29, 2021, at 9:14 AM, Mark Phippard wrote: > > On Mon, Nov 29, 2021 at 10:10 AM Luke Mauldin wrote: >> >> Is there a recommended way to do a full text search of commits that include >> changed text. For example if I wanted “svn log” to show me all of that >> commits that have an added or deleted line that contains “foo”, is that >> possible? Git has similar functionality in “git log -S foo” >> Using “svn diff -r:HEAD | grep foo” gets me close but that just gives me the >> lines that changed and not the commit that they changed. > > With newer versions of SVN, the log command has a --search argument: > > https://svnbook.red-bean.com/nightly/en/svn.ref.svn.html#svn.ref.svn.sw.search > https://subversion.apache.org/docs/release-notes/1.8.html#svn-log-search > > Mark
Re: Subversion 1.14.1 build problem
Den tis 2 nov. 2021 kl 09:33 skrev Daniel Sahlberg < daniel.l.sahlb...@gmail.com>: > Den mån 1 nov. 2021 kl 09:32 skrev Gretton, Liam < > liam.gret...@leicester.ac.uk>: > > > > I'm rebuilding our Subversion server, getting it up to date after a fair > period of neglect. > > > > > > > > I'm finding that 1.41.1 has a problem somewhere in its SQLite code and > fails at the make stage. 1.10.7 succeeds with exactly the same build > process and dependencies. > > > > > > > > I'm using CentOS 7, but with Apache 2.4.8, APR 1.7.0, APR-util 1.6.1 and > SQLite 3.36.0. > > > > > > > > cd subversion-1.14.1 > > > > unzip ../sqlite-amalgamation-336.zip > > > > mv sqlite-amalgamation-336.zip sqlite-amalgamation > > > > > > > > ./configure --prefix=/local/software/subversion-1.14.1 \ > > > > --with-lz4=internal \ > > > > --with-utf8proc=internal \ > > > > --with-apxs=/local/software/httpd/bin/apxs \ > > > > --with-apr=/local/software/bin \ > > > > --with-apr-util=/local/software/bin > > > > make > > > > > > > > … > > > > > > > > In file included from subversion/libsvn_subr/sqlite3wrapper.c:63:0: > > > > > /home/liam/downloads/subversion-1.14.1/sqlite-amalgamation/sqlite3.c:38012:12: > warning: ‘unixFcntlExternalReader’ used but never defined [enabled by > default] > > > > static int unixFcntlExternalReader(unixFile*, int*); > > > > > > > > … > > > > > > > > .libs/sqlite3wrapper.o: In function `unixFileControl': > > > > > /home/liam/downloads/subversion-1.14.1/sqlite-amalgamation/sqlite3.c:38131: > undefined reference to `unixFcntlExternalReader' > > > > /usr/bin/ld: .libs/sqlite3wrapper.o: relocation R_X86_64_PC32 against > undefined symbol `unixFcntlExternalReader' can not be used when making a > shared object; recompile with -fPIC > > > > /usr/bin/ld: final link failed: Bad value > > > > collect2: error: ld returned 1 exit status > > > > make: *** [subversion/libsvn_subr/libsvn_subr-1.la] Error 1 > > > > > > > > Any idea what I can do to get past this? > > Hi! > > I reproduce this behaviour. > > As far as I can tell this is a bug in SQLite. The offending function > was added 2021-04-02 [1] and it seems to be hidden by #ifdef > SQLITE_OMIT_WAL. There is a reference to the same error in the SQLite > forums [2] with a suggestion to leave out SQLITE_OMIT_WAL on > compilation. > > It seems to be possible to restore the old behaviour by reverting our > r1865523 (which is defining SQLITE_OMIT_WAL, triggering the build > failure). I'm adding Evgeny Kotkov, author of r1865523, for a second > pair of eyes, but I don't think that we are doing anything wrong. > > I think it should also be possible to use an older version of SQLite > (released before 2021-04-02). > [1] https://sqlite.org/src/info/e16da5af822ef31d > [2] https://sqlite.org/forum/info/f4640ddef932093c SQLite 3.37.0 was relased today. According to a post in the SQLite forums [1], a fix was committed 2021-11-02. When checking the source of 3.37.0 it seems to be included but I'm out of time to verify. Maybe you can try a new build? Kind regards, Daniel [1] https://sqlite.org/forum/forumpost/8066af6dcd79e78490694a324ed655fe6b6588bf5f02db09becb60ea233e5b1a
Re: Full text search
On Mon, Nov 29, 2021 at 10:10 AM Luke Mauldin wrote: > > Is there a recommended way to do a full text search of commits that include > changed text. For example if I wanted “svn log” to show me all of that > commits that have an added or deleted line that contains “foo”, is that > possible? Git has similar functionality in “git log -S foo” > Using “svn diff -r:HEAD | grep foo” gets me close but that just gives me the > lines that changed and not the commit that they changed. With newer versions of SVN, the log command has a --search argument: https://svnbook.red-bean.com/nightly/en/svn.ref.svn.html#svn.ref.svn.sw.search https://subversion.apache.org/docs/release-notes/1.8.html#svn-log-search Mark
Re: Full text search
Den mån 29 nov. 2021 kl 16:10 skrev Luke Mauldin : > Is there a recommended way to do a full text search of commits that > include changed text. For example if I wanted “svn log” to show me all of > that commits that have an added or deleted line that contains “foo”, is > that possible? Git has similar functionality in “git log -S foo” > Using “svn diff -r:HEAD | grep foo” gets me close but that just gives me > the lines that changed and not the commit that they changed. I'm not familiar with git, but I guess you are looking for a search in the commit message. Have you tried svn log --search? Kind regards, Daniel
Full text search
Is there a recommended way to do a full text search of commits that include changed text. For example if I wanted “svn log” to show me all of that commits that have an added or deleted line that contains “foo”, is that possible? Git has similar functionality in “git log -S foo” Using “svn diff -r:HEAD | grep foo” gets me close but that just gives me the lines that changed and not the commit that they changed.
