subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Weintraub <qazw...@gmail.com>
Subject Re: Commit fails with path not found
Date Wed, 05 Jan 2011 21:56:35 GMT
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 <iapm270409@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 <qazwart@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 <iapm270409@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

Mime
View raw message