You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Pazmiño,
Iván Andrés <ia...@sri.ad> on 2011/01/03 22:18:51 UTC
Commit fails with path not found
Hello,
I've moved some files (java classes) from a directory to another, and
now commit fails complaining the containing folder doesn't exist
svn: Commit failed (details follow):
svn: '/svn/app-project/trunk/app-project-web/src/main/webapp/templates'
path not found: 404 Not Found (https://xxx)
The path in the message is the path where the file used to be and in the
eclipse IDE the folder and file both have a red arrow over them.
I've tried merging, overriding and commiting, but none works. Any ideas?
Thanks,
IP
"Clausula de Confidencialidad: La información contenida en el presente mensaje es confidencial, está dirigida
exclusivamente a su destinatario y no puede ser vinculante. El Servicio de Rentas Internas no se
responsabiliza por su uso y deja expresa constancia que en los registros de la Institución consta la
información originalmente enviada. Este mensaje está protegido por la Ley de Propiedad Intelectual, Ley de
Comercio Electrónico, Firmas y Mensajes de datos, reglamentos y acuerdos internacionales relacionados. Si
usted no es el destinatario de este mensaje, recomendamos su eliminación inmediata. La distribución o copia
del mismo, está prohibida y será sancionada de acuerdo al Código Penal y demás normas aplicables. La
transmisión de información por correo electrónico, no garantiza que la misma sea segura o esté libre de error,
por consiguiente, se recomienda su verificación.Toda solicitud de información requerida de manera oficial al
SRI debe ser ingresada por Secretaría General y dirigida a la máxima autoridad de la Institución, conforme a
la Ley y demás normas vigentes."
Re: Commit fails with path not found
Posted by Pazmiño,
Iván Andrés <ia...@sri.ad>.
Hello David, thanks so much your help.
I can't get to the first step yet. Once I have updated the project and
have no ! marks anymore, all the conflicting directories are marked
with ?, but when trying to commit it complains because the target
directory is missing
svn commit
svn: Commit failed (details follow):
svn: Directory '.../recursos-revision/recursos-revision-ear/target/.svn'
containing working copy admin area is missing
-----Original Message-----
From: David Weintraub <qa...@gmail.com>
To: iapazmino@sri.gob.ec
Cc: users@subversion.apache.org
Subject: Re: Commit fails with path not found
Date: Mon, 10 Jan 2011 10:01:27 -0500
It looks like you deleted the target directories, but you didn't do an
"svn update". I can see that because "svn status" is putting "!" in
front of the target directories.
Your next step is to do an "svn update" which will recreate the "target"
directories, but as directories Subversion is tracking (they'll have
the .svn directory in them.
Once that is done, you should simply see files with "?" in front of them
and no more "!" or "~". Then, you should be able to commit -- at least
from the command line via "svn commit".
Once you've done the commit, we have your working directory and the
Subversion server more or less in agreement. We can finally clean up the
rest of the mess:
STEP #1: Using the "svn delete" command from the command line, delete
the target directories. That will remove them from the Subversion
repository. You can never, ever have Maven "target" directories in your
Subversion repository. This confuses the heck out of Subversion.
STEP #2: Once you've removed these target directories, do another "svn
commit". Those "target" directories are no longer in your Subversion
repository.
STEP #3: Once we've cleaned up the "target" directory mess, you can take
care of all those directories in your "svn status" that show a "?".
These directories look like source directories, but aren't in your
Subversion repository. If you need them in Subversion, use an "svn add"
to add them in.
STEP #4: Do another "svn status". You shouldn't be getting any lines
that start with "~" or "!" or "?". The only lines you should be getting
start with "A" which means you've added the missing directories to your
Subversion repository.
STEP #5: Do another "svn commit". You've at last cleaned everything up.
All "target" directories that caused problems are now gone. All missing
source directories and files are now in Subversion. In theory, someone
should now be able to checkout the project and do a build.
OPTIONAL, BUT HIGHLY RECOMMENDED STEP #6: Now that everything is cleaned
up, it'll be nice if we could keep it this way. There are two things you
can do:
1. Add the property "svn:ignore=target" to the directories where
"target" directories are built. This will help prevent someone
from accidentally adding these "target" directories back into
your Subversion repository. They won't show up as new, but
missing Subversion elements in status reports, and if you do a
massive add, they won't get added. It is still possible for
someone to purposefully add them back into your Subversion
repository.
2. If you have such a pre-commit trigger, set it so you can't add
directories called "target" to your Subversion repository.
Once you've completed all of these steps, I recommend that you delete
the project in Eclipse and recheck it out, and make sure you can build
it and everything works.
--
David Weintraub
qazwart@gmail.com
"Clausula de Confidencialidad: La información contenida en el presente mensaje es confidencial, está dirigida
exclusivamente a su destinatario y no puede ser vinculante. El Servicio de Rentas Internas no se
responsabiliza por su uso y deja expresa constancia que en los registros de la Institución consta la
información originalmente enviada. Este mensaje está protegido por la Ley de Propiedad Intelectual, Ley de
Comercio Electrónico, Firmas y Mensajes de datos, reglamentos y acuerdos internacionales relacionados. Si
usted no es el destinatario de este mensaje, recomendamos su eliminación inmediata. La distribución o copia
del mismo, está prohibida y será sancionada de acuerdo al Código Penal y demás normas aplicables. La
transmisión de información por correo electrónico, no garantiza que la misma sea segura o esté libre de error,
por consiguiente, se recomienda su verificación.Toda solicitud de información requerida de manera oficial al
SRI debe ser ingresada por Secretaría General y dirigida a la máxima autoridad de la Institución, conforme a
la Ley y demás normas vigentes."
Re: Commit fails with path not found
Posted by David Weintraub <qa...@gmail.com>.
It looks like you deleted the target directories, but you didn't do an "svn
update". I can see that because "svn status" is putting "!" in front of the
target directories.
Your next step is to do an "svn update" which will recreate the "target"
directories, but as directories Subversion is tracking (they'll have the
.svn directory in them.
Once that is done, you should simply see files with "?" in front of them and
no more "!" or "~". Then, you should be able to commit -- at least from the
command line via "svn commit".
Once you've done the commit, we have your working directory and the
Subversion server more or less in agreement. We can finally clean up the
rest of the mess:
*STEP #1*: Using the "svn delete" command from the command line, delete the
target directories. That will remove them from the Subversion repository.
You can never, ever have Maven "target" directories in your Subversion
repository. This confuses the heck out of Subversion.
*STEP #2*: Once you've removed these target directories, do another "svn
commit". Those "target" directories are no longer in your Subversion
repository.
*STEP #3*: Once we've cleaned up the "target" directory mess, you can take
care of all those directories in your "svn status" that show a "?". These
directories look like source directories, but aren't in your Subversion
repository. If you need them in Subversion, use an "svn add" to add them in.
*STEP #4*: Do another "svn status". You shouldn't be getting any lines that
start with "~" or "!" or "?". The only lines you should be getting start
with "A" which means you've added the missing directories to your Subversion
repository.
*STEP #5*: Do another "svn commit". You've at last cleaned everything up.
All "target" directories that caused problems are now gone. All missing
source directories and files are now in Subversion. In theory, someone
should now be able to checkout the project and do a build.
*OPTIONAL, BUT HIGHLY RECOMMENDED STEP #6*: Now that everything is cleaned
up, it'll be nice if we could keep it this way. There are two things you can
do:
1. Add the property "svn:ignore=target" to the directories where "target"
directories are built. This will help prevent someone from accidentally
adding these "target" directories back into your Subversion repository. They
won't show up as new, but missing Subversion elements in status reports, and
if you do a massive add, they won't get added. It is still possible for
someone to purposefully add them back into your Subversion repository.
2. If you have such a pre-commit trigger, set it so you can't add
directories called "target" to your Subversion repository.
Once you've completed all of these steps, I recommend that you delete the
project in Eclipse and recheck it out, and make sure you can build it and
everything works.
--
David Weintraub
qazwart@gmail.com
Re: Commit fails with path not found
Posted by Pazmiño,
Iván Andrés <ia...@sri.ad>.
thanks for your reply.
I do have one folder added to be ignored, in the root the target folder,
but it doesn't even appear in the listing.
-----Original Message-----
From: Johan Corveleyn <jc...@gmail.com>
To: iapazmino@sri.gob.ec
Cc: David Weintraub <qa...@gmail.com>, users@subversion.apache.org
Subject: Re: Commit fails with path not found
Date: Fri, 7 Jan 2011 20:43:54 +0100
2011/1/7 Pazmiño Mazón, Iván Andrés <ia...@sri.ad>:
> I have cleaned the project and checked the -xxx/target directories
> doesn't exist anymore. Then updated. But when tried to check the status
> again the folders still are shown in the result.
>
> svn update
> At revision 60654.
>
> svn status
> M .
> ! recursos-revision-ejb/target
> ?
> recursos-revision-ejb/src/main/java/ec/gob/sri/recursos/revision/comun
> ?
> recursos-revision-ejb/src/main/java/ec/gob/sri/recursos/revision/ejb/entidades
> ?
> recursos-revision-ejb/src/main/java/ec/gob/sri/recursos/revision/ejb/exception
> ?
> recursos-revision-ejb/src/main/java/ec/gob/sri/recursos/revision/ejb/dao/impl
> ?
> recursos-revision-ejb/src/main/java/ec/gob/sri/recursos/revision/servicio/impl
> ! recursos-revision-ear/target
> M recursos-revision-ear/pom.xml
> ! recursos-revision-web/target
> ? recursos-revision-web/src/main/config
> ? recursos-revision-web/src/main/webapp
> ? recursos-revision-web/src/main/java/ec
> A .settings
> A .settings/org.eclipse.jdt.core.prefs
> A .settings/org.maven.ide.eclipse.prefs
>
> and of course if I try to commit it's not possible due to the missing
> folders
I haven't followed/read this thread closely, but just a thought: is
there perhaps some svn:ignore property, or global ignores playing a
role? You can get strange things if you first create a versioned item
(add a file/directory to svn), and subsequently put this in an
svn:ignore property.
(also, if you can, please don't top-post on this list, but put your
reply below or inline the thing you're replying to)
"Clausula de Confidencialidad: La información contenida en el presente mensaje es confidencial, está dirigida
exclusivamente a su destinatario y no puede ser vinculante. El Servicio de Rentas Internas no se
responsabiliza por su uso y deja expresa constancia que en los registros de la Institución consta la
información originalmente enviada. Este mensaje está protegido por la Ley de Propiedad Intelectual, Ley de
Comercio Electrónico, Firmas y Mensajes de datos, reglamentos y acuerdos internacionales relacionados. Si
usted no es el destinatario de este mensaje, recomendamos su eliminación inmediata. La distribución o copia
del mismo, está prohibida y será sancionada de acuerdo al Código Penal y demás normas aplicables. La
transmisión de información por correo electrónico, no garantiza que la misma sea segura o esté libre de error,
por consiguiente, se recomienda su verificación.Toda solicitud de información requerida de manera oficial al
SRI debe ser ingresada por Secretaría General y dirigida a la máxima autoridad de la Institución, conforme a
la Ley y demás normas vigentes."
Re: Commit fails with path not found
Posted by Johan Corveleyn <jc...@gmail.com>.
2011/1/7 Pazmiño Mazón, Iván Andrés <ia...@sri.ad>:
> I have cleaned the project and checked the -xxx/target directories
> doesn't exist anymore. Then updated. But when tried to check the status
> again the folders still are shown in the result.
>
> svn update
> At revision 60654.
>
> svn status
> M .
> ! recursos-revision-ejb/target
> ?
> recursos-revision-ejb/src/main/java/ec/gob/sri/recursos/revision/comun
> ?
> recursos-revision-ejb/src/main/java/ec/gob/sri/recursos/revision/ejb/entidades
> ?
> recursos-revision-ejb/src/main/java/ec/gob/sri/recursos/revision/ejb/exception
> ?
> recursos-revision-ejb/src/main/java/ec/gob/sri/recursos/revision/ejb/dao/impl
> ?
> recursos-revision-ejb/src/main/java/ec/gob/sri/recursos/revision/servicio/impl
> ! recursos-revision-ear/target
> M recursos-revision-ear/pom.xml
> ! recursos-revision-web/target
> ? recursos-revision-web/src/main/config
> ? recursos-revision-web/src/main/webapp
> ? recursos-revision-web/src/main/java/ec
> A .settings
> A .settings/org.eclipse.jdt.core.prefs
> A .settings/org.maven.ide.eclipse.prefs
>
> and of course if I try to commit it's not possible due to the missing
> folders
I haven't followed/read this thread closely, but just a thought: is
there perhaps some svn:ignore property, or global ignores playing a
role? You can get strange things if you first create a versioned item
(add a file/directory to svn), and subsequently put this in an
svn:ignore property.
(also, if you can, please don't top-post on this list, but put your
reply below or inline the thing you're replying to)
--
Johan
Re: Commit fails with path not found
Posted by Pazmiño,
Iván Andrés <ia...@sri.ad>.
I have cleaned the project and checked the -xxx/target directories
doesn't exist anymore. Then updated. But when tried to check the status
again the folders still are shown in the result.
svn update
At revision 60654.
svn status
M .
! recursos-revision-ejb/target
?
recursos-revision-ejb/src/main/java/ec/gob/sri/recursos/revision/comun
?
recursos-revision-ejb/src/main/java/ec/gob/sri/recursos/revision/ejb/entidades
?
recursos-revision-ejb/src/main/java/ec/gob/sri/recursos/revision/ejb/exception
?
recursos-revision-ejb/src/main/java/ec/gob/sri/recursos/revision/ejb/dao/impl
?
recursos-revision-ejb/src/main/java/ec/gob/sri/recursos/revision/servicio/impl
! recursos-revision-ear/target
M recursos-revision-ear/pom.xml
! recursos-revision-web/target
? recursos-revision-web/src/main/config
? recursos-revision-web/src/main/webapp
? recursos-revision-web/src/main/java/ec
A .settings
A .settings/org.eclipse.jdt.core.prefs
A .settings/org.maven.ide.eclipse.prefs
and of course if I try to commit it's not possible due to the missing
folders
-----Original Message-----
From: David Weintraub <qa...@gmail.com>
To: iapazmino@sri.gob.ec
Cc: users@subversion.apache.org
Subject: Re: Commit fails with path not found
Date: Thu, 6 Jan 2011 15:58:29 -0500
The directories that might be causing all the trouble are the "target"
directories marked with the "~" mark. Subversion has these directories
as versioned items, but they were replaced.
I know Maven deletes those directories on a "clean", so I suspect that
you did a checkout, created these directories, and did a rebuild. That
would have created new "target" directories that prevent Subversion from
putting its versioned "target" directories.
The directories that start with a "?" should be causing Subversion
commit issues.
Try this from the command line:
1). Delete the 3 "target" directories. Under Maven, there shouldn't be
anything in there that you need. However, you might want to verify that
first anyway. You should be able to remove them with a "mvn clean".
2). Do a "svn update". This should recreate the target directories, but
these will now be Subversion's version of these directories.
3). Run "svn status" one more time. Make sure that you don't have any
listings with "!", "~", or "C" in the first column. The "?" are fine and
shouldn't block a commit (although you probably want to add them to the
repository, but let's take care of one problem at a time).
4). Now try the commit once more. You can do that from the command line
with a "svn commit". The build might not work right this second, but we
can fix that in a couple of minutes. Let's make sure you can commit your
stuff.
5). If you can do a commit, your next step is to remove the "target"
directories using the "svn delete" command. These should not be stored
in Subversion.
6). You might want to add in the directories with the "?" before we do
another commit. you can use the "svn add" command. The "svn add" will
recurse automatically through the directories and add in any sub
directories and files.
7). Now commit once more. Your workspace should be clean. There are no
more "target" directories in your repository. Although, you might still
have them on your disk. Again, "mvn clean" should get rid of them.
8). Now refresh your Eclipse workspace and everything should be fine.
--
David Weintraub
qazwart@gmail.com
"Clausula de Confidencialidad: La información contenida en el presente mensaje es confidencial, está dirigida
exclusivamente a su destinatario y no puede ser vinculante. El Servicio de Rentas Internas no se
responsabiliza por su uso y deja expresa constancia que en los registros de la Institución consta la
información originalmente enviada. Este mensaje está protegido por la Ley de Propiedad Intelectual, Ley de
Comercio Electrónico, Firmas y Mensajes de datos, reglamentos y acuerdos internacionales relacionados. Si
usted no es el destinatario de este mensaje, recomendamos su eliminación inmediata. La distribución o copia
del mismo, está prohibida y será sancionada de acuerdo al Código Penal y demás normas aplicables. La
transmisión de información por correo electrónico, no garantiza que la misma sea segura o esté libre de error,
por consiguiente, se recomienda su verificación.Toda solicitud de información requerida de manera oficial al
SRI debe ser ingresada por Secretaría General y dirigida a la máxima autoridad de la Institución, conforme a
la Ley y demás normas vigentes."
Re: Commit fails with path not found
Posted by David Weintraub <qa...@gmail.com>.
The directories that might be causing all the trouble are the "target"
directories marked with the "~" mark. Subversion has these directories as
versioned items, but they were replaced.
I know Maven deletes those directories on a "clean", so I suspect that you
did a checkout, created these directories, and did a rebuild. That would
have created new "target" directories that prevent Subversion from putting
its versioned "target" directories.
The directories that start with a "?" should be causing Subversion commit
issues.
Try this from the command line:
1). Delete the 3 "target" directories. Under Maven, there shouldn't be
anything in there that you need. However, you might want to verify that
first anyway. You should be able to remove them with a "mvn clean".
2). Do a "svn update". This should recreate the target directories, but
these will now be Subversion's version of these directories.
3). Run "svn status" one more time. Make sure that you don't have any
listings with "!", "~", or "C" in the first column. The "?" are fine and
shouldn't block a commit (although you probably want to add them to the
repository, but let's take care of one problem at a time).
4). Now try the commit once more. You can do that from the command line with
a "svn commit". The build might not work right this second, but we can fix
that in a couple of minutes. Let's make sure you can commit your stuff.
5). If you can do a commit, your next step is to remove the "target"
directories using the "svn delete" command. These should not be stored in
Subversion.
6). You might want to add in the directories with the "?" before we do
another commit. you can use the "svn add" command. The "svn add" will
recurse automatically through the directories and add in any sub directories
and files.
7). Now commit once more. Your workspace should be clean. There are no more
"target" directories in your repository. Although, you might still have them
on your disk. Again, "mvn clean" should get rid of them.
8). Now refresh your Eclipse workspace and everything should be fine.
--
David Weintraub
qazwart@gmail.com
Re: Commit fails with path not found
Posted by Pazmiño,
Iván Andrés <ia...@sri.ad>.
This project went through some big refactoring. It was not a maven
project at first and had very different directories structure. The
modules did not exist before so all the -ejb -ear and -web directories
are new and the source and other files inside were originally in
directories on the root directory.
I've looked into some of the problem directories and no one is marked
with (!)
-----Original Message-----
From: David Weintraub <qa...@gmail.com>
To: iapazmino@sri.gob.ec
Cc: users@subversion.apache.org
Subject: Re: Commit fails with path not found
Date: Wed, 5 Jan 2011 16:56:35 -0500
Interesting. These look like directory names. The ones that start with
"?" are not under Subversion control. Are these the ones you moved? The
directoy is "src/main/java/...", so I assume these should be under
version control. Did you move your directories around?
The strange thing is the "~" mark. This is for versioned items that are
obstructed. For example, if I delete a directory, and put a file in its
place. However, these are for "target" directories which I assume should
not be under version control. Did you put the "target" directory under
revision control? The "obstructed version object flag" (~) could happen
if you delete the revisioned target directories and then put duplicate
non-revisioned "target" directories in their place.
Are there any directories or files showing up with the "missing
flag" (!)?
2011/1/5 Pazmiño Mazón, Iván Andrés <ia...@sri.ad>
Thanks a lot David!
This is the output to my status command:
iapm270409@UIOiapm270409:~/workspace/intranet/recursos-revision$
svn
status
M .
~ recursos-revision-ejb/target
?
recursos-revision-ejb/src/main/java/ec/gob/sri/recursos/revision/comun
?
recursos-revision-ejb/src/main/java/ec/gob/sri/recursos/revision/ejb/entidades
?
recursos-revision-ejb/src/main/java/ec/gob/sri/recursos/revision/ejb/exception
?
recursos-revision-ejb/src/main/java/ec/gob/sri/recursos/revision/ejb/dao/impl
?
recursos-revision-ejb/src/main/java/ec/gob/sri/recursos/revision/servicio/impl
~ recursos-revision-ear/target
~ recursos-revision-web/target
? recursos-revision-web/src/main/config
? recursos-revision-web/src/main/webapp
? recursos-revision-web/src/main/java/ec
A .settings
A .settings/org.eclipse.jdt.core.prefs
A .settings/org.maven.ide.eclipse.prefs
The command was run on the projects base directory.
-----Original Message-----
From: David Weintraub <qa...@gmail.com>
To: iapazmino@sri.gob.ec
Cc: users@subversion.apache.org
Subject: Re: Commit fails with path not found
Date: Tue, 4 Jan 2011 12:08:27 -0500
2011/1/4 Pazmiño Mazón, Iván Andrés <ia...@sri.ad>:
> I just moved the directories within the IDE, it's eclipse, and
worked
on
> them for quite long before being ready to commit. I'm using
subversive
> plugin.
If you don't have the command line Subversion client installed,
install
it on your system, and try the following:
Go to the directory where your files are checked out and run:
C> svn status
This will print out the status of the various files in your
working
directory. If the first column is an exclamation point (!), it
means
that the file exists in Subversion, but does not exist in your
working
directory. If the first column of the report is a question mark
(?), it
means that the item is not under version control.
I have a feeling that when you moved files around with Eclipse,
it
didn't inform Subversion what you were doing, and you'll see the
files
in the directory where they were moved starting with a "?" and
in the
directory where they were moved from, you'll see a "!".
I just played around with my Subversion install, and see the
following:
H:\svn> move groups.pl File
H:\svn> svn status
? File\groups.pl
! groups.pl
M updateRms.cqpl
I first moved the file "groups.pl" to the File directory, and
ran "svn
status".
The first line in the status report is telling me that the file
"groups.pl" is under the "File" directory, but is not under
version
control. The second line is telling me that the file "groups.pl"
should
be in the current directory, but isn't found there. Subversion
may not
let me commit my changes. (It might, but I'm not going to see
what
happens).
What I should have done was:
H:\svn> svn move groups.pl File
A File\groups.pl
D groups.pl
Which would have not only moved the file, but told Subversion
that I was
moving the file. If I do that, my "svn status" report looks like
this:
H:\svn> svn status
A + File\groups.pl
D groups.pl
M updateRms.cqpl
Subversion is now showing me that I am adding a file called
"groups.pl"
to the "File" directory, and I'm deleting this file from the
current
directory. I can now do a "svn commit".
I don't have a copy of Eclipse in front of me, but you need to
do all
SCM stuff using the "Team" menu item in the drop down menu when
you
click on a file. I believe you can move files from there.
It could be that Eclipse is suppose to track drag and drop
changes for
SCM files, and it's not which would be an Eclipse issue. There
may be
someone on this list who can help you out, but you might have to
ask at
an Eclipse support site.
So, run the "svn status" command and show us the output. It'll
allow us
to more easily identify the issues you're having.
--
David Weintraub
qazwart@gmail.com
--
David Weintraub
qazwart@gmail.com
"Clausula de Confidencialidad: La información contenida en el presente mensaje es confidencial, está dirigida
exclusivamente a su destinatario y no puede ser vinculante. El Servicio de Rentas Internas no se
responsabiliza por su uso y deja expresa constancia que en los registros de la Institución consta la
información originalmente enviada. Este mensaje está protegido por la Ley de Propiedad Intelectual, Ley de
Comercio Electrónico, Firmas y Mensajes de datos, reglamentos y acuerdos internacionales relacionados. Si
usted no es el destinatario de este mensaje, recomendamos su eliminación inmediata. La distribución o copia
del mismo, está prohibida y será sancionada de acuerdo al Código Penal y demás normas aplicables. La
transmisión de información por correo electrónico, no garantiza que la misma sea segura o esté libre de error,
por consiguiente, se recomienda su verificación.Toda solicitud de información requerida de manera oficial al
SRI debe ser ingresada por Secretaría General y dirigida a la máxima autoridad de la Institución, conforme a
la Ley y demás normas vigentes."
Re: Commit fails with path not found
Posted by David Weintraub <qa...@gmail.com>.
Interesting. These look like directory names. The ones that start with "?"
are not under Subversion control. Are these the ones you moved? The directoy
is "src/main/java/...", so I assume these should be under version control.
Did you move your directories around?
The strange thing is the "~" mark. This is for versioned items that are
obstructed. For example, if I delete a directory, and put a file in its
place. However, these are for "target" directories which I assume should not
be under version control. Did you put the "target" directory under revision
control? The "obstructed version object flag" (~) could happen if you delete
the revisioned target directories and then put duplicate non-revisioned
"target" directories in their place.
Are there any directories or files showing up with the "missing flag" (!)?
2011/1/5 Pazmiño Mazón, Iván Andrés <ia...@sri.ad>
> Thanks a lot David!
>
> This is the output to my status command:
>
> iapm270409@UIOiapm270409:~/workspace/intranet/recursos-revision$ svn
> status
> M .
> ~ recursos-revision-ejb/target
> ?
> recursos-revision-ejb/src/main/java/ec/gob/sri/recursos/revision/comun
> ?
>
> recursos-revision-ejb/src/main/java/ec/gob/sri/recursos/revision/ejb/entidades
> ?
>
> recursos-revision-ejb/src/main/java/ec/gob/sri/recursos/revision/ejb/exception
> ?
>
> recursos-revision-ejb/src/main/java/ec/gob/sri/recursos/revision/ejb/dao/impl
> ?
>
> recursos-revision-ejb/src/main/java/ec/gob/sri/recursos/revision/servicio/impl
> ~ recursos-revision-ear/target
> ~ recursos-revision-web/target
> ? recursos-revision-web/src/main/config
> ? recursos-revision-web/src/main/webapp
> ? recursos-revision-web/src/main/java/ec
> A .settings
> A .settings/org.eclipse.jdt.core.prefs
> A .settings/org.maven.ide.eclipse.prefs
>
> The command was run on the projects base directory.
>
> -----Original Message-----
> From: David Weintraub <qa...@gmail.com>
> To: iapazmino@sri.gob.ec
> Cc: users@subversion.apache.org
> Subject: Re: Commit fails with path not found
> Date: Tue, 4 Jan 2011 12:08:27 -0500
>
> 2011/1/4 Pazmiño Mazón, Iván Andrés <ia...@sri.ad>:
> > I just moved the directories within the IDE, it's eclipse, and worked
> on
> > them for quite long before being ready to commit. I'm using subversive
> > plugin.
>
> If you don't have the command line Subversion client installed, install
> it on your system, and try the following:
>
> Go to the directory where your files are checked out and run:
>
> C> svn status
>
> This will print out the status of the various files in your working
> directory. If the first column is an exclamation point (!), it means
> that the file exists in Subversion, but does not exist in your working
> directory. If the first column of the report is a question mark (?), it
> means that the item is not under version control.
>
> I have a feeling that when you moved files around with Eclipse, it
> didn't inform Subversion what you were doing, and you'll see the files
> in the directory where they were moved starting with a "?" and in the
> directory where they were moved from, you'll see a "!".
>
> I just played around with my Subversion install, and see the following:
>
> H:\svn> move groups.pl File
> H:\svn> svn status
> ? File\groups.pl
> ! groups.pl
> M updateRms.cqpl
>
> I first moved the file "groups.pl" to the File directory, and ran "svn
> status".
>
>
> The first line in the status report is telling me that the file
> "groups.pl" is under the "File" directory, but is not under version
> control. The second line is telling me that the file "groups.pl" should
> be in the current directory, but isn't found there. Subversion may not
> let me commit my changes. (It might, but I'm not going to see what
> happens).
>
>
> What I should have done was:
>
>
> H:\svn> svn move groups.pl File
> A File\groups.pl
> D groups.pl
>
>
>
> Which would have not only moved the file, but told Subversion that I was
> moving the file. If I do that, my "svn status" report looks like this:
>
>
> H:\svn> svn status
> A + File\groups.pl
> D groups.pl
> M updateRms.cqpl
>
> Subversion is now showing me that I am adding a file called "groups.pl"
> to the "File" directory, and I'm deleting this file from the current
> directory. I can now do a "svn commit".
>
>
> I don't have a copy of Eclipse in front of me, but you need to do all
> SCM stuff using the "Team" menu item in the drop down menu when you
> click on a file. I believe you can move files from there.
>
>
> It could be that Eclipse is suppose to track drag and drop changes for
> SCM files, and it's not which would be an Eclipse issue. There may be
> someone on this list who can help you out, but you might have to ask at
> an Eclipse support site.
>
>
> So, run the "svn status" command and show us the output. It'll allow us
> to more easily identify the issues you're having.
>
>
> --
> David Weintraub
> qazwart@gmail.com
>
>
>
> "Clausula de Confidencialidad: La información contenida en el presente
> mensaje es confidencial, está dirigida
> exclusivamente a su destinatario y no puede ser vinculante. El Servicio de
> Rentas Internas no se
> responsabiliza por su uso y deja expresa constancia que en los registros de
> la Institución consta la
> información originalmente enviada. Este mensaje está protegido por la Ley
> de Propiedad Intelectual, Ley de
> Comercio Electrónico, Firmas y Mensajes de datos, reglamentos y acuerdos
> internacionales relacionados. Si
> usted no es el destinatario de este mensaje, recomendamos su eliminación
> inmediata. La distribución o copia
> del mismo, está prohibida y será sancionada de acuerdo al Código Penal y
> demás normas aplicables. La
> transmisión de información por correo electrónico, no garantiza que la
> misma sea segura o esté libre de error,
> por consiguiente, se recomienda su verificación.Toda solicitud de
> información requerida de manera oficial al
> SRI debe ser ingresada por Secretaría General y dirigida a la máxima
> autoridad de la Institución, conforme a
> la Ley y demás normas vigentes."
>
--
David Weintraub
qazwart@gmail.com
Re: Commit fails with path not found
Posted by Pazmiño,
Iván Andrés <ia...@sri.ad>.
Thanks a lot David!
This is the output to my status command:
iapm270409@UIOiapm270409:~/workspace/intranet/recursos-revision$ svn
status
M .
~ recursos-revision-ejb/target
?
recursos-revision-ejb/src/main/java/ec/gob/sri/recursos/revision/comun
?
recursos-revision-ejb/src/main/java/ec/gob/sri/recursos/revision/ejb/entidades
?
recursos-revision-ejb/src/main/java/ec/gob/sri/recursos/revision/ejb/exception
?
recursos-revision-ejb/src/main/java/ec/gob/sri/recursos/revision/ejb/dao/impl
?
recursos-revision-ejb/src/main/java/ec/gob/sri/recursos/revision/servicio/impl
~ recursos-revision-ear/target
~ recursos-revision-web/target
? recursos-revision-web/src/main/config
? recursos-revision-web/src/main/webapp
? recursos-revision-web/src/main/java/ec
A .settings
A .settings/org.eclipse.jdt.core.prefs
A .settings/org.maven.ide.eclipse.prefs
The command was run on the projects base directory.
-----Original Message-----
From: David Weintraub <qa...@gmail.com>
To: iapazmino@sri.gob.ec
Cc: users@subversion.apache.org
Subject: Re: Commit fails with path not found
Date: Tue, 4 Jan 2011 12:08:27 -0500
2011/1/4 Pazmiño Mazón, Iván Andrés <ia...@sri.ad>:
> I just moved the directories within the IDE, it's eclipse, and worked
on
> them for quite long before being ready to commit. I'm using subversive
> plugin.
If you don't have the command line Subversion client installed, install
it on your system, and try the following:
Go to the directory where your files are checked out and run:
C> svn status
This will print out the status of the various files in your working
directory. If the first column is an exclamation point (!), it means
that the file exists in Subversion, but does not exist in your working
directory. If the first column of the report is a question mark (?), it
means that the item is not under version control.
I have a feeling that when you moved files around with Eclipse, it
didn't inform Subversion what you were doing, and you'll see the files
in the directory where they were moved starting with a "?" and in the
directory where they were moved from, you'll see a "!".
I just played around with my Subversion install, and see the following:
H:\svn> move groups.pl File
H:\svn> svn status
? File\groups.pl
! groups.pl
M updateRms.cqpl
I first moved the file "groups.pl" to the File directory, and ran "svn
status".
The first line in the status report is telling me that the file
"groups.pl" is under the "File" directory, but is not under version
control. The second line is telling me that the file "groups.pl" should
be in the current directory, but isn't found there. Subversion may not
let me commit my changes. (It might, but I'm not going to see what
happens).
What I should have done was:
H:\svn> svn move groups.pl File
A File\groups.pl
D groups.pl
Which would have not only moved the file, but told Subversion that I was
moving the file. If I do that, my "svn status" report looks like this:
H:\svn> svn status
A + File\groups.pl
D groups.pl
M updateRms.cqpl
Subversion is now showing me that I am adding a file called "groups.pl"
to the "File" directory, and I'm deleting this file from the current
directory. I can now do a "svn commit".
I don't have a copy of Eclipse in front of me, but you need to do all
SCM stuff using the "Team" menu item in the drop down menu when you
click on a file. I believe you can move files from there.
It could be that Eclipse is suppose to track drag and drop changes for
SCM files, and it's not which would be an Eclipse issue. There may be
someone on this list who can help you out, but you might have to ask at
an Eclipse support site.
So, run the "svn status" command and show us the output. It'll allow us
to more easily identify the issues you're having.
--
David Weintraub
qazwart@gmail.com
"Clausula de Confidencialidad: La información contenida en el presente mensaje es confidencial, está dirigida
exclusivamente a su destinatario y no puede ser vinculante. El Servicio de Rentas Internas no se
responsabiliza por su uso y deja expresa constancia que en los registros de la Institución consta la
información originalmente enviada. Este mensaje está protegido por la Ley de Propiedad Intelectual, Ley de
Comercio Electrónico, Firmas y Mensajes de datos, reglamentos y acuerdos internacionales relacionados. Si
usted no es el destinatario de este mensaje, recomendamos su eliminación inmediata. La distribución o copia
del mismo, está prohibida y será sancionada de acuerdo al Código Penal y demás normas aplicables. La
transmisión de información por correo electrónico, no garantiza que la misma sea segura o esté libre de error,
por consiguiente, se recomienda su verificación.Toda solicitud de información requerida de manera oficial al
SRI debe ser ingresada por Secretaría General y dirigida a la máxima autoridad de la Institución, conforme a
la Ley y demás normas vigentes."
Re: Commit fails with path not found
Posted by David Weintraub <qa...@gmail.com>.
2011/1/4 Pazmiño Mazón, Iván Andrés <ia...@sri.ad>:
> I just moved the directories within the IDE, it's eclipse, and worked on
> them for quite long before being ready to commit. I'm using subversive
> plugin.
If you don't have the command line Subversion client installed, install it
on your system, and try the following:
Go to the directory where your files are checked out and run:
C> svn status
This will print out the status of the various files in your working
directory. If the first column is an exclamation point (!), it means that
the file exists in Subversion, but does not exist in your working directory.
If the first column of the report is a question mark (?), it means that the
item is not under version control.
I have a feeling that when you moved files around with Eclipse, it didn't
inform Subversion what you were doing, and you'll see the files in the
directory where they were moved starting with a "?" and in the directory
where they were moved from, you'll see a "!".
I just played around with my Subversion install, and see the following:
H:\svn> move groups.pl File
H:\svn> svn status
? File\groups.pl
! groups.pl
M updateRms.cqpl
I first moved the file "groups.pl" to the File directory, and ran "svn
status".
The first line in the status report is telling me that the file "groups.pl"
is under the "File" directory, but is not under version control. The second
line is telling me that the file "groups.pl" should be in the current
directory, but isn't found there. Subversion may not let me commit my
changes. (It might, but I'm not going to see what happens).
What I should have done was:
H:\svn> svn move groups.pl File
A File\groups.pl
D groups.pl
Which would have not only moved the file, but told Subversion that I was
moving the file. If I do that, my "svn status" report looks like this:
H:\svn> svn status
A + File\groups.pl
D groups.pl
M updateRms.cqpl
Subversion is now showing me that I am adding a file called "groups.pl" to
the "File" directory, and I'm deleting this file from the current directory.
I can now do a "svn commit".
I don't have a copy of Eclipse in front of me, but you need to do all SCM
stuff using the "Team" menu item in the drop down menu when you click on a
file. I believe you can move files from there.
It could be that Eclipse is suppose to track drag and drop changes for SCM
files, and it's not which would be an Eclipse issue. There may be someone on
this list who can help you out, but you might have to ask at an Eclipse
support site.
So, run the "svn status" command and show us the output. It'll allow us to
more easily identify the issues you're having.
--
David Weintraub
qazwart@gmail.com
Re: Commit fails with path not found
Posted by Pazmiño,
Iván Andrés <ia...@sri.ad>.
I just moved the directories within the IDE, it's eclipse, and worked on
them for quite long before being ready to commit. I'm using subversive
plugin.
-----Original Message-----
From: David Weintraub <qa...@gmail.com>
To: iapazmino@sri.gob.ec
Cc: users@subversion.apache.org
Subject: Re: Commit fails with path not found
Date: Mon, 3 Jan 2011 17:31:47 -0500
2011/1/3 Pazmiño Mazón, Iván Andrés <ia...@sri.ad>:
> Hello,
>
> I've moved some files (java classes) from a directory to another, and
> now commit fails complaining the containing folder doesn't exist
One of the things that trip many people up is that Subversion doesn't
know you've moved something until you tell it you have.
I've seen people do this from the command line using rename/move/mv
(depending upon platform, or in a GUI by simply clicking on a
directory and moving it elsewhere.
You have to tell Subversion, you're moving the files. In TortoiseSVN,
you right click on the file, move it, and it'll show you a menu with
items like "SVN Move versioned items here". From the command line, you
have to use "svn move". If you're in Eclipse, you must use the Team
menu item to move things around.
Did you simply move the files from one directory to another, or did
you use the Subversion commands to do this?
"Clausula de Confidencialidad: La información contenida en el presente mensaje es confidencial, está dirigida
exclusivamente a su destinatario y no puede ser vinculante. El Servicio de Rentas Internas no se
responsabiliza por su uso y deja expresa constancia que en los registros de la Institución consta la
información originalmente enviada. Este mensaje está protegido por la Ley de Propiedad Intelectual, Ley de
Comercio Electrónico, Firmas y Mensajes de datos, reglamentos y acuerdos internacionales relacionados. Si
usted no es el destinatario de este mensaje, recomendamos su eliminación inmediata. La distribución o copia
del mismo, está prohibida y será sancionada de acuerdo al Código Penal y demás normas aplicables. La
transmisión de información por correo electrónico, no garantiza que la misma sea segura o esté libre de error,
por consiguiente, se recomienda su verificación.Toda solicitud de información requerida de manera oficial al
SRI debe ser ingresada por Secretaría General y dirigida a la máxima autoridad de la Institución, conforme a
la Ley y demás normas vigentes."
Re: Commit fails with path not found
Posted by David Weintraub <qa...@gmail.com>.
2011/1/3 Pazmiño Mazón, Iván Andrés <ia...@sri.ad>:
> Hello,
>
> I've moved some files (java classes) from a directory to another, and
> now commit fails complaining the containing folder doesn't exist
One of the things that trip many people up is that Subversion doesn't
know you've moved something until you tell it you have.
I've seen people do this from the command line using rename/move/mv
(depending upon platform, or in a GUI by simply clicking on a
directory and moving it elsewhere.
You have to tell Subversion, you're moving the files. In TortoiseSVN,
you right click on the file, move it, and it'll show you a menu with
items like "SVN Move versioned items here". From the command line, you
have to use "svn move". If you're in Eclipse, you must use the Team
menu item to move things around.
Did you simply move the files from one directory to another, or did
you use the Subversion commands to do this?
--
David Weintraub
qazwart@gmail.com
Re: Commit fails with path not found
Posted by Ryan Schmidt <su...@ryandesign.com>.
On Jan 3, 2011, at 15:32, Pazmiño Mazón, Iván Andrés wrote:
> Nick wrote:
>
>> svn update on the client
>
> what do you mean? using the client instead of the ide?
Using whatever. Presumably if you're using an IDE that has Subversion support, it will have a menu or button or something that will run an "svn update". If your IDE does not have Subversion support, well, that's a problem. And from what you've said before, it sounds like your IDE does not have Subversion support, or if it does, then it is not configured properly. It sounds like you've moved directories around in your IDE without the IDE informing Subversion about those moves. It's vital to inform Subversion about moves by performing the moves (or rather, having the IDE perform those moves) using the "svn mv" command. Consult your IDE's documentation to learn about its Subversion capabilities, if any.
Re: Commit fails with path not found
Posted by Pazmiño,
Iván Andrés <ia...@sri.ad>.
what do you mean? using the client instead of the ide?
-----Original Message-----
From: Nick <no...@codesniffer.com>
To: iapazmino@sri.gob.ec
Cc: users@subversion.apache.org
Subject: Re: Commit fails with path not found
Date: Mon, 03 Jan 2011 16:19:56 -0500
svn update on the client
"Clausula de Confidencialidad: La información contenida en el presente mensaje es confidencial, está dirigida
exclusivamente a su destinatario y no puede ser vinculante. El Servicio de Rentas Internas no se
responsabiliza por su uso y deja expresa constancia que en los registros de la Institución consta la
información originalmente enviada. Este mensaje está protegido por la Ley de Propiedad Intelectual, Ley de
Comercio Electrónico, Firmas y Mensajes de datos, reglamentos y acuerdos internacionales relacionados. Si
usted no es el destinatario de este mensaje, recomendamos su eliminación inmediata. La distribución o copia
del mismo, está prohibida y será sancionada de acuerdo al Código Penal y demás normas aplicables. La
transmisión de información por correo electrónico, no garantiza que la misma sea segura o esté libre de error,
por consiguiente, se recomienda su verificación.Toda solicitud de información requerida de manera oficial al
SRI debe ser ingresada por Secretaría General y dirigida a la máxima autoridad de la Institución, conforme a
la Ley y demás normas vigentes."
Re: Commit fails with path not found
Posted by Nick <no...@codesniffer.com>.
On Mon, 2011-01-03 at 16:18 -0500, Pazmiño Mazón, Iván Andrés wrote:
> I've moved some files (java classes) from a directory to another, and
> now commit fails complaining the containing folder doesn't exist
>
> svn: Commit failed (details follow):
> svn:
> '/svn/app-project/trunk/app-project-web/src/main/webapp/templates'
> path not found: 404 Not Found (https://xxx)
>
> The path in the message is the path where the file used to be and in
> the
> eclipse IDE the folder and file both have a red arrow over them.
>
> I've tried merging, overriding and commiting, but none works. Any
> ideas?
Did you try svn update on the client?
NIck