Project

General

Profile

Actions

Defect #58

closed

repository browsing returns notice_scm_error

Added by Nikolay Solakov over 17 years ago. Updated over 17 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Affected version:

Description

Hi,
I have a filename - "What's New.txt" in my repository and when I click on it I get the notice_scm_error. I
notice this only for this file.

Thanks,
Nikolay

Actions #1

Updated by Nikolay Solakov over 17 years ago

And something more:
when I click on any View differences concerning a single
file (mean the right links for every file on a revision
page) I get the same error.

Thanks

Actions #2

Updated by Jean-Philippe Lang over 17 years ago

Hi

First point is fixed in rev 522.

Concerning the second point, does this problem occur for any
file ? Could you post the correponding log (in dev mode) ? In
particular, the line that starts with: "Shelling out:"
(the svn command in fact).

Actions #3

Updated by Nikolay Solakov over 17 years ago

Hi,
The problem comes with changing the address of the
repository. The changes table remains in the old paths.
example:
old: http://host/svn/repository concatenatet with
/project1/file1,
new: http://host/svn/repository/project1 concatenated with
/project1/file1.

new doubles /project1.

Regards,
Nikolay

Actions #4

Updated by Nikolay Solakov over 17 years ago

As for the top link "View differences", it shows just
the
changeset for the selected revision of the repository. So it
works correct. The right individual file links are affected
of the problem.

I hope it helps :)

Actions #5

Updated by Nikolay Solakov over 17 years ago

The question is: Is it possible to setting the link for the
repository of some project to any path different from root
of the repository?
Maybe this is the problem.

Actions #6

Updated by Jean-Philippe Lang over 17 years ago

Is it possible to setting the link for the

repository of some project to any path different from root
of the repository?

Yes.

The problem comes with changing the address of the

repository.

How did you change the url of the repository, through the web
app or directly in the db ?

The changes table remains in the old paths.

Paths in the "changes" table are always absolute, even
if your repository url points to a subdir.
In fact, the root url of the repository is retrieved and stored
in db (look at the repository table).

Actions #7

Updated by Nikolay Solakov over 17 years ago

Hi,
Shelling out: svn diff -r 189:190
"http://*.*.*.*/svn/build/oraBuild/Development//oraBuild/Dev
elopment/Tools/MkVer4/ReadMe1st.TXT"@190
--username * --password *

I removed the checkbox of the repo url through the web app.
Then I added the url againg. Then I clicked SVN Repository
for filling the tables in the db. And then I got this in the
development log with the error displayed.

Thanks,
Nikolay

Actions #8

Updated by Jean-Philippe Lang over 17 years ago

I would like to know 2 more things:

- what value you have in the root_url field of your repository
table (if it was working, you should have something like
http://*.*.*.*/svn/build/)

- what you get when you run this svn command:
svn info http://*.*.*.*/svn/build/oraBuild/Development/
(full output please)

Actions #9

Updated by Nikolay Solakov over 17 years ago

Hello,

My SVN Repo from the web app:
http://*.*.*.*/svn/build/oraBuild/Development/

My root_url:
http://*.*.*.*/svn/build;

svn info http://*.*.*.*/svn/build/oraBuild/Development/

Path: Development
URL: http://*.*.*.*/svn/build/oraBuild/Development
Repository Root: http://*.*.*.*/svn/build
Repository UUID: af4b8885-56d8-484b-8861-d50510d6205b
Revision: 190
Node Kind: directory
Last Changed Author: niki
Last Changed Rev: 190
Last Changed Date: 2007-05-05 13:09:11 +0300 (ÑÂъñþтð, 05
Ãœðù
2007)

Hope it helps :)

Thank,
Nikolay

Actions #10

Updated by Nikolay Solakov over 17 years ago

The root_url is without the ";" at the end.

Actions #11

Updated by Jean-Philippe Lang over 17 years ago

Thanks
I found the bug. Rev 528 should fix it.

Actions #12

Updated by Nikolay Solakov over 17 years ago

I think it's ok now.

Thanks,
Nikolay

Actions

Also available in: Atom PDF