gmane.comp.version-control.subversion.tortoisesvn.user

Re: Downgrading Tortoise from 1.7 to 1.6

Andy Levy — 2012-05-25T14:21:13

On Fri, May 25, 2012 at 9:57 AM, Christian Brudevoll
<Christian.Brudevoll-w1+NB2m+WNgXWF+eFR7m5Q< at >public.gmane.org> wrote:

Once you have upgraded a WC to the 1.7 format, there is no going back.
You will have to check out fresh & copy your changes over.

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2965083

To unsubscribe from this discussion, e-mail: [users-unsubscribe< at >tortoisesvn.tigris.org].

Downgrading Tortoise from 1.7 to 1.6

Christian Brudevoll — 2012-05-25T13:57:00

I've upgraded Tortoise on my PC from 1.6 to 1.7.
Unfortunately, 1.7 doesn't work properly together with PowerBuilder.
When comparing with the checked in version, no differences are shown.
I've therefore tried to rollback to 1.6.
That was not so easy.
Removing 1.7 lead to error.
Repairing 1.6 didn't help, so reinstallation was necessary.

Now it seems as I've problems with the file structure.
Tortoise 1.6 isn't able to use the control files made by 1.7.
Anybody having any tips / ideas?

Will I have to do something like this?
1.      Checkout the Tortoise directories to a new directory on my PC
2.      Copy interesting files back, run diff and check in.

Christian Brudevoll

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2965078

To unsubscribe from this discussion, e-mail: [users-unsubscribe< at >tortoisesvn.tigris.org].

RE: Re: External diff tool ignored in some specific cases

Markus Humm — 2012-05-25T11:13:52

Hello,



Ok, but why can the check for modifications command then use WinMerge? 
This one obvisously not using this unified diff format. How does this come?




Hm? That sounds prety illogically in this case. How does it matter if 
I begin the process of compairing two versions (the revision and the wc)
with selecting the revision first and then the wc from first selecting the 
wc and then the revision? Isn't it like a+b = c and b+a = c?
If not it would not make any sense to me at all. Might be that it 
requires additonal logic on the displaying of that popum menu, but for us 
users this would create a more consistent user experience!

Greetings

Markus

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2965042

To unsubscribe from this discussion, e-mail: [users-unsubscribe-6zjzXkf2FExf8fUKLXF2/HdfcadvtA/q< at >public.gmane.org].

Re: External diff tool ignored in some specific cases

Stefan Küng — 2012-05-25T10:02:35

On Fri, May 25, 2012 at 10:38 AM, Markus Humm
<markus.humm-BHGg2g4QZrrWt40Fecq1Vw< at >public.gmane.org> wrote:

"compare with working copy" first creates a unified diff (patch) file,
and then uses TMerge to 'apply' that patch file in reverse to the
working copy.

Since TMerge is the only UI tool that can apply patch files (as far as
I know), TMerge is used unconditionally for this task.
WinMerge can not apply a patch file (the issue for such an enhancement
is open in their issue tracker for years).


Nope, not a bug. The first selected revision determines the action
since in case of multiple selected revs, that's the 'root' revision.

Stefan

External diff tool ignored in some specific cases

Markus Humm — 2012-05-25T08:38:30

Hello,

my colleagues found a issue with the definition of external diff programs today which I can reproduce. So it still exists in TortoiseSVN 1.7.7.

The issue is, that the external diff program defined (WinMerge in our case) is being used as expected for comparing two revisions past, but for comparing the working copy with a past revision Tortoise's diff program is being used. This happens from the graph as well as from the log dialogue.

The graph has an additional issue: depending on whether you've selected the working copy first and the other revision afterwards or vice versa the context menu has the view diff option or not. In my eyes that's a bug as well.

Has anybody hints for these two issues? Are they perhaps a bug? At least the behaviour is unexpected.

Greetings

Markus

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2965002

To unsubscribe from this discussion, e-mail: [users-unsubscribe-6zjzXkf2FExf8fUKLXF2/Hdf

RE: File contents not being index by windows 7 search

Stefano Brustia — 2012-05-25T07:56:00

This behavior is still present in version 1.7.7.
If I check out a project directories are flagged as to be indexed, files not.

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2964994

To unsubscribe from this discussion, e-mail: [users-unsubscribe-6zjzXkf2FExf8fUKLXF2/HdfcadvtA/q< at >public.gmane.org].

RE: Re: TSVN 1.7.7: Invalid storing bugtraq:logarex while using simplified dialog

Andriy Kvasnytsya — 2012-05-25T07:13:45

Hi Stefan,

Obviously, it is. But as far as I understand, it also supports one line mode - with only bug id regex. 
At least my experience (it was working before mentioned change, and after manual tweak - works after) and documentation at http://tortoisesvn.net/docs/release/TortoiseSVN_sk/tsvn-dug-bugtracker.html are proving that.

That's very nice that simplified UI allows user to modify settings without precisely picking complicated and unobvious property names. But if simple edit-ok (without any modifications) breaks things that had already worked, that's not very nice. Actually, it's frustrating, because I've spend half an hour trying to understand what's wrong with my regexes (pretty trivial, that makes attempt to find nonexisting bugs in them even harder), or did something changed in way how Tortoise SVN is handling them... Just to find out it stores regexes in different way than earlier, or actually tries to force me to use "officially recommened" way of using log regexes without actually telling me.

Re: "Commit Finished!" dialog not closeable via system menu or close button

Martin Bischoff — 2012-05-25T06:44:04

I can confirm this problem (on windows 7 64-bit). It also happens when
updating the working copy - the "Update Finished!" window cannot be closed
using the Close button in the upper right corner.

On Thu, May 24, 2012 at 11:26 AM, Kurt Pruenner <leak-RbZlAiThDcE< at >public.gmane.org> wrote:


------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2964986

To unsubscribe from this discussion, e-mail: [users-unsubscribe-6zjzXkf2FExf8fUKLXF2/HdfcadvtA/q< at >public.gmane.org].

Re: Problem report: can't dismiss "Update Finished!" dialog with close box

HamRusTal — 2012-05-24T19:34:31

I have exactly the same issue. In addition, the window doesn't close upon
either pressing AltF4 or choosing the “Close” command from its system menu.
When I send the WM_CLOSE message to the window, the result returned is 1
which means the message isn't handled properly. 
Francois Grieu-3 wrote:

Re: TSVN 1.7.7: Invalid storing bugtraq:logarex while using simplified dialog

Stefan Küng — 2012-05-24T16:19:41

The log regex *is* a two line string: the first line is the "message 
part expression" which must catch the whole bug expression, e.g. "issue 
#233". The second line then catches only the issue id itself, e.g., "233".

Stefan

TSVN 1.7.7: Invalid storing bugtraq:logarex while using simplified dialog

Andriy Kvasnytsya — 2012-05-24T11:20:48

What I did:

I was going to reconfigure JIRA integration in TortoiseSVN 1.7.7
I've opened trunk properties, double clicked bugtraq:logarex
Adjusted existing regular expression in form 
((?:MY_PROJECT_1|MY_PROJECT_2|...|MY_PROJECT_N)-\d+)
Clicked okay.

What I expected:
After opening log dialog afterward, column Bug-ID should have been 
filled with issue ids pulled from existing comments.

What happened:
Colum Bug-ID was present, but empty, all log entries had issue ids in it.

Future investigation showed that there was empty line added in property 
file (or whatever is it)
http://imageshack.us/f/13/201205241413.png/
Manual (Advanced) editing of property fixed this problem.

It seems that testing feature doesn't work too.

Re: version 1.7.7 Chinese, simplified Language packs install failed

Lübbe Onken — 2012-05-24T10:19:44

Hi,

you wrote:

2012/5/24 HH <hhsc2004< at >qq.com>


Sorry, I can't understand Chinese, this mailing list is English only. Have
your tried to download the language pack from a differnt sourceforge
mirror?

"Commit Finished!" dialog not closeable via system menu or close button

Kurt Pruenner — 2012-05-24T09:26:26

I just noticed the in the latest released version of TSVN (1.7.7) you
cannot close the commit result dialog (i.e. the one titled "Commit
Finished!") via either the window's close button or the "Close" item in
it's system menu.

I take it it's not meant to be closed while the operation is running,
but shouldn't you be able to close it in all the regular ways when the
operation is finished? Right now, you have to click the "OK" button to
dismiss it...

version 1.7.7 Chinese, simplified Language packs install failed

HH — 2012-05-24T02:54:22

Hi,
我在安装1.7.7版本的中文语言包时，安装了很多次都没法在设置中的语言选择项中看到 中文简体 选择项，我机器是 64位的，也是用的64位的安装包。但是我在安装繁体中文包时却一次性成功。


另外，我在安装简体语言包时，碰到了如下的错误，查了很多资料都没解决，麻烦查看一下是什么原因，在这个操作失败后，安装繁体中文包却很顺利，不知道是什么原因：

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2964733

To unsubscribe from this discussion, e-mail: [users-unsubscribe< at >tortoisesvn.tigris.org].

Re: Redirection of Upgrade Check

Todd Nelson — 2012-05-23T19:18:15

Thank you! :D

Re: tsvn 1.7.7 Show Log bugs

Gunnar Dalsnes — 2012-05-23T19:14:07

Thank you, and Konstantin for the diagnose.

Gunnar.

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2964669

To unsubscribe from this discussion, e-mail: [users-unsubscribe< at >tortoisesvn.tigris.org].

Re: Redirection of Upgrade Check

Stefan Küng — 2012-05-23T19:13:45

Also see
http://code.google.com/p/tortoisesvn/source/detail?r=22940
from two minutes ago :)

Stefan

Re: Redirection of Upgrade Check

Todd Nelson — 2012-05-23T19:12:05

I think we got things figured out.  In our text file our version number
matched the one installed and in that scenario the update will still point
to tortoisesvn.net.  We entered a test number of 2.7 and the link correctly
updated and pointed to our link.

Thanks for your quick responses and support.

-Todd N.

Re: tsvn 1.7.7 Show Log bugs

Stefan Küng — 2012-05-23T18:48:13

This is already fixed (see post from Konstantin)


Opened issue #305 for this:
http://code.google.com/p/tortoisesvn/issues/detail?id=305

Stefan

Re: Redirection of Upgrade Check

Stefan Küng — 2012-05-23T18:41:30

So you have the new version already, the update check therefore 
correctly shows that there's a new version available (1.7.7) in case 
you're still at 1.7.7.

However, if there's no new version available, then the link at the 
bottom of the update-check dialog always points to our website.

Stefan

Re: Redirection of Upgrade Check

Todd Nelson — 2012-05-23T18:32:26

The content of the tortoisesvn_version.txt file is the following:

1.7.7.22907
A new version of TortoiseSVN is available for you to download!
http://epedia/wiki/TortoiseSVN#Installation


I'll try running a repair on the installations to see if that helps too.