Re: Subversion Exception
Am 13.01.2012 20:49, schrieb George Xing: ...\TortoiseSVN-1.7.0\... Upgrade. Four newer bugfix releases were released since that one already. TSVN even features an update reminder, make sure to activate it. That said, please read the whole text, you omitted important steps to making a useful bug report. Good luck! Uli ** Domino Laser GmbH, Fangdieckstraße 75a, 22547 Hamburg, Deutschland Geschäftsführer: Thorsten Föcking, Amtsgericht Hamburg HR B62 932 ** Visit our website at http://www.dominolaser.com ** Diese E-Mail einschließlich sämtlicher Anhänge ist nur für den Adressaten bestimmt und kann vertrauliche Informationen enthalten. Bitte benachrichtigen Sie den Absender umgehend, falls Sie nicht der beabsichtigte Empfänger sein sollten. Die E-Mail ist in diesem Fall zu löschen und darf weder gelesen, weitergeleitet, veröffentlicht oder anderweitig benutzt werden. E-Mails können durch Dritte gelesen werden und Viren sowie nichtautorisierte Änderungen enthalten. Domino Laser GmbH ist für diese Folgen nicht verantwortlich. **
Re: Subversion Exception
Am 15.01.2012 14:18, schrieb 10287464: Hi, when I use TortoiseSvn with x64 to checkout a path like: http:/mobile-anarchy-widgets.googlecode.com/svn/trunk . I'd say that should be http://... instead of http:/..., but SVN shouldn't choke on that. Uli ** Domino Laser GmbH, Fangdieckstraße 75a, 22547 Hamburg, Deutschland Geschäftsführer: Thorsten Föcking, Amtsgericht Hamburg HR B62 932 ** Visit our website at http://www.dominolaser.com ** Diese E-Mail einschließlich sämtlicher Anhänge ist nur für den Adressaten bestimmt und kann vertrauliche Informationen enthalten. Bitte benachrichtigen Sie den Absender umgehend, falls Sie nicht der beabsichtigte Empfänger sein sollten. Die E-Mail ist in diesem Fall zu löschen und darf weder gelesen, weitergeleitet, veröffentlicht oder anderweitig benutzt werden. E-Mails können durch Dritte gelesen werden und Viren sowie nichtautorisierte Änderungen enthalten. Domino Laser GmbH ist für diese Folgen nicht verantwortlich. **
Subversion Exception
Hi, I saw that 1 image file differs from the copy on the server, so I clicked Revert and got this message. In file 'D:\Development\SVN\Releases\TortoiseSVN-1.7.3\ext\subversion\subversion\libsvn_wc\workqueue.c' line 673: assertion failed (checksum != NULL) I didn't have any problems on 1.7.1. Later it asked for Clean Up to be performed, but I got the same message. Kind Regards,
Sub Version Source Code
Hi, This is Manohar. I would like to work on sub version. So, can u please provide me the complete source code of sub version. Regards, MANOHAR MYLARAM SYSTEMS ENGINEER Infosys(r)| HYDERABAD SEZ CAUTION - Disclaimer * This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the use of the addressee(s). If you are not the intended recipient, please notify the sender by e-mail and delete the original message. Further, you are not to copy, disclose, or distribute this e-mail or its contents to any other person and any such actions are unlawful. This e-mail may contain viruses. Infosys has taken every reasonable precaution to minimize this risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. Infosys reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the Infosys e-mail system. ***INFOSYS End of Disclaimer INFOSYS***
svn 1.6.17 crashed
I was trying to reintegrate merge. svn crashes. In file subversion\libsvn_ra_neon\props.c function svn_ra_neon__do_stat has this code: /* easy out: */ svn_error_clear(err); *dirent = NULL; return SVN_NO_ERROR; so function return NO_ERROR, but dirent == NULL; In file subversion\libsvn_client\merge.c function ensure_all_missing_ranges_are_phantoms has this code: SVN_ERR(svn_ra_stat(target_ra_session, path, range-end, dirent, iterpool)); if (svn_merge_range_contains_rev(range, dirent-created_rev)) After svn_ra_stat we have no errors, but dirent == NULL and during call to svn_merge_range_contains_rev dirent-created_rev causes access violation C:\svn-win32-1.6.17\binsvn --version svn, version 1.6.17 (r1128011) compiled Jun 2 2011, 23:35:08 Copyright (C) 2000-2009 CollabNet. Subversion is open source software, see http://subversion.apache.org/ This product includes software developed by CollabNet ( http://www.Collab.Net/). -- С уважением, Игорь ise...@gmail.com
Re: Sub Version Source Code
http://subversion.apache.org/packages.html Just google for Apache Subversion and choose your flavor. On Jan 16, 2012, at 3:28 AM, Manohar Mylaram wrote: Hi, This is Manohar. I would like to work on sub version. So, can u please provide me the complete source code of sub version. Regards, MANOHAR MYLARAM SYSTEMS ENGINEER Infosys®| HYDERABAD SEZ CAUTION - Disclaimer * This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the use of the addressee(s). If you are not the intended recipient, please notify the sender by e-mail and delete the original message. Further, you are not to copy, disclose, or distribute this e-mail or its contents to any other person and any such actions are unlawful. This e-mail may contain viruses. Infosys has taken every reasonable precaution to minimize this risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. Infosys reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the Infosys e-mail system. ***INFOSYS End of Disclaimer INFOSYS***
Re: Subversion Exception
Hi, Am 16.01.2012 09:05, schrieb Ulrich Eckhardt: Am 15.01.2012 14:18, schrieb 10287464: Hi, when I use TortoiseSvn with x64 to checkout a path like: http:/mobile-anarchy-widgets.googlecode.com/svn/trunk . I'd say that should be http://... instead of http:/..., but SVN shouldn't choke on that. Indeed using this syntax does crash TortoiseSVN, confirmed with 1.7.4. 10287464, please take the time to report this on the TortoiseSVN mailing list: us...@tortoisesvn.tigris.org -- Michael Geisinger
svn rm painfully slow with 1.7.2 and many files
Hi, I have a local working copy with some files and directories: # find . | wc -l 1255817 wc.db is currently 1.1 GiB: # du -hsA wc.db 1.1Gwc.db I've started an svn rm * in one directory and after 20 minutes it's still running. The directory is not quite large, it contains 153 small text files. Measuring the time between each D file name svn print I get 10 seconds. So it takes 10 seconds to remove a file. Top says 100% CPU usage: PID USERNAMETHR PRI NICE SIZERES STATE C TIME WCPU COMMAND 11048 root 1 1030 74052K 7424K CPU55 11:55 100.00% svn and the system doesn't touch the disks, wc.db is in the memory cache. The system is FreeBSD. I've found some options to sqlite (secure erase, default turned on, stat3, and memtable, turned off), which I flipped, so now I can remove a file in just 6 seconds. :) Is it possible somehow to speed that up? Sometimes I remove hundreds of files, which takes ages. Thanks, ps: is there a debug mode to subversion, so it would print out its SQL commands?
Re: Subversion Exception
On Jan 16, 2012, at 6:18 AM, Sidewinder wrote: Am 16.01.2012 09:05, schrieb Ulrich Eckhardt: I'd say that should be http://... instead of http:/..., but SVN shouldn't choke on that. Indeed using this syntax does crash TortoiseSVN, confirmed with 1.7.4. 10287464, please take the time to report this on the TortoiseSVN mailing list: us...@tortoisesvn.tigris.org Actually, the error message specifically states that it should be reported to the Subversion mailing list--it's an assertion failure in the SVN library. -- Name: Dave Huang | Mammal, mammal / their names are called / INet: k...@azeotrope.org | they raise a paw / the bat, the cat / FurryMUCK: Dahan | dolphin and dog / koala bear and hog -- TMBG Dahan: Hani G Y+C 36 Y++ L+++ W- C++ T++ A+ E+ S++ V++ F- Q+++ P+ B+ PA+ PL++
bi-directional merging?
Hi! I have a few questions regarding a particular subversion usage scenario. We are two teams, each working on more or less unrelated portions of a common code base. To isolate each team from stability issues introduced due to the work of the other team, we consider creating a separate branch for each team. Whenever one team considers its work to be stable (after a few weeks), it is reintegrated into the trunk, from where it can be picked up by the other team. However, there are also cases when changes need to be synchronized more quickly (e.g., critical bug fixes). This could be done by merging individual revisions of one branch back into the trunk, but since this workflow is different from the proposals discussed in http://svnbook.red-bean.com/en/1.7/svn.branchmerge.commonpatterns.html, I'm not sure about its consequences. So my questions are: *) Will it cause troubles (in terms of merge conflicts, performance, etc.) to perform bi-directional merging between the trunk and a branch created from the trunk (i.e., alternately merge changes from the trunk into the branch and from the branch into the trunk)? *) Will it cause troubles to perform a reintegration of the branch after some of the changes in the branch have already been merged into the trunk individually? *) Is there a different best-practice recommendation to achieve the isolation of two development teams as sketched above? Thanks kind regards, Markus Dipl.- Ing. Dr. techn. Markus Grabner Research Development Team phone +43 (0) 316 4000 761 fax +43 (0) 316 4000 711 www.alicona.com Alicona Imaging GmbH - Optical 3D measurement and inspection - Teslastraße 8 - 8074 Grambach/Graz - Austria Registered office: Grambach, FN 208097a, Landesgericht für ZRS Graz / This e-mail may contain privileged and/or confidential information. If you receive this email in error or are not the intended recipient, you may not use, copy, disseminate or distribute it. Do not open any attachments, delete it immediately from your system and notify the sender promptly by email that you have done so.
Re: bi-directional merging?
On 16/01/12 16:08, Grabner Markus wrote: Hi! I have a few questions regarding a particular subversion usage scenario. We are two teams, each working on more or less unrelated portions of a common code base. To isolate each team from stability issues introduced due to the work of the other team, we consider creating a separate branch for each team. Whenever one team considers its work to be stable (after a few weeks), it is reintegrated into the trunk, from where it can be picked up by the other team. However, there are also cases when changes need to be synchronized more quickly (e.g., critical bug fixes). This could be done by merging individual revisions of one branch back into the trunk, but since this workflow is different from the proposals discussed in http://svnbook.red-bean.com/en/1.7/svn.branchmerge.commonpatterns.html, I'm not sure about its consequences. So my questions are: *) Will it cause troubles (in terms of merge conflicts, performance, etc.) to perform bi-directional merging between the trunk and a branch created from the trunk (i.e., alternately merge changes from the trunk into the branch and from the branch into the trunk)? *) Will it cause troubles to perform a reintegration of the branch after some of the changes in the branch have already been merged into the trunk individually? *) Is there a different best-practice recommendation to achieve the isolation of two development teams as sketched above? Thanks kind regards, Markus Dipl.- Ing. Dr. techn. Markus Grabner Research Development Team phone +43 (0) 316 4000 761 fax +43 (0) 316 4000 711 www.alicona.com Alicona Imaging GmbH - Optical 3D measurement and inspection - Teslastraße 8 - 8074 Grambach/Graz - Austria Registered office: Grambach, FN 208097a, Landesgericht für ZRS Graz / This e-mail may contain privileged and/or confidential information. If you receive this email in error or are not the intended recipient, you may not use, copy, disseminate or distribute it. Do not open any attachments, delete it immediately from your system and notify the sender promptly by email that you have done so. If you're talking about critical bug fixes in trunk then I think I remember the recommended way would be to create a new branch for this fix, reintegrate to trunk, merge to the two development branches. Giulio
Documentation for svnserve based server setup out-of-date.
Hi. Svnserve based server related documentation as available on 'http://tortoisesvn.net/docs/nightly/TortoiseSVN_en/tsvn-serversetup-svnserve.html' seems to be out of date. The links there are now invalid. Also, CollabNet no longer packages a simple server distribution. Instead it now packages its Subversion Edge package which is quite large and, although it contains the necessary svnserve executable, is actually biased towards an Apache/HTTP based server setup. It can be used but then its default server first needs to be removed (services stopped) and a new svnserve based service set up manually. Hope this helps. Best regards, Jurko Gospodnetić
Re: Documentation for svnserve based server setup out-of-date.
On Mon, Jan 16, 2012 at 11:24 AM, Jurko Gospodnetić jurko.gospodne...@pke.hr wrote: Also, CollabNet no longer packages a simple server distribution. Instead it now packages its Subversion Edge package which is quite large and, although it contains the necessary svnserve executable, is actually biased towards an Apache/HTTP based server setup. It can be used but then its default server first needs to be removed (services stopped) and a new svnserve based service set up manually. CollabNet still provides the plain binaries package it always has. It is available here: http://www.open.collab.net/downloads/subversion/svn-other.html -- Thanks Mark Phippard http://markphip.blogspot.com/
Re: Documentation for svnserve based server setup out-of-date.
On Jan 16, 2012, at 10:24, Jurko Gospodnetić wrote: Svnserve based server related documentation as available on 'http://tortoisesvn.net/docs/nightly/TortoiseSVN_en/tsvn-serversetup-svnserve.html' seems to be out of date. You should report that problem to the TortoiseSVN mailing list, not here.
Re: bug: Subversion rejects property names
Garret Wilson wrote on Sun, Jan 15, 2012 at 18:33:32 -0800: Because Subversion over WebDAV (and Subversion in general) doesn't support namespace URIs in property names (see P.S.), I've created a system in which I encode URIs in property names. For example, here is one such property name: http·3a·2f·2fpurl.org·2fdc·2felements·2f1.1·2ftitle /** * Return @c TRUE iff @a prop_name is a valid property name. * * For now, valid means the ASCII subset of an XML Name. * XML Name is defined at http://www.w3.org/TR/REC-xml#sec-common-syn * * @since New in 1.5. */ svn_boolean_t svn_prop_name_is_valid(const char *prop_name); Use MIME Quoted-Printable? P.S. Note that the reason I had to encode the properties to begin with is because Subversion over WebDAV wasn't honoring the namespace I requested. I brought this up several times years ago, but no one replied. :( See e.g. http://svn.haxx.se/users/archive-2007-12/0640.shtml . Now Subversion is yet again fighting me, and I don't know why... If you have questions about WebDAV details of libsvn_ra's implementation, feel free to raise them on dev@.
Re: subversion sqlite.c bug
I finally recover my repository with svnadmin tool. I did dump, then load to new repository. But I can send anyone interested buggy repo (it's about 120 Mb)
Internal assertion when updating symlink changes on 64-bit Ubuntu 10.04 LTS
I admit I haven't updated my working copy on this Linux machine in some time, but I do know that we had some symlink changes in recent history that broke Subversion 1.7.0 on Windows with a similar assertion to the following. Upgrading to Subversion 1.7.2 on Windows fixed the assertion. However, now that I've gone to update on Linux, I get the following assertion: svn: E235000: In file 'subversion/libsvn_wc/update_editor.c' line 1583: assertion failed (action == svn_wc_conflict_action_edit || action == svn_wc_conflict_action_delete || action == svn_wc_conflict_action_replace) Deleting the directories containing the symlinks allows svn update to complete. Perhaps the above assertion is the same as http://mail-archives.apache.org/mod_mbox/subversion-dev/201201.mbox/%3c20120101235241.gb10...@ted.stsp.name%3E?
SVN 1.7 cannot add symlinks that reference a directory which is an svn external
Hi, We have the following issue: SVN cannot add symlinks that reference a directory which is an svn external. We have these directories in SVN inside a parent directory: DirectoryA DirectoryB Code_Framework Code_Framework has the svn:external property pointing to another location 1.2.3 http://svn/parent2/3partycode/1.2.3; We check out parent directory and add a symlink S1 to reference Code_Framework/1.2.3. This is fine. However, when we try to add S1, we get: svn: warning: W150002: '/Users/evanw/Projects/test/parent/1.2.3' is already under version control svn: E29: Could not add all targets because some targets are already versioned svn: E29: Illegal target for the requested operation When we try to check it in, we get: svn: E145001: Commit failed (details follow): svn: E145001: Entry '/Users/evanw/Projects/test/parent/1.2.3' has unexpectedly changed special status This operation works in SVN 1.6.x client, but not 1.7.2. We just upgraded to SVN 1.7.2 for our client and our server is still on 1.6.10. We are on a Mac platform. SVN was installed via MacPorts. Is this change intentional? Evan Wee [Build] Email/AIM: ev...@nationalfibre.net
AW: bi-directional merging?
-Ursprüngliche Nachricht- Von: Giulio Troccoli [mailto:giulio.trocc...@mediatelgroup.co.uk] Gesendet: Montag, 16. Jänner 2012 17:48 An: Grabner Markus Cc: Betreff: Re: bi-directional merging? On 16/01/12 16:08, Grabner Markus wrote: Hi! I have a few questions regarding a particular subversion usage scenario. We are two teams, each working on more or less unrelated portions of a common code base. To isolate each team from stability issues introduced due to the work of the other team, we consider creating a separate branch for each team. Whenever one team considers its work to be stable (after a few weeks), it is reintegrated into the trunk, from where it can be picked up by the other team. However, there are also cases when changes need to be synchronized more quickly (e.g., critical bug fixes). This could be done by merging individual revisions of one branch back into the trunk, but since this workflow is different from the proposals discussed in http://svnbook.red- bean.com/en/1.7/svn.branchmerge.commonpatterns.html, I'm not sure about its consequences. So my questions are: *) Will it cause troubles (in terms of merge conflicts, performance, etc.) to perform bi-directional merging between the trunk and a branch created from the trunk (i.e., alternately merge changes from the trunk into the branch and from the branch into the trunk)? *) Will it cause troubles to perform a reintegration of the branch after some of the changes in the branch have already been merged into the trunk individually? *) Is there a different best-practice recommendation to achieve the isolation of two development teams as sketched above? If you're talking about critical bug fixes in trunk then I think I remember the recommended way would be to create a new branch for this fix, reintegrate to trunk, merge to the two development branches. This would certainly work, but I was wondering if it is feasible to apply the convenient cherry-picking style of porting individual changes between trunk and branch in both directions (I probably have to take care of the mergeinfo, i.e., use svn merge --record-only). Can anybody please give advice on this? Thanks kind regards, Markus Dipl.- Ing. Dr. techn. Markus Grabner Research Development Team phone +43 (0) 316 4000 761 fax +43 (0) 316 4000 711 www.alicona.com Alicona Imaging GmbH - Optical 3D measurement and inspection - Teslastraße 8 - 8074 Grambach/Graz - Austria Registered office: Grambach, FN 208097a, Landesgericht für ZRS Graz / This e-mail may contain privileged and/or confidential information. If you receive this email in error or are not the intended recipient, you may not use, copy, disseminate or distribute it. Do not open any attachments, delete it immediately from your system and notify the sender promptly by email that you have done so.
Re: SVN 1.7 cannot add symlinks that reference a directory which is an svn external
On Jan 16, 2012, at 23:52 , Evan Wee wrote: Hi, We have the following issue: SVN cannot add symlinks that reference a directory which is an svn external. We have these directories in SVN inside a parent directory: DirectoryA DirectoryB Code_Framework Code_Framework has the svn:external property pointing to another location 1.2.3 http://svn/parent2/3partycode/1.2.3; We check out parent directory and add a symlink S1 to reference Code_Framework/1.2.3. This is fine. However, when we try to add S1, we get: svn: warning: W150002: '/Users/evanw/Projects/test/parent/1.2.3' is already under version control svn: E29: Could not add all targets because some targets are already versioned svn: E29: Illegal target for the requested operation When we try to check it in, we get: svn: E145001: Commit failed (details follow): svn: E145001: Entry '/Users/evanw/Projects/test/parent/1.2.3' has unexpectedly changed special status This operation works in SVN 1.6.x client, but not 1.7.2. We just upgraded to SVN 1.7.2 for our client and our server is still on 1.6.10. We are on a Mac platform. SVN was installed via MacPorts. Is this change intentional? No, it's a bug in 1.7.x. It looks like a variant of the recently reported issue #4091 error replacing executable with symlink. http://subversion.tigris.org/issues/show_bug.cgi?id=4091 Regards, Steve Evan Wee [Build] Email/AIM: ev...@nationalfibre.net -- Stephen Butler | Consultant elego Software Solutions GmbH Gustav-Meyer-Allee 25, 13355 Berlin, Germany tel: +49 30 2345 8696 | mobile: +49 163 25 45 015 fax: +49 30 2345 8695 | http://www.elego.de Geschäftsführer: Olaf Wagner | Sitz der Gesellschaft: Berlin Amtsgericht Charlottenburg HRB 77719
Re: Subversion Exception
On Jan 16, 2012, at 16:48 , Dave Huang wrote: On Jan 16, 2012, at 6:18 AM, Sidewinder wrote: Am 16.01.2012 09:05, schrieb Ulrich Eckhardt: I'd say that should be http://... instead of http:/..., but SVN shouldn't choke on that. Indeed using this syntax does crash TortoiseSVN, confirmed with 1.7.4. 10287464, please take the time to report this on the TortoiseSVN mailing list: us...@tortoisesvn.tigris.org Actually, the error message specifically states that it should be reported to the Subversion mailing list--it's an assertion failure in the SVN library. Correct. As discussed recently in a long email thread, http://svn.haxx.se/dev/archive-2011-12/0297.shtml this looks like one of those places where the Subversion libraries should return an error instead of aborting. I opened a Subversion issue for this bug: http://subversion.tigris.org/issues/show_bug.cgi?id=4099 Steve
