Change prevprops in pre-commit
Hello, I see in pre-commit hook template that changing revisions properties in transaction are allowed. But I can't find way for it (I want change svn:author to more readable). Is here way for this with svn, svnadmin, svnlook ... or other standard tool? Or I should use Subversion API and write simple tool? BR, Sergey Azarkevich
Re: Change prevprops in pre-commit
> On 8 Sep 2014, at 08:20, Sergey Azarkevich wrote: > > Hello, > > I see in pre-commit hook template that changing revisions properties in > transaction are allowed. > But I can't find way for it (I want change svn:author to more readable). > > Is here way for this with svn, svnadmin, svnlook ... or other standard tool? > Or I should use Subversion API and write simple tool? This question was recently answered in the "commit bot" thread. Please check the archives. Andreas
Re: Change prevprops in pre-commit
Sergey Azarkevich writes: > I see in pre-commit hook template that changing revisions properties in > transaction are allowed. > But I can't find way for it (I want change svn:author to more readable). > > Is here way for this with svn, svnadmin, svnlook ... or other standard > tool? Or I should use Subversion API and write simple tool? I think we should provide command line support for setting txnprops. The code is simple enough, the iterface is a bit harder. There was was some debate on IRC as to whether it should be svnlook propset -t txn or svnadmin settxnprop -t txn For svnlook it means adding a write subcommand to a program that at present is read-only. If we add "-r REV" support to be consistent with other subcommands then we would then need further options to run/bypass hooks. This would then overlap with the existing "svnadmin setrevprop". For svnadmin it means that a pre-commit needs to use different programs for reading and writing txnprops rather than just using svnlook, and the name new name "settxnprop" is a different pattern from the existing "propget" name. We will probably need some way to delete txnprops as well. There is currently a new-in-1.9 "svnadmin delrevprop" to delete revision properties, so either "svnlook propdel" or "svnadmin deltxnprop". Or perhaps the new subcommand to set txnprops should allow a way to delete as well? -- Philip Martin | Subversion Committer WANdisco // *Non-Stop Data*
Re: Change prevprops in pre-commit
On Mon, Sep 8, 2014 at 3:26 PM, Philip Martin wrote: > > I think we should provide command line support for setting txnprops. > The code is simple enough, the iterface is a bit harder. There was was > some debate on IRC as to whether it should be > >svnlook propset -t txn > > or > >svnadmin settxnprop -t txn > > For svnlook it means adding a write subcommand to a program that at > present is read-only. If we add "-r REV" support to be consistent with > other subcommands then we would then need further options to run/bypass > hooks. This would then overlap with the existing "svnadmin setrevprop". > > For svnadmin it means that a pre-commit needs to use different programs > for reading and writing txnprops rather than just using svnlook, and the > name new name "settxnprop" is a different pattern from the existing > "propget" name. > > We will probably need some way to delete txnprops as well. There is > currently a new-in-1.9 "svnadmin delrevprop" to delete revision > properties, so either "svnlook propdel" or "svnadmin deltxnprop". > Or perhaps the new subcommand to set txnprops should allow a way to > delete as well? This would be much appreciated, we talked about this this morning in the wake of our Python hack modifying transaction files directly. I don't know what the tools look like on the inside, but to me it would be nice if the interface treated -r and -t as interchangeable, so it was just a matter of choosing whether you wanted to poke at a transaction-in-flight or an existing revision. - Kim
Re: Change prevprops in pre-commit
Philip Martin wrote: > Sergey Azarkevich writes: > >> I see in pre-commit hook template that changing revisions properties in >> transaction are allowed. >> But I can't find way for it (I want change svn:author to more readable). >> >> Is here way for this with svn, svnadmin, svnlook ... or other standard >> tool? Or I should use Subversion API and write simple tool? > > I think we should provide command line support for setting txnprops. > The code is simple enough, the iterface is a bit harder. There was was > some debate on IRC as to whether it should be > > svnlook propset -t txn > > or > > svnadmin settxnprop -t txn or svnadmin setrevprop -t txn is another reasonable option. > For svnlook it means adding a write subcommand to a program that at > present is read-only. If we add "-r REV" support to be consistent > with > other subcommands then we would then need further options to run/bypass > hooks. This would then overlap with the existing "svnadmin > setrevprop". > > For svnadmin it means that a pre-commit needs to use different programs > for reading and writing txnprops rather than just using svnlook, and the > name new name "settxnprop" is a different pattern from the existing > "propget" name. > > We will probably need some way to delete txnprops as well. There is > currently a new-in-1.9 "svnadmin delrevprop" to delete revision > properties, so either "svnlook propdel" or "svnadmin > deltxnprop". or, again, "svnadmin delrevprop -t TXN ...". > Or perhaps the new subcommand to set txnprops should allow a way to > delete as well? For reference, the rev-prop/txn-prop commands currently available in 'svnadmin' and 'svnlook' are: svnadmin setlog -r REV [--bypass-hooks] FILE setrevprop -r REV [--use-pre|post-revprop-change-hook] NAME FILE delrevprop -r REV [--use-pre|post-revprop-change-hook] NAME # new for 1.9 svnlook author [-t TXN|-r REV] date [-t TXN|-r REV] log [-t TXN|-r REV] propget [-t TXN|-r REV] --revprop NAME proplist [-t TXN|-r REV] --revprop Notice that there is already a lot of inconsistency in the commands and their options. 'svnlook' has so far been read-only, as the name 'svnlook' implies. That could change, although some people may be uncomfortable with that. An option to use or bypass the hooks is needed for commands that write to a rev-prop, but not applicable when writing to a txn-prop nor when reading any properties. The 'svn' program can also read/write rev-props, but it cannot access txn-props, and can't bypass the hooks. Note also that the commands for setting and querying locks are distributed between 'svnadmin' and 'svnlook' in a non-obvious way too. I mention this because locks are another of the three main sorts of user data in a repository, along with the versioned trees and rev-props. If we are going to make a decision about the user interface for reading and writing revprops, we might want to give some consideration to the UI for locks at the same time. - Julian
Re: Change prevprops in pre-commit
On 09/08/2014 09:26 AM, Philip Martin wrote: > Sergey Azarkevich writes: > >> I see in pre-commit hook template that changing revisions properties in >> transaction are allowed. >> But I can't find way for it (I want change svn:author to more readable). >> >> Is here way for this with svn, svnadmin, svnlook ... or other standard >> tool? Or I should use Subversion API and write simple tool? > I think we should provide command line support for setting txnprops. > The code is simple enough, the iterface is a bit harder. There was was > some debate on IRC as to whether it should be > >svnlook propset -t txn > > or > >svnadmin settxnprop -t txn Why not just 'svnadmin setrevprop -t txn' ? New option, but not a new subcommand. I don't think it all that important to distinguish between "transaction props" and "revision props" once we get outside our API space and into user command space. Our users understand "revision props" as properties on revisions, and transactions as revisions-to-be ... the rest is fairly trivial inference. (And yes, 'svnlook' should be kept read-only.) -- C. Michael Pilato CollabNet <> www.collab.net <> Enterprise Cloud Development
Assertion failed while updating a working copy
Hi, I looked at the mail archives and found the same issue posted a handful of times, but couldn't find a resolution. I tripped the Assert pasted below from TortoiseSVN 1.8.7 while I was updating my working copy. There were tree conflicts with the update (I had renamed a folder and modified some of the files in it, but the update had also made changes to the files). Now, I receive the same error when I use Tortoise to edit tree conflicts regardless of resolution. That is, I get the error when attempting "Apply the update to the move destination" as well as "Mark as resolved (the move will become a copy)". Any thoughts? --- Subversion Exception! --- Subversion encountered a serious problem. Please take the time to report this on the Subversion mailing list with as much information as possible about what you were trying to do. But please first search the mailing list archives for the error message to avoid reporting the same problem repeatedly. You can find the mailing list archives at http://subversion.apache.org/mailing-lists.html Subversion reported the following (you can copy the content of this dialog to the clipboard using Ctrl-C): In file 'D:\Development\SVN\Releases\TortoiseSVN-1.8.7\ext\subversion\subversion\libsvn_wc\wc_db_update_move.c' line 1039: assertion failed (move_dst_revision == expected_move_dst_revision || status == svn_wc__db_status_not_present) --- OK ---
http://svnbook.red-bean.com/ site
Hi, http://svnbook.red-bean.com/ is no longer working. It says "This domain is pending WHOIS verification." Is this something easy to fix? Regards Pete
Re: http://svnbook.red-bean.com/ site
On Sep 8, 2014, at 8:49 AM, Peter Hitchman wrote: > Hi, > http://svnbook.red-bean.com/ is no longer working. > It says "This domain is pending WHOIS verification." > > Is this something easy to fix? > > Regards > Pete It's fine in my part of the Internet. Maybe your ISP didn't pay their electric bill.
Re: http://svnbook.red-bean.com/ site
I see this problem too. I use the Google DNS servers. Weird how there is a joker.com banner on the page as well. Mark > On Sep 8, 2014, at 11:57 AM, jbl...@icloud.com wrote: > >> On Sep 8, 2014, at 8:49 AM, Peter Hitchman wrote: >> >> Hi, >> http://svnbook.red-bean.com/ is no longer working. >> It says "This domain is pending WHOIS verification." >> >> Is this something easy to fix? >> >> Regards >> Pete > > > It's fine in my part of the Internet. Maybe your ISP didn't pay their > electric bill. > >
Re: Change prevprops in pre-commit
"C. Michael Pilato" writes: > Why not just 'svnadmin setrevprop -t txn' ? New option, but not a new > subcommand. I don't think it all that important to distinguish between > "transaction props" and "revision props" once we get outside our API > space and into user command space. Our users understand "revision > props" as properties on revisions, and transactions as revisions-to-be > ... the rest is fairly trivial inference. I was concerned that two thing: combining --transaction with set*rev*prop, and the --use-pre/post options that do not apply to --transaction. However "svnlook propget" already combines --revprop with --transaction and we can error out if --transaction is combined with --use-pre/post. > (And yes, 'svnlook' should be kept read-only.) I prefer an svnadmin solution as well. -- Philip Martin | Subversion Committer WANdisco // *Non-Stop Data*
global ignores
Hello I am trying to get subversion to ignore certain files and directories on a windows system. I am using a windows 7 machine with a 1.7 subversion client. My repository has about 40 projects in it and I want to ignore bin and obj directories along with *.sou and *.user files. I seemed like it was working but it is acting strangely. I just recently rebuilt my machine, but a project I added prior to the rebuild is only half correct, the folders are being ignored but not the files. The files are stored on a network drive and I issued svn proplist -R and do not see any ignores in the list. I saw somewhere that I can edit the config file in this folder C:\Documents and Settings\[username]\Application Data\Subversion, but this directory is inaccessible. I went to %Appdata% and found a config file there. So I tried to edit it, however I can find no information on how to properly edit it. I saw # global-ignores = *.o *.lo *.la *.al .libs *.so *.so.[0-9]* *.a *.pyc *.pyo I tried # global-ignores = *.o *.lo *.la *.al .libs *.so *.so.[0-9]* *.a *.pyc *.pyo *.sou And # global-ignores = *.o *.lo *.la *.al .libs *.so *.so.[0-9]* *.a *.pyc *.pyo global-ignores = *.sou But everytime I issue a svn status I still see the files. I do not know if status ignores the ignore list and it is just for committing or if I am editing the right file. Nor do I know if a reboot is needed before the changes take effect, I tried that once but I can be here for hours with all the unknowns. Anyone have any idea? JM
Re: global ignores
On Mon, Sep 8, 2014 at 12:37 PM, John Maher wrote: > Hello > > > > I am trying to get subversion to ignore certain files and directories on a > windows system. I am using a windows 7 machine with a 1.7 subversion > client. My repository has about 40 projects in it and I want to ignore bin > and obj directories along with *.sou and *.user files. I seemed like it > was working but it is acting strangely. I just recently rebuilt my > machine, but a project I added prior to the rebuild is only half correct, > the folders are being ignored but not the files. The files are stored on a > network drive and I issued svn proplist –R and do not see any ignores in > the list. I saw somewhere that I can edit the config file in this folder > C:\Documents and Settings\[username]\Application Data\Subversion, but this > directory is inaccessible. I went to %Appdata% and found a config file > there. So I tried to edit it, however I can find no information on how to > properly edit it. > > > > I saw > > # global-ignores = *.o *.lo *.la *.al .libs *.so *.so.[0-9]* *.a *.pyc > *.pyo > > I tried > > # global-ignores = *.o *.lo *.la *.al .libs *.so *.so.[0-9]* *.a *.pyc > *.pyo *.sou > > And > > # global-ignores = *.o *.lo *.la *.al .libs *.so *.so.[0-9]* *.a *.pyc > *.pyo > > global-ignores = *.sou > > > > But everytime I issue a svn status I still see the files. I do not know > if status ignores the ignore list and it is just for committing or if I am > editing the right file. Nor do I know if a reboot is needed before the > changes take effect, I tried that once but I can be here for hours with all > the unknowns. Anyone have any idea? > > Are the files showing as unversioned or modfied? Ignores only apply to unversioned files. If the file is already part of your repository and has local modifications, there is no option in SVN to ignore those files. -- Thanks Mark Phippard http://markphip.blogspot.com/
Re: global ignores
On Mon, Sep 8, 2014 at 12:47 PM, John Maher wrote: > Thanks for the reply Mark. For the new project they became versioned, > but not the projects prior to that. They all show up with the status > command with a ? in front except the two from the latest project. Before I > remove the two offending files (or delete, I do not know which is better) I > would prefer to ensure they are properly ignored otherwise I will be going > through this again. > Adding users@ A ? would indicate the files are in fact unversioned which means they could be ignored. So I guess I would look closer at your configuration to see why they are not being ignored. -- Thanks Mark Phippard http://markphip.blogspot.com/
Re: global ignores
Please keep users@ involved. On Mon, Sep 8, 2014 at 1:07 PM, John Maher wrote: > Thanks Mark. Could you be a little more specific? Like look at what > and where. I’ve been looking at all kinds of stuff and reading many, many > posts but nothing is clear. > I do not have any specific suggestion, just that if you see a ? then that means the file should be ignorable if the settings are right. > > > For example, what is a comment in the config file. Many places it talks > about comments but nowhere does it explain what a comment is. I see lines > starting with # and lines starting with ###. Are all of those comments or > just the ###? It is clear that the lines with ### are comments but is > subversion reading the lines with # or are they comments also? > Any line that starts with # is a comment. On Windows, open the Run dialog and enter %APPDATA%\Subversion and press ENTER. Then edit the file named "config" with a text editor. The default value for this option is: [miscellany] ### Set global-ignores to a set of whitespace-delimited globs ### which Subversion will ignore in its 'status' output, and ### while importing or adding files and directories. global-ignores = *.o *.lo *.la #*# .*.rej *.rej .*~ *~ .#* .DS_Store Make sure your text editor does not change the filename or save it with a file extension added. If you are using TortoiseSVN, I recall their Settings dialog also provides access to this. -- Thanks Mark Phippard http://markphip.blogspot.com/
RE: global ignores
Thanks Mark, that did it. JM From: Mark Phippard [mailto:markp...@gmail.com] Sent: Monday, September 08, 2014 1:18 PM To: John Maher; users@subversion.apache.org Subject: Re: global ignores Please keep users@ involved. On Mon, Sep 8, 2014 at 1:07 PM, John Maher mailto:jo...@rotair.com>> wrote: Thanks Mark. Could you be a little more specific? Like look at what and where. I’ve been looking at all kinds of stuff and reading many, many posts but nothing is clear. I do not have any specific suggestion, just that if you see a ? then that means the file should be ignorable if the settings are right. For example, what is a comment in the config file. Many places it talks about comments but nowhere does it explain what a comment is. I see lines starting with # and lines starting with ###. Are all of those comments or just the ###? It is clear that the lines with ### are comments but is subversion reading the lines with # or are they comments also? Any line that starts with # is a comment. On Windows, open the Run dialog and enter %APPDATA%\Subversion and press ENTER. Then edit the file named "config" with a text editor. The default value for this option is: [miscellany] ### Set global-ignores to a set of whitespace-delimited globs ### which Subversion will ignore in its 'status' output, and ### while importing or adding files and directories. global-ignores = *.o *.lo *.la #*# .*.rej *.rej .*~ *~ .#* .DS_Store Make sure your text editor does not change the filename or save it with a file extension added. If you are using TortoiseSVN, I recall their Settings dialog also provides access to this. -- Thanks Mark Phippard http://markphip.blogspot.com/
