Outlook macro for proper quoting (was RE: Problem with adding files in SVN 1.8.0+. Is it in the tracker already?)
-Original Message- From: Geoff Field [mailto:geoff_fi...@aapl.com.au] Sent: Wednesday, September 25, 2013 7:27 PM To: Bert Huijben; 'JANIKOVIC Jan'; users@subversion.apache.org Subject: RE: Problem with adding files in SVN 1.8.0+. Is it in the tracker already? Hi Bert, From: Bert Huijben [mailto:b...@qqmail.nl] Sent: Wednesday, 25 September 2013 21:04 PM To: Geoff Field; 'JANIKOVIC Jan'; users@subversion.apache.org Subject: RE: Problem with adding files in SVN 1.8.0+. Is it in the tracker already? I'll just reply in the html form as it will be very hard to convert this thread to plain ascii and I have better things to do than spending half an hour on that. As much as Outlook (and I know you're using Outlook because the headers of your message include X-Mailer: Microsoft Outlook 15.0) is a sub- optimal tool for traditional groups, it's not that hard to change the Format selection from HTML to Plain Text. The real problem/pain is that you then have to reformat the message to make sense in plain-text format. I haven't done much to this message and it's a bit of a mess. For those suffering from the embarrassment of posting with Outlook clients: QuoteFix Macro at http://sourceforge.net/apps/mediawiki/macros4outlook/index.php?title=QuoteFix_Macro#Configuration
Recommendation for path-based authorisation auditing tool?
Hi We use path-based authorisation to control access to our svn repositories. The authorisation rules can be quite complex as we apply different authorisations across various branches and directories of our projects. It is quite hard to be sure that the required permissions structure is correctly implemented. Therefore, we are looking for a tool to help audit the permissions. I am aware that there are various commercial tools available. The ones I have seen are part of larger svn tool suites and not available separately. They are therefore expensive. I am wondering whether anyone would recommend a suitable tool for controlling or auditing path-based permissions? Best regards David
Re: Recommendation for path-based authorisation auditing tool?
On Thu, Sep 26, 2013 at 10:50 AM, David Aldrich david.aldr...@emea.nec.comwrote: We use path-based authorisation to control access to our svn repositories. The authorisation rules can be quite complex as we apply different authorisations across various branches and directories of our projects. It is quite hard to be sure that the required permissions structure is correctly implemented. ** ** ** Therefore, we are looking for a tool to help audit the permissions. I am aware that there are various commercial tools available. The ones I have seen are part of larger svn tool suites and not available separately. They are therefore expensive. ** ** I am wondering whether anyone would recommend a suitable tool for controlling or auditing path-based permissions? -- Define what you mean by auditing? I am not aware of any commercial tools that do this. There are certainly tools that provide their own UI for defining the permissions and probably leave an audit trail of who made the changes, but that does not seem like what you want. With SVN 1.8 you can store the authz files in the repository -- so that would give an audit trail. Also, there is a command line tool that can be used to validate the file as well as run checks on the rules. See: http://subversion.apache.org/docs/release-notes/1.8.html#svnauthz_accessof Thanks Mark Phippard http://markphip.blogspot.com/
RE: Recommendation for path-based authorisation auditing tool?
Hi Mark Thanks for replying. By auditing, I mean the ability to easily see who has access to a specified folder. I think we already have the recording of changes covered. svnauthz_accessof looks interesting, but it reports whether a specified user has access. I would prefer to ask 'who has access?' to a specified folder. David From: Mark Phippard [mailto:markp...@gmail.com] Sent: 26 September 2013 15:56 To: David Aldrich Cc: 'users@subversion.apache.org' (users@subversion.apache.org) Subject: Re: Recommendation for path-based authorisation auditing tool? On Thu, Sep 26, 2013 at 10:50 AM, David Aldrich david.aldr...@emea.nec.commailto:david.aldr...@emea.nec.com wrote: We use path-based authorisation to control access to our svn repositories. The authorisation rules can be quite complex as we apply different authorisations across various branches and directories of our projects. It is quite hard to be sure that the required permissions structure is correctly implemented. Therefore, we are looking for a tool to help audit the permissions. I am aware that there are various commercial tools available. The ones I have seen are part of larger svn tool suites and not available separately. They are therefore expensive. I am wondering whether anyone would recommend a suitable tool for controlling or auditing path-based permissions? -- Define what you mean by auditing? I am not aware of any commercial tools that do this. There are certainly tools that provide their own UI for defining the permissions and probably leave an audit trail of who made the changes, but that does not seem like what you want. With SVN 1.8 you can store the authz files in the repository -- so that would give an audit trail. Also, there is a command line tool that can be used to validate the file as well as run checks on the rules. See: http://subversion.apache.org/docs/release-notes/1.8.html#svnauthz_accessof Thanks Mark Phippard http://markphip.blogspot.com/ Click herehttps://www.mailcontrol.com/sr/V0PBIBeSTzjGX2PQPOmvUgItITKVa7z0Xk0fQOMfCUIfDOMoOhGZTkGhdk3mmYAyB08qPzQHNPJIWrzEXY2ZCw== to report this email as spam.
Re: Recommendation for path-based authorisation auditing tool?
On Thu, Sep 26, 2013 at 11:02 AM, David Aldrich david.aldr...@emea.nec.comwrote: Hi Mark ** ** Thanks for replying. By auditing, I mean the ability to easily see who has access to a specified folder. I think we already have the recording of changes covered. svnauthz_accessof looks interesting, but it reports whether a specified user has access. I would prefer to ask ‘who has access?’ to a specified folder. ** OK. I am not aware of any tools commercial or otherwise that provide the information that way. If you use groups and have a finite number of them, it seems like it would be a fairly simple script to check each group against the path using the command line tool and report which ones have access. -- Thanks Mark Phippard http://markphip.blogspot.com/
RE: Recommendation for path-based authorisation auditing tool?
Hi Mark Thanks, that's a very helpful suggestion. Best regards David From: Mark Phippard [mailto:markp...@gmail.com] Sent: 26 September 2013 16:06 To: David Aldrich Cc: 'users@subversion.apache.org' (users@subversion.apache.org) Subject: Re: Recommendation for path-based authorisation auditing tool? On Thu, Sep 26, 2013 at 11:02 AM, David Aldrich david.aldr...@emea.nec.commailto:david.aldr...@emea.nec.com wrote: Hi Mark Thanks for replying. By auditing, I mean the ability to easily see who has access to a specified folder. I think we already have the recording of changes covered. svnauthz_accessof looks interesting, but it reports whether a specified user has access. I would prefer to ask 'who has access?' to a specified folder. OK. I am not aware of any tools commercial or otherwise that provide the information that way. If you use groups and have a finite number of them, it seems like it would be a fairly simple script to check each group against the path using the command line tool and report which ones have access. -- Thanks Mark Phippard http://markphip.blogspot.com/ Click herehttps://www.mailcontrol.com/sr/D8nXeCAIogfGX2PQPOmvUiQSa3+T5MHvHfzOz+TEk5kDT59leSYV069gQeHxHhY7B08qPzQHNPIAXoNDtAu6BA== to report this email as spam.
Re: subversion load fails with “no such revision”
An FYI to all, I'm back trying to deal with this migration, and it's still a giant mess. The consistent problem seem to be that revision numbering is just flat wrong when files were renamed in a revision. I'm fixing svnadmin load errors one-at-a-time by the following process: 1. Find in the dump file the add that's breaking. Note that there is a Node-copyfrom-rev that refers to a revision that doesn't exist in the filtered file (and is irrelevant in the pre-filtered file); that is, the revision number is incorrect. Also note that the svnadmin load error message refers to a third revision number that has nothing to do with the problem either -- it's NOT the number in the Node-copyfrom-rev. 2. Find the first previous revisionof that file that was a change. Note the correct revision number. 3. Return to the add that's breaking and manually change the revision number to refer to that commit. 4. Wipe the repo and restart. Go back to step 1. I'm doing the load with svnadmin 1.7.13, but the dump was from svnadmin 1.6.6. Upgrading the latter is not an option, which is why we're moving and splitting the repo. On Fri, Aug 30, 2013 at 2:03 PM, Harlan Harris har...@harris.name wrote: Tony, I used the seemingly-standard version of dumpfilter, not the 2 or 3 versions. But then I also did the search/replace trick that others had suggested to shift paths around. I don't think that's the issue, but I'm not sure. Thorsten, I wish it was just a bit of web application stuff, but it's actually a 5-year-old enterprise repo that was horribly abused, including checkins of very large binary and data files. The dump file of the whole thing is about 25 GB in size. That's part of why I want to split it up and filtering things out. I'm going to try just exporting the last month worth of revisions, and see if that works better. We may have to sacrifice most history in the interest of actually getting this working. -Harlan On Fri, Aug 30, 2013 at 11:41 AM, Thorsten Schöning tschoen...@am-soft.de wrote: Guten Tag Harlan Harris, am Freitag, 30. August 2013 um 17:10 schrieben Sie: I guess disk space is cheap now...! It's especially cheaper than your time if you only need to version a bit of web application stuff and, depending on the version of your old repos, newer repos may even reduce disk space because of representation sharing and some improvements in storing directory structures in Subversion 1.8. 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
Re: subversion load fails with “no such revision”
Hi, On Thu, Sep 26, 2013 at 12:18:30PM -0400, Harlan Harris wrote: An FYI to all, I'm back trying to deal with this migration, and it's still a giant mess. The consistent problem seem to be that revision numbering is just flat wrong when files were renamed in a revision. I'm fixing svnadmin load errors one-at-a-time by the following process: 1. Find in the dump file the add that's breaking. Note that there is a Node-copyfrom-rev that refers to a�revision�that doesn't exist in the filtered file (and is irrelevant in the pre-filtered file); that is, the revision number is incorrect. Also note that the svnadmin load error message refers to a third revision number that has nothing to do with the problem either -- it's NOT the number in the Node-copyfrom-rev.� I'm not entirely convinced that manual corrections are the way to go. From the sounds of it, this is a painfully huge effort for you, with considerable complications. IOW: ouch. So, AFAICS (you hinted at that) these dumps were split out via svndumpfilter. What about tending towards trying to fix the suspected root cause (problematic algorithms in svndumpfilter) rather than huge manual efforts of trying to fix each such broken rename case? I don't know how difficult/challenging it would be to try to fix svndumpfilter algorithms to correctly handle/take into account such renames (I don't have any experience with svndumpfilter), but to me it sounds like this would be much more lucrative. If one managed to do some investigations about the differences between the 4 different svndumpfilter offsprings and codify this into a nice well-manageable upstream project (SourceForge, github, ...) while fixing the revisions-with-renames issues, then this would be a huge win AFAICS. I'm trying to teach the TFS Plain-Original-Software some new SVN tricks, so I know that there's quite some effort required to achieve proper SCM handling, but fixing one isolated issue (let's hope it's only one issue...) hopefully wouldn't be too hard (in the TFS support case there were many low-hanging fruits, too). Or try to ask someone to have a look at what would be required to get these svndumpfilter issues improved... HTH, Andreas Mohr
Re: encoding issue with ruby binding
Hi,
On Wed, Sep 25, 2013 at 11:20:58AM +0200, Stephane D'Alu wrote:
Version:
Subversion: 1.8.3
Ruby: 2.0.0.195
Error message:
/usr/local/lib/ruby/site_ruby/2.0/svn/info.rb:236:in `===': invalid byte
sequence in US-ASCII (ArgumentError)
It occurs in the parse_diff_unified methods when trying to mach lines
of entry.body
How to repeat:
Having an UTF-8 encoded character in a committed file
It may not be a solution in its entirety or even overly helpful,
but for reference here's some code fragment that I created
to handle such issues in vcproj2cmake
(in this case in filenames, as opposed to file content,
but that does not matter):
# RUBY VERSION COMPAT STUFF
if (RUBY_VERSION '1.9') # FIXME exact version where it got introduced?
def rc_string_start_with(candidate, str_start)
nil != candidate.match(/^#{str_start}/)
end
else
def rc_string_start_with(candidate, str_start)
candidate.start_with?(str_start) # SYNTAX_CHECK_WHITELIST
end
end
module V2C_Ruby_Compat
alias string_start_with rc_string_start_with
module_function :string_start_with
end
# Guards against exceptions due to encountering mismatching-encoding entries
# within the directory.
def dir_entries_grep_skip_broken(dir_entries, regex)
dir_entries.grep(regex)
rescue ArgumentError = e
if not V2C_Ruby_Compat::string_start_with(e.message, 'invalid byte sequence')
raise
end
# Hrmpf, *some* entry failed. Rescue operations,
# by going through each entry manually and logging/skipping broken ones.
array_collect_compact(dir_entries) do |entry|
result = nil
begin
if not regex.match(entry).nil?
result = entry
end
rescue ArgumentError = e
if V2C_Ruby_Compat::string_start_with(e.message, 'invalid byte sequence')
log_error Dir entry #{entry} has invalid (foreign?) encoding
(#{e.message}), skipping!
result = nil
else
raise
end
end
result
end
end
Stephane D'Alu -- Ingenieur Recherche
Laboratoire CITI / INSA-Lyon
Lyon is nice for vacations :-)
Andreas Mohr
RE: Outlook macro for proper quoting (was RE: Problem with adding files in SVN 1.8.0+. Is it in the tracker already?)
From: Andrew Reedick From: Geoff Field Sent: Wednesday, September 25, 2013 7:27 PM Hi Bert, From: Bert Huijben Sent: Wednesday, 25 September 2013 21:04 PM I'll just reply in the html form as it will be very hard to convert this thread to plain ascii and I have better things to do than spending half an hour on that. As much as Outlook (and I know you're using Outlook because the headers of your message include X-Mailer: Microsoft Outlook 15.0) is a sub- optimal tool for traditional groups, it's not that hard to change the Format selection from HTML to Plain Text. The real problem/pain is that you then have to reformat the message to make sense in plain-text format. I haven't done much to this message and it's a bit of a mess. For those suffering from the embarrassment of posting with Outlook clients: QuoteFix Macro at http://sourceforge.net/apps/mediawiki/macros4outlook/index.php?title=QuoteFix_Macro#Configuration Thanks Andrew, I've found that with a very small effort and a little manual configuration, I can produce a reasonably formatted post without upsetting the modern conventions used by most of the others within our business. Having said that, I've applied QuoteFix on my Outlook Express at home (some time in the past). I'm reluctant to apply it on my work computers, though - if our firewall even allows downloads from SourceForge (it's a bit fussy in some very odd ways). Regards, Geoff -- Apologies for the auto-generated legal boilerplate added by our IT department: - The contents of this email, and any attachments, are strictly private and confidential. - It may contain legally privileged or sensitive information and is intended solely for the individual or entity to which it is addressed. - Only the intended recipient may review, reproduce, retransmit, disclose, disseminate or otherwise use or take action in reliance upon the information contained in this email and any attachments, with the permission of Australian Arrow Pty. Ltd. - If you have received this communication in error, please reply to the sender immediately and promptly delete the email and attachments, together with any copies, from all computers. - It is your responsibility to scan this communication and any attached files for computer viruses and other defects and we recommend that it be subjected to your virus checking procedures prior to use. - Australian Arrow Pty. Ltd. does not accept liability for any loss or damage of any nature, howsoever caused, which may result directly or indirectly from this communication or any attached files.
Re: Commit ignoring whitespace changes
On 09/25/2013 11:37 PM, Ryan Schmidt wrote: On Sep 25, 2013, at 16:19, Zé jose.pas...@gmx.com wrote: Does subversion provide a way to commit all changes except those that affect only whitespaces? Nothing built in for that, no. I recommend whitespace changes be a separate commit from functional changes. But it's up to the developers to do that. The tool doesn't do it for you. Bummer. It's a shame and a nuissance that subversion can ignore whitespaces on svn diff but not on commit. Zé
RE: Recommendation for path-based authorisation auditing tool?
Hi David, I hate to sound like I'm stating the bleeding obvious, but what about just looking at the authz file with a text editor? It's not hard to interpret if your usernames are sensible. I've recently spent a little while making sure the projects are sorted in a sensible order, so finding particular projects is quite easy (apart from just using the built-in search functions). Having said that, we use a home-grown tool (written by a long-gone colleague in C# and backed by an SQL database for administration items) for some network administration tasks. Mostly, this is useful as a lazy way of adding or deleting projects. I still use the text editor for modifying user permissions (because it's faster and easier). Regards, Geoff From: David Aldrich Sent: Friday, 27 September 2013 1:08 AM Hi Mark Thanks, that's a very helpful suggestion. Best regards David From: Mark Phippard Sent: 26 September 2013 16:06 On Thu, Sep 26, 2013 at 11:02 AM, David Aldrich wrote: Hi Mark Thanks for replying. By auditing, I mean the ability to easily see who has access to a specified folder. I think we already have the recording of changes covered. svnauthz_accessof looks interesting, but it reports whether a specified user has access. I would prefer to ask 'who has access?' to a specified folder. OK. I am not aware of any tools commercial or otherwise that provide the information that way. If you use groups and have a finite number of them, it seems like it would be a fairly simple script to check each group against the path using the command line tool and report which ones have access. -- Thanks Mark Phippard http://markphip.blogspot.com/ -- Apologies for the auto-generated legal boilerplate added by our IT department: - The contents of this email, and any attachments, are strictly private and confidential. - It may contain legally privileged or sensitive information and is intended solely for the individual or entity to which it is addressed. - Only the intended recipient may review, reproduce, retransmit, disclose, disseminate or otherwise use or take action in reliance upon the information contained in this email and any attachments, with the permission of Australian Arrow Pty. Ltd. - If you have received this communication in error, please reply to the sender immediately and promptly delete the email and attachments, together with any copies, from all computers. - It is your responsibility to scan this communication and any attached files for computer viruses and other defects and we recommend that it be subjected to your virus checking procedures prior to use. - Australian Arrow Pty. Ltd. does not accept liability for any loss or damage of any nature, howsoever caused, which may result directly or indirectly from this communication or any attached files.
