Re: How do I enable storing of plaintext passwords?
> On 15 Dec 2019, at 15:29, Branko Čibej wrote: > > On 15.12.2019 14:46, Barry Scott wrote: >> I'm doing some testing and want to test with plaintext passwords. >> >> It seems that storing plaintext passwords can be compiled out. Is that why I >> cannot configure it back on? > > > https://subversion.apache.org/docs/release-notes/1.12.html#client-server-improvements Aha, that explains why it works on some systems with older svn. Been working on Centos 7 with svn 1.7 for some tests. > If you want to use plaintext passwords on disk, you'll have to build > Subversion from source and explicitly enable that feature. What had me confused for a while is that if the svn.simple/123... file was written by an earlier svn then 1.12 with a plaintext password that password is used with the newer svn versions. Barry > > -- Brane >
Announce: PySVN 1.7.5 - binary kits built against SVN 1.6.15
PySVN home page: http://pysvn.tigris.org/ The kits have been built against SVN 1.6.15 release for python 2.6, 2.7 and 3.1. This release include: * bug fixes for reported issues * On Mac OS X it is now possible to install pysvn kits for multiple versions of python * New binary kit for Apple's Python 2.6 on Mac OS X 10.6, 32 and 64 bit * New binary kit for Python.org's Python 2.7 on Mac OS X 10.5 and 10.6, 32 and 64 bit Features of PySVN: * Natural python interface to Subversion * Supports Subversion 1.2.0 thru 1.6.15 * Supports Python 2.2, 2.3, 2.4, 2.5, 2.6, 2.7 and 3.1 * Full reference documentation * Working example of svn command line written in python * Binary kits for: - Windows - Mac OS X 10.5 Intel for Python.Org python - Mac OS X 10.6 Intel for both Apple Python and Python.Org python * Source kit tested: - Linux Fedora 13 - Windows XP Visual C++ 2008 Express edition - Mac OS X 10.6 Snow Leopard Download page: http://pysvn.tigris.org/project_downloads.html Source kits: http://pysvn.tigris.org/servlets/ProjectDocumentList?folderID=1762 http://pysvn.barrys-emacs.org/ (recommended for distribution packagers) Windows Binary Kits: http://pysvn.tigris.org/servlets/ProjectDocumentList?folderID=1768 Mac OS X Binary Kits: http://pysvn.tigris.org/servlets/ProjectDocumentList?folderID=2860 Barry
Announce: PySVN WorkBench 1.6.5 - built against SVN 1.6.15
PySVN home page: http://pysvn.tigris.org/ PySVN Workbench documentation http://pysvn.tigris.org/docs/WorkBench.html The kits have been built against SVN 1.6.15 release. Features of this release: * Bug fixes for reported issues Features of PySVN WorkBench: * Easy to use working copy management * Same Look and Feel across Windows, Mac OS X and Unix * Integration of custom command shell, diff tools and editor * Bookmark working copy directories for fast navigation in large projects * Instant filtering of files lists to allow you to find the file you are looking for quickly. * OS File Open on Windows, Mac OS X and Unix * Binary kits for: - Windows - Mac OS X 10.5 and later Intel Download page: http://pysvn.tigris.org/project_downloads.html Source kits: http://pysvn.tigris.org/servlets/ProjectDocumentList?folderID=1763 http://pysvn.barrys-emacs.org/ (recommended for distribution packagers) Windows Binary Kits: http://pysvn.tigris.org/servlets/ProjectDocumentList?folderID=1765 Mac OS X Binary Kits: http://pysvn.tigris.org/servlets/ProjectDocumentList?folderID=2867 Barry
Announce: PySVN 1.7.6 - binary kits built against SVN 1.7.3 and 1.6.17
PySVN home page: http://pysvn.tigris.org/ The kits have been built against SVN 1.7.3 and SVN 1.6.17release for python 2.6, 2.7 and 3.2. This release include: * bug fixes for reported issues * Support SVN 1.7 * Support Python 3.2 Features of PySVN: * Natural python interface to Subversion * Supports Subversion 1.2.0 thru 1.7.3 * Supports Python 2.2, 2.3, 2.4, 2.5, 2.6, 2.7, 3.1 and 3.2 * Full reference documentation * Working example of svn command line written in python * Binary kits for: - Windows - Mac OS X 10.6 Intel for both Apple Python and Python.Org python * Source kit tested: - Linux Fedora 16 - Windows 7, Microsoft Visual Studio 2008 x86 tools - Mac OS X 10.7.3 Lion Download page: http://pysvn.tigris.org/project_downloads.html Source kits: http://pysvn.tigris.org/servlets/ProjectDocumentList?folderID=1762 http://pysvn.barrys-emacs.org/ (recommended for distribution packagers) Windows Binary Kits: http://pysvn.tigris.org/servlets/ProjectDocumentList?folderID=1768 Mac OS X Binary Kits: http://pysvn.tigris.org/servlets/ProjectDocumentList?folderID=2860 Barry -- http://pysvn.tigris.org/ds/viewMessage.do?dsForumId=1331&dsMessageId=2930778 To unsubscribe from this discussion, e-mail: [dev-unsubscr...@pysvn.tigris.org].
Announce: PySVN WorkBench 1.6.6 - built against SVN 1.7.3 and SVN
PySVN home page: http://pysvn.tigris.org/ PySVN Workbench documentation http://pysvn.tigris.org/docs/WorkBench.html The kits have been built against SVN 1.7.3 and 1.6.17 release. Features of this release: * Support Subversion 1.7 * Add Upgrade command to allow 1.6 working copies to be upgrades by WorkBench to 1.7 format Features of PySVN WorkBench: * Easy to use working copy management * Same Look and Feel across Windows, Mac OS X and Unix * Integration of custom command shell, diff tools and editor * Bookmark working copy directories for fast navigation in large projects * Instant filtering of files lists to allow you to find the file you are looking for quickly. * OS File Open on Windows, Mac OS X and Unix * Binary kits for: - Windows (Tested on Window 7) - Mac OS X 10.6 and later Intel (Tested on Mac OS X 10.7.3 Lion) Download page: http://pysvn.tigris.org/project_downloads.html Source kits: http://pysvn.tigris.org/servlets/ProjectDocumentList?folderID=1763 http://pysvn.barrys-emacs.org/ (recommended for distribution packagers) Windows Binary Kits: http://pysvn.tigris.org/servlets/ProjectDocumentList?folderID=1765 Mac OS X Binary Kits: http://pysvn.tigris.org/servlets/ProjectDocumentList?folderID=2867 Barry -- http://pysvn.tigris.org/ds/viewMessage.do?dsForumId=1331&dsMessageId=2930781 To unsubscribe from this discussion, e-mail: [dev-unsubscr...@pysvn.tigris.org].
PySVN 1.7.7 - binary kits built against SVN 1.7.8
PySVN home page: http://pysvn.tigris.org/ The kits have been built against SVN 1.7.8 release for python 2.6, 2.7, 3.2 and 3.3. This release include: * bug fixes for reported issues * Support SVN 1.7.8 * New Mac installer Features of PySVN: * Natural python interface to Subversion * Supports Subversion 1.2.0 thru 1.7.8 * Supports Python 2.5, 2.6, 2.7, 3.2 and 3.3 * Full reference documentation * Working example of svn command line written in python * Binary kits for: - Windows - Mac OS X 10.7 and 10.8 Intel for both Apple Python and Python.Org python * Source kit tested: - Linux Fedora 17 - Windows 7, Microsoft Visual Studio 2008 x86 tools - Mac OS X 10.8 Lion Download page: http://pysvn.tigris.org/project_downloads.html Source kits: http://pysvn.tigris.org/servlets/ProjectDocumentList?folderID=1762 http://pysvn.barrys-emacs.org/ (recommended for distribution packagers) Windows Binary Kits: http://pysvn.tigris.org/servlets/ProjectDocumentList?folderID=1768 Mac OS X Binary Kits: http://pysvn.tigris.org/servlets/ProjectDocumentList?folderID=2860 Barry
PySVN WorkBench 1.6.7 - built against SVN 1.7.8
PySVN home page: http://pysvn.tigris.org/ PySVN Workbench documentation http://pysvn.tigris.org/docs/WorkBench.html The kits have been built against SVN 1.7.8 release. Features of this release: * Support Subversion 1.7.8 Features of PySVN WorkBench: * Easy to use working copy management * Same Look and Feel across Windows, Mac OS X and Unix * Integration of custom command shell, diff tools and editor * Bookmark working copy directories for fast navigation in large projects * Instant filtering of files lists to allow you to find the file you are looking for quickly. * OS File Open on Windows, Mac OS X and Unix * Binary kits for: - Windows (Tested on Window 7) - Mac OS X 10.7 and later Intel (Tested on Mac OS X 10.8 Lion) Download page: http://pysvn.tigris.org/project_downloads.html Source kits: http://pysvn.tigris.org/servlets/ProjectDocumentList?folderID=1763 http://pysvn.barrys-emacs.org/ (recommended for distribution packagers) Windows Binary Kits: http://pysvn.tigris.org/servlets/ProjectDocumentList?folderID=1765 Mac OS X Binary Kits: http://pysvn.tigris.org/servlets/ProjectDocumentList?folderID=2867 Barry
Re: Tortoise SVn LOG issue
Note: It is not an error in svn to have no author or date in an svn log entry. Do you see that same data using the svn command line? If so its not a TSVN issue. Barry On 15 Jan 2013, at 08:42, Ajay Pawar wrote: > Thanks Thorsten fro your prompt reply but the as I am the owner of the server > I have full access to all the repository on the server. > > I checked SHOW LOG with 1.7.10 version of tortoise SVN but still found the > same UI. > > Regrads, > Ajay Pawar > > -Original Message- > From: Thorsten Schöning [mailto:tschoen...@am-soft.de] > Sent: Tuesday, January 15, 2013 1:33 PM > To: users@subversion.apache.org > Subject: Re: Tortoise SVn LOG issue > > Guten Tag Ajay Pawar, > am Dienstag, 15. Januar 2013 um 08:42 schrieben Sie: > >> Please look into SVN issue. > > Next time please textually describe your problem and don't just send > screenshots as those can't be indexed and it's your interest to make > it as easy as possible for others to help you. Your problem isn't even > hard to describe, but there's additional info missing which could help > resolve your problem: How is your repo layout and in which directory > did you open the log viewer? Are there any read restrictions for your > user in some directories of the repo? Normally missing log entries > like yours mean exactly that, missing read access to some paths. > >> Tortoise SVN Version Information : > > TortoiseSVN has it's own mailing list: > > http://tortoisesvn.net/community.html > >> TortoiseSVN 1.6.10, Build 19898 - 32 Bit , 2010/07/16 15:46:08 > > Any reason why you don't use a current stable version? > > Mit freundlichen Grüßen, > > Thorsten Schöning > > -- > Thorsten Schöning E-Mail:thorsten.schoen...@am-soft.de > AM-SoFT IT-Systeme http://www.AM-SoFT.de/ > > Telefon...05151- 9468- 55 > Fax...05151- 9468- 88 > Mobil..0178-8 9468- 04 > > AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln > AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow > >
Tree conflict - svn status cannot show?
I starting to see failures to commit because of tree conflicts. svn status does not seem to show tree conflicts. Did I miss the way to find the tree conflicts? At the moment I'm having to guess which folder is in conflict. Barry
Re: Tree conflict - svn status cannot show?
On 25 Feb 2010, at 23:18, Stefan Sperling wrote: > On Thu, Feb 25, 2010 at 10:30:18PM +0000, Barry Scott wrote: >> I starting to see failures to commit because of tree conflicts. >> >> svn status does not seem to show tree conflicts. > > It sure does. See examples here: > http://svnbook.red-bean.com/nightly/en/svn.tour.treeconflicts.html We notice tree conflict after folder moves. Not seen one for a file move yet. This example only about file issues not folder issues. > >> Did I miss the way to find the tree conflicts? > > Not sure. What commands are you running and what output are you seeing? svn st -q and the output is blank. (I ran svn st -q after pysvn workbench failed to show anything problems.) I guess I'm going to have to create a test script for this given you expect this to work. Barry
Re: Tree conflict - svn status cannot show?
On 26 Feb 2010, at 13:01, Stefan Sperling wrote: > On Fri, Feb 26, 2010 at 12:05:52AM +0000, Barry Scott wrote: > j >> On 25 Feb 2010, at 23:18, Stefan Sperling wrote: >> >>> On Thu, Feb 25, 2010 at 10:30:18PM +, Barry Scott wrote: >>>> I starting to see failures to commit because of tree conflicts. >>>> >>>> svn status does not seem to show tree conflicts. >>> >>> It sure does. See examples here: >>> http://svnbook.red-bean.com/nightly/en/svn.tour.treeconflicts.html >> >> We notice tree conflict after folder moves. Not seen one for a file move yet. >> This example only about file issues not folder issues. >> >>> >>>> Did I miss the way to find the tree conflicts? >>> >>> Not sure. What commands are you running and what output are you seeing? >> >> svn st -q >> >> and the output is blank. >> >> (I ran svn st -q after pysvn workbench failed to show anything problems.) > > What version of svn? Below 1.6.3? Some at 1.6.5 others at 1.5.4. > If so, this could be http://subversion.tigris.org/issues/show_bug.cgi?id=3382 > which was fixed in 1.6.3. ok. I'll make sure everybody is updated to this version of better. > > If this is not the problem, please try to come up with a script that > others can use to reproduce the problem, starting from an empty > repository. Will do if I see this again. Barry
Migrating to SVN from zipfile-based archival. Advice?
I've been using zipfiles to make snapshots of my development directories. Recently, I've decided maybe a solution that's a little more robust might be in order, so I'm looking to migrate to SVN. I'd like a bit of advice on how to go about doing that. Perhaps even just a sanity check. Using the standard layout, I figured the current source would get imported under trunk/ and each snapshot should be unzipped and imported as a tag (eg: tags/release_x). If I understood correctly, unlike, say, RCS, since SVN doesn't version individual files, I guess it doesn't matter so much what order things get imported in. Right? If I follow this course of action, would I end up being penalized in terms of disk usage or performance over some other, preferred method? Is the SVN server smart enough to realize that, even if I follow this course of action, that /trunk/foo/bar.c /tags/release1/foo/bar.c /tags/release2/foo/bar.c are all the same file with minor (if any) differences? Thanks.
Re: Migrating to SVN from zipfile-based archival. Advice?
On 06/10/2010 06:24 PM, Lieven Govaerts wrote: All files from svn.collab.net have been copied to svn.apache.org. You're probably talking about svn_load_dirs.pl, which is the tool that the documentation refers to in the 'vendor drop' chapter. You can find it here: http://svn.apache.org/repos/asf/subversion/trunk/contrib/client-side/svn_load_dirs/ Excellent. I read through the section on vendor drops, and it looks relatively straightforward. I'll pull a copy of svn_load_dirs.pl and read through it to make sure everything makes sense. From the overview, it looked like it might handle adding/removing files automagically, as necessary. I may be wrong, but I'll find out when I look at the code. And I'm assuming that if, in the course of importing things, I find I accidentally skipped a snapshot I want preserved, I'll want to check-out the snapshot prior to the one I want to import before overwriting with, and importing the skipped one.
Subversion 1.6.12 and Python 2.7
Hello folks, I'm currently working on adding Python 2.7 support to Ubuntu, and am in the process of investigating build problems with various packages. One such package is Subversion, which appears to build just fine against Python 2.7 but fails a handful of tests. I can see from this message http://article.gmane.org/gmane.comp.version-control.subversion.devel/120567/match=python+2.7 the same set of failing tests. I'm also building/testing 1.6.12 (or thereabouts). Building against Python 2.6 has no problems. I've looked at the tests but don't understand them well enough for any obvious problems to jump out at me. I was unable to find any open issues tracking these failures. Does anybody have any additional information? Is anybody working on fixing the failing Python 2.7 tests? Is there an open bug on the issue? I'd be happy to work with folks to put together a set of patches to fix the Python 2.7 bindings. I'm tempted to just disable the tests for now to get a working package. I am not on this mailing list so please do CC me or contact me directly off-list. Cheers, -Barry signature.asc Description: PGP signature
Re: Subversion 1.6.12 and Python 2.7
On Aug 19, 2010, at 11:03 PM, Daniel Shahaf wrote: >(Just to clarify, this is about the *python bindings* tests, not about >the Python tests of the core C binaries subversion/svn*/) Yes, I believe that's correct. >Barry Warsaw wrote on Wed, Aug 18, 2010 at 17:38:04 -0400: >> Does anybody have any additional information? Is anybody working on >> fixing the failing Python 2.7 tests? Is there an open bug on the >> issue? >> > >I don't recall hearing anything of this issue, other than your mail and >Arfrever's mail that you link to. Okay thanks. I'll try to submit a bug to the tracker, but I'm just trying to follow the workflow described here: http://subversion.apache.org/issue-tracker.html (hence the email to users@ ;). >Perhaps the best way to start would be for you to start analyzing some >of the failures and post your findings to dev@; I'm sure someone >familiar with the bindings will pick the thread up. Cool, thanks. -Barry signature.asc Description: PGP signature
win32svn for 1.9.1?
I see that the recent 1.7 and 1.8 win32svn builds being announced, thanks for them. Do you know when the svn 1.9 win32svn build might be available? Barry
Re: win32svn for 1.9.1?
> On 7 Sep 2015, at 11:43, Andreas Stieger wrote: > > Hi, > > Barry Scott wrote: >> I see that the recent 1.7 and 1.8 win32svn builds being announced, thanks >> for >> them. >> >> Do you know when the svn 1.9 win32svn build might be available? > > Available at other binary "vendors": > https://subversion.apache.org/packages.html#windows Sadly only win32svn packages the include files that are needed to write code against svn. In my case I use win32svn as the basis of the pysvn win32 build. Barry
Re: win32svn for 1.9.1?
> On 7 Sep 2015, at 21:21, Win32Svn wrote: > > On 2015-09-07 18:59, Barry Scott wrote: >>> On 7 Sep 2015, at 11:43, Andreas Stieger wrote: >>> >>> Hi, >>> >>> Barry Scott wrote: >>>> I see that the recent 1.7 and 1.8 win32svn builds being announced, thanks >>>> for >>>> them. >>>> >>>> Do you know when the svn 1.9 win32svn build might be available? >>> Available at other binary "vendors": >>> https://subversion.apache.org/packages.html#windows >> Sadly only win32svn packages the include files that are needed to write >> code against svn. In my case I use win32svn as the basis of the pysvn >> win32 build. >> >> Barry >> > > Hi Barry! > > I'm sorry to say there won't be any 1.9.x build of Win32SVN. > You can read about it on http://alagazam.net (click the 1.9.x info link on > the right) David, Sorry to hear that. But thank you for providing such useful win32 builds for so long. Barry > Regards, > David Darj a.k.a. Alagazam > Maintainer of Win32SVN > http://alagazam.net > > ps. > If you like my work, please support this project by donating at > http://sourceforge.net/donate/index.php?group_id=357628 > > >
Announcing pysvn WorkBench 1.7.0
PYSVN WorkBench release supporting Subversion 1.9.1, 1.8.14 and 1.7.22 Kits for Python 3.5 are new. Mac OS X kits are built for OSX 10.9 and 10.10. Improvements: * Support for svn 1.9.1 * Sources changes to make use of WorkBench on linux simpler for packagers * Add RPM spec file - tested on Fedora 22 * Add linux desktop file * Increase size of the Info dialog to show typical paths without truncation * updated to use wxPython 3.0.2 * Folders can now be added from the list view Bugs fixed: * On windows history could trigger a julian date error. * Fix for bug 202: CVE-2015-0853: insecure use of os.system() * Fix problems with the display of built in diff tool * issue 201: Fix problems with adding folders from the tree view Source Kit available from pysvn.tigris.org and pysvn.barrys-emacs.org: WorkBench-1.7.0.tar.gz Windows Installers available from pysvn.tigris.org: pysvn-workbench-svn1722-1.7.0-1661.exe pysvn-workbench-svn1814-1.7.0-1661.exe Note: No windows kit for svn 1.9.1 because of missing win32svn support Mac OS X Installers available from pysvn.tigris.org: pysvn_workbench_svn1722-1.7.0-1661-x86_64.dmg pysvn_workbench_svn1814-1.7.0-1661-x86_64.dmg pysvn_workbench_svn191-1.7.0-1661-x86_64.dmg Barry
Announcing pysvn Extension 1.8.0
PYSVN Extension release supporting Subversion 1.9.1, 1.8.14 and 1.7.22 Kits for Python 3.5 are new. Mac OS X kits are built for OSX 10.9 and 10.10. Features: * Support python3 sorting of list of PysvnDict objects that name a known "key”. * Support Subversion 1.9.1. Note: no Windows kit as no win32svn kits will be built. * Support Python 3.5 Bugs fixed: * issue 193: is_versioned is always 0 * issue 200: svn_client_root_url_from_path() would crash if login callback was called. Source Kit available from pysvn.tigris.org and pysvn.barrys-emacs.org: pysvn-1.8.0.tar.gz Windows Installers available from pysvn.tigris.org: py26-pysvn-svn1722-1.8.0-1667.exe py26-pysvn-svn1814-1.8.0-1667.exe py27-pysvn-svn1722-1.8.0-1667.exe py27-pysvn-svn1814-1.8.0-1667.exe py32-pysvn-svn1722-1.8.0-1667.exe py32-pysvn-svn1814-1.8.0-1667.exe py33-pysvn-svn1722-1.8.0-1667.exe py33-pysvn-svn1814-1.8.0-1667.exe py34-pysvn-svn1722-1.8.0-1667.exe py34-pysvn-svn1814-1.8.0-1667.exe py35-pysvn-svn1722-1.8.0-1667.exe py35-pysvn-svn1814-1.8.0-1667.exe Mac OS X Installers available from pysvn.tigris.org: py27_apple_com_pysvn_svn1722-1.8.0-1668-intel.dmg py27_apple_com_pysvn_svn1814-1.8.0-1668-intel.dmg py27_apple_com_pysvn_svn191-1.8.0-1668-intel.dmg py27_python_org_pysvn_svn1722-1.8.0-1668-intel.dmg py27_python_org_pysvn_svn1814-1.8.0-1668-intel.dmg py27_python_org_pysvn_svn191-1.8.0-1668-intel.dmg py32_python_org_pysvn_svn1722-1.8.0-1668-intel.dmg py32_python_org_pysvn_svn1814-1.8.0-1668-intel.dmg py32_python_org_pysvn_svn191-1.8.0-1668-intel.dmg py33_python_org_pysvn_svn1722-1.8.0-1668-intel.dmg py33_python_org_pysvn_svn1814-1.8.0-1668-intel.dmg py33_python_org_pysvn_svn191-1.8.0-1668-intel.dmg py34_python_org_pysvn_svn1722-1.8.0-1668-intel.dmg py34_python_org_pysvn_svn1814-1.8.0-1668-intel.dmg py34_python_org_pysvn_svn191-1.8.0-1668-intel.dmg py35_python_org_pysvn_svn1722-1.8.0-1668-intel.dmg py35_python_org_pysvn_svn1814-1.8.0-1668-intel.dmg py35_python_org_pysvn_svn191-1.8.0-1668-intel.dmg Barry
Re: SVN 1.6.17 dump is growing larger than repository size (approx. more than 10 times)
Unless svn's changed, you can look in your repositories directory on the server, e.g., repos/myproj/db/revs/0/ and you can see each revision stored there. Under the db directory is revs and also revprops, and under each of those is one or more subdirectory (mine just had one called "0"). If you see one that is outrageously large, then dump is just trying to do its job. If they are all reasonable size, then maybe there's a circular reference or some other bug. Also, svnadmin dump just goes to standard-out, so you can send it to the screen, or through a grep filter or some other ingenious scheme to try to get a handle on what's happening. Barry On Wed, Nov 25, 2015 at 4:41 AM, Nico Kadel-Garcia wrote: > On Wed, Nov 25, 2015 at 4:25 AM, arun prasath wrote: > > Hello Team, > > > > I am creating Subversion 1.6.17 dump for a repository hosted in Linux > > server. SVNSERVE is serving the repository. We are migrating to SVN > 1.9.2. > > > > While creating the dump for repository of size 1.8 GB (revisions 3000+), > the > > dump command completes revision 119 and hangs and keep updating the > dumpfile > > which grows to 7-8 GBs. dump command is not moving to next revision but > kept > > updating the dump file. So, i just closed the putty to stop creating the > > dump. > > Which Linux? And are you using the verndor provided version, or a > locally compiled one? Subversion 1.6 was last up to 1.6.23: is there > any reason you can't upgrade that? Ideally with a hotcopy or "rsync" > based copy of the repository to somehwere else, for testing the copy? > > > However, I ran the svnadmin verify which completes revision 119 and take > > some time to verify revision 120 and complete the verification > successfully > > for all the repository revisions. > > Hmm. You might consider skipping the svnadmin dump command, and simply > setting up an svnsync mirror on the Subversion 1.9 server. Even using > "rsync" to bring the old repository over should let you run a dump and > reload on the server with Subversion 1.9, as long as there's not some > other weird corruption with revision 119 or 120. > > > Since, there is no error output I have no logs to attach. Please suggest > the > > work around for this situation. How can create the dump and migrate to > > target server. I am planning to use rsync from the server. I will post > how > > it goes. > > > > I am expecting the workaround to this situation and let me know if this > is a > > known issue in SVN 1.6.17. This is my active repository and created the > dump > > without stopping the svnserve program in the production server. > > It's not one I've seen, but I don't let my repositories get that big. > And I'd look at revisions 119 and 120 to see if there were erroneous > commits of huge binary files, in which case I'd want to exclude them > from the backup. >
"svn update --set-depth=exclude" exits prematurely, leaving repo in need of cleanup
When excluding a subtree from the working copy, if any unversioned items are present then the svn update command fails silently, leaving the working copy locked and requiring cleanup. This is with version 1.9.4, the current release. Reproducing the problem is fairly straightforward. Create a new repo (or just use an existing one): $ svnadmin create repo $ svn checkout file://`pwd`/repo wc Checked out revision 0. Add a directory and subdirectory: $ cd wc $ mkdir dir $ mkdir dir/subdir1 $ svn add dir A dir A dir/subdir1 $ svn commit -m "Added dir" Adding dir Adding dir/subdir1 Committing transaction... Committed revision 1. Create another subdirectory, without adding it to the repo: $ mkdir dir/subdir2 Now, let's exclude "dir" from the working copy: $ svn update --set-depth exclude dir D dir/subdir1 OK, so svn says it has deleted "dir/subdir1", but has left "dir" alone. Fair enough, as "dir" contains the unversioned item "subdir2". But wait - let's take a peek: $ ls dir subdir1 subdir2 Huh? What is "subdir1" still doing there? Let's quickly do a regular update: $ svn update svn: E155037: Previous operation has not finished; run 'cleanup' if it was interrupted Oooh, that's not good! Let's take a closer look: $ svn status L . L dir ? dir\subdir1 ? dir\subdir2 Yikes! Looks like svn bailed out without finishing the job. This must be a bug, right? Any chance somebody can take a look at it? Thanks!
Re: "svn update --set-depth=exclude" exits prematurely, leaving repo in need of cleanup
> This must be a bug, right? Any chance somebody can take a look at it? [... tumbleweed ...] Anyone? Should I file a bug report? Thanks
Re: "svn update --set-depth=exclude" exits prematurely, leaving repo in need of cleanup
Branko Čibej writes: > I can reproduce this with 1.9.4 and trunk ... definitely a bug, only > dir/subdir2 should be left (since dir/subdir2 is unversioned content of > dir). Thanks Brane. Would it be possible for an svn dev to take this on? By the way, I just checked it with 1.8.16 and everything works as expected, so it seems this bug was introduced in 1.9.x. - Jim
Re: "svn update --set-depth=exclude" exits prematurely, leaving repo in need of cleanup
Branko Čibej wrote: > Please file a bug with the reproduction script. OK, the issue number is SVN-4642. Thanks
Announcing SCM Workbench 0.8.5 GUI for Git, Mercurial (hg) and Subversion (svn)
SCM Workbench features • Support Subversion (svn), Mercurial (hg) and Git projects. • Easy to learn and use • Built in User Guide describes the operation and features of the application. • Add project wizard can scan for all your existing projects. • All subversion client operations in a GUI • Many Git client operations in a GUI • GUI git rebase • Some mercurial (hg) client operations in a GUI • Enhanced operations (subversion rename of modified files etc) • Support software development workflow • Built in GUI diff showing line and character diffs • Ability to diff between commits in a files history • Runs on Windows, Mac OS X and Unix platforms Kits are available for Windows, macOS and Fedora. Please visit http://scm-workbench.barrys-emacs.org/ for downloads and further information on SCM Workbench. Barry
Announcing SCM Workbench 0.8.6 for Git, Mercurial and Subversion
SCM Workbench features • Support Subversion (svn), Mercurial (hg) and Git projects. • Easy to learn and use • Builtin User Guide describes the operation and features of the application. • Add project wizard can scan for all your existing projects. • All subversion client operations in a GUI • Many Git client operations in a GUI • GUI git rebase • Some mercurial (hg) client operations in a GUI • Enhanced operations (subversion rename of modified files etc) • Support software development workflow • Builtin GUI diff showing line and character diffs • Ability to diff between revisions in a files history • Runs on Windows, Mac OS X and Unix platforms Please visit http://scm-workbench.barrys-emacs.org/ for downloads, git source, user guide and further information on SCM Workbench. New in 0.8.6 • Dialog feedback has been refactored to give a cleaner user experience in the Add project wizard. • Add basic git stash support. • Update to use python3.6 and latest PyQt5. • Fixes for minor issues found by pylint. • Improvements to build tooling. Barry
Announcing pysvn Extension 1.9.6
PYSVN Extension release supporting Subversion 1.10.0, 1.9.7 and 1.8.19 This is update to pysvn which adds support for subversion 1.10.0. Mac OS X kits are built for OSX 10.9 and later, testing on 10.13 Windows kits are build for Windows 7 or latest, tested on Windows 10. Windows 64 bit kits are now available. Note: python 3.3 and 3.4 64 bit support is not practical as the required Microsoft Compiler will not install its 64 bit support on Windows 10. Improvements: * Use subversion 1.0 APIs as appropiate Bugs fixed: * size fields are correctly returned as None if no size is know by subversion. Source Kit is available from pysvn.tigris.org and pysvn.barrys-emacs.org: pysvn-1.9.6.tar.gz Windows Installers available from pysvn.tigris.org: py27-pysvn-svn1100-1.9.6-1961-Win32.exe py27-pysvn-svn1100-1.9.6-1961-Win64.exe py27-pysvn-svn1819-1.9.6-1961-Win32.exe py27-pysvn-svn1819-1.9.6-1961-Win64.exe py27-pysvn-svn197-1.9.6-1961-Win32.exe py27-pysvn-svn197-1.9.6-1961-Win64.exe py33-pysvn-svn1100-1.9.6-1961-Win32.exe py33-pysvn-svn1819-1.9.6-1961-Win32.exe py33-pysvn-svn197-1.9.6-1961-Win32.exe py34-pysvn-svn1100-1.9.6-1961-Win32.exe py34-pysvn-svn1819-1.9.6-1961-Win32.exe py34-pysvn-svn197-1.9.6-1961-Win32.exe py35-pysvn-svn1100-1.9.6-1961-Win32.exe py35-pysvn-svn1100-1.9.6-1961-Win64.exe py35-pysvn-svn1819-1.9.6-1961-Win32.exe py35-pysvn-svn1819-1.9.6-1961-Win64.exe py35-pysvn-svn197-1.9.6-1961-Win32.exe py35-pysvn-svn197-1.9.6-1961-Win64.exe py36-pysvn-svn1100-1.9.6-1961-Win32.exe py36-pysvn-svn1100-1.9.6-1961-Win64.exe py36-pysvn-svn1819-1.9.6-1961-Win32.exe py36-pysvn-svn1819-1.9.6-1961-Win64.exe py36-pysvn-svn197-1.9.6-1961-Win32.exe py36-pysvn-svn197-1.9.6-1961-Win64.exe Mac OS X Installers available from pysvn.tigris.org: py27_apple_com_pysvn_svn1100-1.9.6-1961-intel.dmg py27_apple_com_pysvn_svn1819-1.9.6-1961-intel.dmg py27_apple_com_pysvn_svn197-1.9.6-1961-intel.dmg py27_python_org_pysvn_svn1100-1.9.6-1961-intel.dmg py27_python_org_pysvn_svn1819-1.9.6-1961-intel.dmg py27_python_org_pysvn_svn197-1.9.6-1961-intel.dmg py34_python_org_pysvn_svn1100-1.9.6-1961-intel.dmg py34_python_org_pysvn_svn1819-1.9.6-1961-intel.dmg py34_python_org_pysvn_svn197-1.9.6-1961-intel.dmg py35_python_org_pysvn_svn1100-1.9.6-1961-intel.dmg py35_python_org_pysvn_svn1819-1.9.6-1961-intel.dmg py35_python_org_pysvn_svn197-1.9.6-1961-intel.dmg py36_python_org_pysvn_svn1100-1.9.6-1961-x86_64.dmg py36_python_org_pysvn_svn1819-1.9.6-1961-x86_64.dmg py36_python_org_pysvn_svn197-1.9.6-1961-x86_64.dmg Barry
PYSVN Release 1.9.10
PySVN home page: https://pysvn.sourceforge.io/ PySVN 1.9.10 supporting Subversion 1.12.0 and earlier. Changes: * Built against subversion 1.12.2, 1.11.1, 1.10.6 and 1.9.12 * Built against PyCXX 7.1.3 to pick up fix for a memory leak with python 3 strings * Prepare for Python 3.8 - binary kit will be available after python 3.8 is released PySVN supports Python 3 as well as Python 2. Prebuilt kits are available for Windows and Mac OS X built for subversion 1.12.2, 1.11.1, 1.10.6 and 1.9.12 for python 2.7, 3.3 to 3.7. Download details: https://pysvn.sourceforge.io/downloads.html Barry
Re: PYSVN Release 1.9.10
> On 6 Aug 2019, at 15:50, Daniel Shahaf wrote: > > Barry Scott wrote on Mon, 05 Aug 2019 10:14 +00:00: >> Changes: >> * Built against subversion 1.12.2, 1.11.1, 1.10.6 and 1.9.12 > > Subversion 1.11.1 is no longer supported by the Subversion project (it was a > non-LTS release). > > Subversion 1.9.12 may have EOL'd yesterday; we're currently discussing that > (on our dev@ list). > Traditionally I have been asked for builds against more versions of subversion and python then where supported by upstream. I was also contemplating only supporting the versions of subversion and python that upstream still supports. I am minded to implement that policy for the next pysvn release. But I suspect I will not be dropping python 2.7 builds, even after 2.7 EOLs next year. Barry
Announcing Scm Workbench 0.9.3 for Git, Mercurial and Subversion
SCM Workbench features • Support Subversion (svn), Mercurial (hg) and Git projects. • Experimental support for Perforce (P4) • Easy to learn and use • Builtin User Guide describes the operation and features of the application. • Add project wizard can scan for all your existing projects. • All subversion client operations in a GUI • Many Git client operations in a GUI • GUI git rebase • Some mercurial (hg) client operations in a GUI • Enhanced operations (subversion rename of modified files etc) • Support for Dark mode • Support software development workflow • Builtin GUI diff showing line and character diffs • Ability to diff between revisions in a files history • Runs on Windows, Mac OS X and Unix platforms Please visit http://scm-workbench.barrys-emacs.org/ for downloads, git source, user guide and further information on SCM Workbench. New in 0.9.3 • Lots of improvement since the last release • Update to use python3.7, PyQt5 5.12 and pysvn with svn 1.12 Barry
PYSVN Release 1.9.11
PySVN home page: https://pysvn.sourceforge.io/ PySVN 1.9.11 supporting Subversion 1.13.0 and earlier. Changes: * Binary kits limited to using currently support versions of Subversion and Python. However python 2.7 kits will be provided after python 2.7 goes end-of-life. * Add suport for subversion 1.13 * Build binary kits for Python 3.8 * Add support for gpg-agent auth provider * Fix problem building against svn 1.7 which is needed for Centos 7 support PySVN supports Python 3 as well as Python 2. Prebuilt kits are available for Windows and Mac OS X built for subversion 1.13.0, 1.10.6 and 1.9.12 for python 2.7, 3.5, 3.6, 3.7 and 3.8. Download details: https://pysvn.sourceforge.io/downloads.html Barry
How do I enable storing of plaintext passwords?
I'm doing some testing and want to test with plaintext passwords. It seems that storing plaintext passwords can be compiled out. Is that why I cannot configure it back on? Barry
PySVN Release 1.9.12
PySVN home page: https://pysvn.sourceforge.io/ PySVN 1.9.12 supporting Subversion 1.14.0 and earlier. Changes: * Binary kits limited to using currently support versions of Subversion and Python. However python 2.7 kits will be provided after python 2.7 goes end-of-life. * Add support for subversion 1.14 * Build binary kits for Python 3.9b1 * Add support for gpg-agent auth provider * Fix problem building against svn 1.7 which is needed for Centos 7 support PySVN supports Python 3 as well as Python 2. Prebuilt kits are available for Windows and Mac OS X built for subversion 1.14.0 and 1.10.6 for python 2.7, 3.5, 3.6, 3.7, 3.8 and 3.9b1. Download details: https://pysvn.sourceforge.io/downloads.html Barry
Announcing Scm Workbench 0.9.4 for Git, Mercurial and Subversion
SCM Workbench features * Support Subversion (svn), Mercurial (hg) and Git projects. * Experimental support for Perforce (P4) * Easy to learn and use * Builtin User Guide describes the operation and features of the application. * Add project wizard can scan for all your existing projects. * All subversion client operations in a GUI * Many Git client operations in a GUI * GUI git rebase * Some mercurial (hg) client operations in a GUI * Enhanced operations (subversion rename of modified files etc) * Support for Dark mode * Support software development workflow * Builtin GUI diff showing line and character diffs * Ability to diff between revisions in a files history * Runs on Windows, Mac OS X and Unix platforms Please visit http://scm-workbench.barrys-emacs.org/ for downloads, git source, user guide and further information on SCM Workbench. New in 0.9.4 * Feature to show all commits since a tag (great for writing release notes) * Update to Python 3.8 for built kits * Build tools for macOS and Windows use venv * Fix problem with creating editor and shell process on macOS 10.15 * Fix traceback with changing SVN properties * Fix styles for light mode diff * Support favourites that start with "Config". Barry
PySVN Release 1.9.13
PySVN home page: https://pysvn.sourceforge.io/ PySVN 1.9.13 supporting Subversion 1.14.1 and earlier. Changes: * Add support for subversion 1.14.1 * Use latest openssl 1.1.1k * Fix issue with Client.mkdir() on Windows python 3.8 and later * No longer able to build python 2.7 kits for Windows. An issue with incompatible C++ DLL PySVN supports Python 3 as well as Python 2. Prebuilt kits are available for Windows and Mac OS X built for subversion 1.14.1 and 1.10.7 for python 3.6, 3.7, 3.8 and 3.9. Note: Python 2.7 kits only for macOS. Download details: https://pysvn.sourceforge.io/downloads.html Barry
Authentication Issue
Hello, We have a service account in our domain that we use for our builds. I am trying to connect to our Subversion server via the command line: svn co --username BuildUser --password private --no-auth-cache https://svnserver/Repo1/trunk/ This works fine from my local machine, but from the build server I receive: svn: E170001: OPTIONS of : authorization failed: Could not authenticate to server: rejected Basic challenge Any ideas on why this would work on one machine, but not another? Thank you, Barry
RE: Authentication Issue
Thanks Johan. The solution ended up being to reset the password in the domain. The odd thing is the user account was fine, not locked and the password was not expired. It had been approximately 90 days since we set the password, so I assume something is going on with the domain settings or user account. -Original Message- From: Johan Corveleyn [mailto:jcor...@gmail.com] Sent: Tuesday, June 10, 2014 7:11 PM To: Pape, Barry Cc: users@subversion.apache.org Subject: Re: Authentication Issue On Tue, Jun 10, 2014 at 11:21 PM, Pape, Barry wrote: > Hello, > > > > We have a service account in our domain that we use for our builds. I > am trying to connect to our Subversion server via the command line: > > svn co --username BuildUser --password private --no-auth-cache > https://svnserver/Repo1/trunk/ > > > > This works fine from my local machine, but from the build server I receive: > > svn: E170001: OPTIONS of : authorization failed: Could not > authenticate to > server: rejected Basic challenge > > > > > > Any ideas on why this would work on one machine, but not another? > The first obvious thing to check is: is it the same version of svn client software? 'svn --version' should tell you. The second thing: what about the network route? Any proxies, firewalls, ... differences between both network paths? -- Johan
svnsync via svn+ssh w/key authentication: password prompt
I am attempting to use svnsync over a SSH tunnel, which works, but always prompts for a password. I already setup ssh key authentication, which does work fine when performing svn commands. I can establish a SSH tunnel with keys like this - no password prompts: ssh servername Using svn, I can do this without being prompted for a password: svn list svn+ssh://servername/path/to/repos However, this does prompt for a password: svnsync sync svn+ssh://servername/path/to/repos And just for good measure, this does the same thing: svnsync sync svn+ssh://username@servername/path/to/repos Any ideas of what I can do here to eliminate the password prompt? My goal is to automate a 'push' synchronization via hooks scripts.
RE: svnsync via svn+ssh w/key authentication: password prompt
Thank you for the advice on the hooks, it will be helpful. At this point, I’m trying to get it working from a command line first, and I’m not using ssh agent. I am using a keyfile without a passphrase. What is a little confusing is that my attempts work with ‘svn’ commands (I don’t have to enter a password), but not ‘svnsync’ commands (I DO have to enter a password). Using ‘svn+ssh’, do both commands establish a tunnel, and start an instance of svnserve? From: Andreas Stieger [mailto:andreas.stie...@gmx.de] Sent: Friday, August 29, 2014 12:20 PM To: Sampson, Barry Cc: users@subversion.apache.org Subject: Re: svnsync via svn+ssh w/key authentication: password prompt On 29 Aug 2014, at 17:22, "Sampson, Barry" mailto:barry.samp...@teejet.com>> wrote: I am attempting to use svnsync over a SSH tunnel, which works, but always prompts for a password. I already setup ssh key authentication, which does work fine when performing svn commands. I can establish a SSH tunnel with keys like this – no password prompts: ssh servername Using svn, I can do this without being prompted for a password: svn list svn+ssh://servername/path/to/repos However, this does prompt for a password: svnsync sync svn+ssh://servername/path/to/repos And just for good measure, this does the same thing: svnsync sync svn+ssh://username@servername/path/to/repos Any ideas of what I can do here to eliminate the password prompt? My goal is to automate a ‘push’ synchronization via hooks scripts. Hooks execute in a mostly empty environment so your ssh client will not have access to the ssh agent. Add a wrapper to compensate, e.g. Specify a passphrase less key file (-i) or configure hook environment via conf/hooks-env (from 1.8) to find the ssh agent. As it's pid/socket will change that is a moving target. You should it run --non-interactive in either case. Andreas
pysvn does not build against 1.9-alpha2 because of incomplete type 'const svn_sort__item_t'
I have been building pysvn against the latest svn kits. 1.7.18, 1.8.10 and 1.9.0-alpha2 using the Mac OS X Xcode 6.1 command line tools, clang is the compiler not gcc. Compiling and testing pysvn against 1.7.18 and 1.8.10 works with no errors. But I get compile errors when compiling pysvn against 1.9.0-alpha2: pysvn_client_cmd_info.cpp:1383:39: error: use of undeclared identifier 'svn_sort__hash' apr_array_header_t *statusarray = svn_sort__hash( status_hash, svn_sort_compare_items_as_paths, pool ); ^ pysvn_client_cmd_info.cpp:1388:41: error: subscript of pointer to incomplete type 'const svn_sort__item_t' const svn_sort__item_t *item = &APR_ARRAY_IDX( statusarray, i, const svn_sort__item_t ); ^~~ /usr/include/apr-1/apr_tables.h:141:57: note: expanded from macro 'APR_ARRAY_IDX' #define APR_ARRAY_IDX(ary,i,type) (((type *)(ary)->elts)[i]) ~^ svn_sort.h has been included. Barry
Re: pysvn does not build against 1.9-alpha2 because of incomplete type 'const svn_sort__item_t'
Thanks will the required changes be in alpha3? Is it possible to do the sort without using the private API? Barry pysvn author On 6 Nov 2014, at 19:55, Ben Reser wrote: > On 11/6/14 5:10 AM, Nico Kadel-Garcia wrote: >> Out of curiosity, do the same issues occur with gcc on a modern box? >> Ther'e's a lot to like about MacPorts, but I don't think it's the >> primary build and testing platform for Subversion. > > Yes gcc is going to have the same issues because the declarations he needs > have > been removed from svn_sorts.h These declarations have been there since 1.0. > Prior to 1.0 they had names in the APR namespace, since it was expected this > functionality would be moved to APR. Before 1.0 we cleaned up that namespace > problem and marked them private (by documentation and by using __ in the > names). Of course since they were still in a public header they are > effectively public APIs. Bert noticed that there were a lot of these private > APIs added to the svn_sorts.h header since 1.8 on trunk and so he moved all of > them into a private header that isn't installed. This meant he moved the ones > that had been there since 1.0, thus breaking any 3rd party code that depended > on them. > > Ideally we would have never exposed these. Ideally 3rd parties would have > observed the private markers and not used them. > > I suggested that we resolve this by restoring the long standing private APIs > that had been exposed. While not adding any new APIs. If nobody objects to > that suggestion soon I'm going to just do it. >
Re: Can't set permissions on 'barrys-sources/db/revs/2': Operation not permitted
> On 15 Dec 2024, at 15:52, Nathan Hartman wrote: > > (Apologies for the duplicate; I meant to respond to the users@ list > but omitted it the first time...) > > On Fri, Dec 13, 2024 at 12:10 PM Barry Scott wrote: >> >> I have a svn repo hosted on a Fedora server that I access via http: using >> mod_dav_svn-1.14.4-1.fc41.x86_64. >> >> The repo has 1999 revs in it but fails to create rev 2000 with these errors >> in the httpd error log: >> >> [dav:error] An error occurred while committing the transaction. [500, #1] >> [dav:error] Can't set permissions on >> '/shared/SourceControl/barrys-sources/db/revs/2' [500, #1] >> [dav:error] Can't set permissions on >> '/shared/SourceControl/barrys-sources/db/revs/2': Operation not permitted >> [500, #1] >> >> As use apache I can create and delete a the file >> >> /shared/SourceControl/barrys-sources/db/revs/2/tmp >> >> I have tried to svnadmin dump and svnadmin load to see if that makes a >> difference. >> But the problem is identical on the old and new repos. >> >> What do I need to investigate and fix to allow rev 2000? >> >> Barry > > > Hi Barry, > > I would check permissions and ownership I had set the ownership with `chown -R apache: ` so assumed that had set everything to allow apache user to do what it wants. I could not find any file with the wrong permissions. What "fixed" it was using sudo svn mkdir file:Test to force the creation of a rev 2000. Then I fixed the perms that using root changed the revs/2 dir and the 2000 file. I did this on the svnadmin loaded new repos. After that apache user can create revs. I still have the original "bad" repo as-is and it does not have any permission issue I can see. > > It looks like you already verified that user 'apache' can create a > file in in the db/revs/2 subdirectory. However, only the owner* of a > file or directory can change its permissions. Is 'apache' the owner of > the '2' subdirectory? > > Since it worked until revision 1999, who is the owner of the '1' > subdirectory (which contains revs 1000-1999) and how are its > permissions? > > Also who is the owner of the parent 'revs' subdirectory and how are > its permissions? > > It's possible that some time in the past, after revision 1000 but > before now, that the ownership of these directories changed for some > reason. Software updates? Moving things to a new hard drive? A > permissions check that automatically "fixed" things? It wasn't noticed > until now because the '2' subdirectory isn't created until revision > 2000. I have to assume that is the case but I cannot see the error and it my mistake. All files are owned by apache:apache Here is ll of the original bad repo: $ ll barrys-sources.bad/db total 2680 -rw-r--r--. 1 apache apache 5 2024-12-13 15:49:15 current -r--r--r--. 1 apache apache 22 2011-05-22 13:26:57 format -rw-r--r--. 1 apache apache1920 2011-05-22 13:26:57 fsfs.conf -rw-r--r--. 1 apache apache 5 2011-05-22 13:26:57 fs-type drwxr-sr-x. 6 apache apache4096 2016-06-19 20:31:18 locks/ -rw-r--r--. 1 apache apache 2 2011-05-22 13:26:57 min-unpacked-rev -rw-r--r--. 1 apache apache 2690048 2024-12-13 15:49:15 rep-cache.db -rw-r--r--. 1 apache apache 0 2024-12-13 15:49:15 rep-cache.db-journal drwxr-sr-x. 4 apache apache4096 2016-08-10 16:30:28 revprops/ drwxr-sr-x. 5 apache apache4096 2024-12-13 15:49:45 revs/ drwxr-sr-x. 2 apache apache4096 2024-12-13 16:19:04 transactions/ -rw-r--r--. 1 apache apache 4 2024-12-13 16:19:01 txn-current -rw-r--r--. 1 apache apache 0 2011-05-22 13:26:57 txn-current-lock drwxr-sr-x. 2 apache apache4096 2024-12-13 16:19:04 txn-protorevs/ -rw-r--r--. 1 apache apache 37 2011-05-22 13:43:56 uuid -rw-r--r--. 1 apache apache 0 2011-05-22 13:26:57 write-lock $ ll barrys-sources.bad/db/revs total 44 drwxr-sr-x. 2 apache apache 20480 2016-07-22 10:28:14 0/ drwxr-sr-x. 2 apache apache 20480 2024-12-13 15:49:15 1/ drwxr-sr-x. 2 apache apache 4096 2024-12-13 15:49:45 2/ FYI I have selinux in permissive mode so that does not have any effect. > > [*] It's not strictly true that *only* the owner of a file or > directory may change its permissions. The root user may also do so; > however, please *don't* run the server as root! Now that would be a terrible idea! Barry > > Hope this helps, > Nathan >
Can't set permissions on 'barrys-sources/db/revs/2': Operation not permitted
I have a svn repo hosted on a Fedora server that I access via http: using mod_dav_svn-1.14.4-1.fc41.x86_64. The repo has 1999 revs in it but fails to create rev 2000 with these errors in the httpd error log: [dav:error] An error occurred while committing the transaction. [500, #1] [dav:error] Can't set permissions on '/shared/SourceControl/barrys-sources/db/revs/2' [500, #1] [dav:error] Can't set permissions on '/shared/SourceControl/barrys-sources/db/revs/2': Operation not permitted [500, #1] As use apache I can create and delete a the file /shared/SourceControl/barrys-sources/db/revs/2/tmp I have tried to svnadmin dump and svnadmin load to see if that makes a difference. But the problem is identical on the old and new repos. What do I need to investigate and fix to allow rev 2000? Barry
