| View previous topic :: View next topic |
| Author |
Message |
Chris
Guest
|
 Posted: Mon Nov 17, 2008 7:15 pm Post subject: .svn/tmp |
 |
|
Hello,
After 3+ years using CVS, I have switched to Subversion (SVN). I copy my
working-copy to my laptop (not access to the SVN repo via the laptop) from
time to time. When I am done on the laptop I copy the working-copy back to
my main machine in order to commit my changes to the repo.
Lately, I have been getting errors that .svn/tmp is missing. If I manually
create the tmp dirs (recursively as I have subdirectory) and then do "svn
cleanup" the error goes away (most of the time) and I am able to commit my
changes.
Why does .svn/tmp go missing in the first place? I use tar to create
a .tar.gz of the working-copy, so .svn/tmp should not go missing, right?
--
Chris |
|
| |
|
 Back to top |
Kevin Nathan
Guest
|
| Posted: Tue Nov 18, 2008 8:29 am Post subject: Re: .svn/tmp |
|
|
On Mon, 17 Nov 2008 13:15:42 GMT
Chris <chris@thisisnotanemailaddress.ca> wrote:
| Quote: | After 3+ years using CVS, I have switched to Subversion (SVN). I copy
my working-copy to my laptop (not access to the SVN repo via the
laptop) from time to time. When I am done on the laptop I copy the
working-copy back to my main machine in order to commit my changes to
the repo.
|
This can often lead to some strange problems. What I have done when I
need to go from one directory/machine and another without being able to
use the repository for it is to remove the .svn directories, then tar
it up and untar and commit in the main directory. I use the following
script in the top directory of my code to remove the .svn directories
(*only* use this on your laptop and *not* on your other machine!)
#!/bin/bash
find . -type d -iname '.svn*' | xargs -i rm -R {}
| Quote: | Why does .svn/tmp go missing in the first place? I use tar to create
a .tar.gz of the working-copy, so .svn/tmp should not go missing,
right?
|
I don't know why that directory goes missing, but I've had some very
hard to correct problems happen when I copied the directory structure
between two different machines. My solution above has always worked. :-)
--
Kevin Nathan (Arizona, USA)
Linux Potpourri and a.o.l.s. FAQ -- (temporarily offline)
Open standards. Open source. Open minds.
The command line is the front line.
Linux 2.6.25.18-0.2-pae
10:31pm up 21 days 2:22, 20 users, load average: 0.67, 0.64, 0.59 |
|
| |
|
| Back to top |
Chris
Guest
|
| Posted: Tue Nov 18, 2008 4:39 pm Post subject: Re: .svn/tmp |
|
|
Kevin Nathan wrote:
| Quote: | On Mon, 17 Nov 2008 13:15:42 GMT
Chris <chris@thisisnotanemailaddress.ca> wrote:
After 3+ years using CVS, I have switched to Subversion (SVN). I copy
my working-copy to my laptop (not access to the SVN repo via the
laptop) from time to time. When I am done on the laptop I copy the
working-copy back to my main machine in order to commit my changes to
the repo.
This can often lead to some strange problems. What I have done when I
need to go from one directory/machine and another without being able to
use the repository for it is to remove the .svn directories, then tar
it up and untar and commit in the main directory. I use the following
script in the top directory of my code to remove the .svn directories
(*only* use this on your laptop and *not* on your other machine!)
#!/bin/bash
find . -type d -iname '.svn*' | xargs -i rm -R {}
Why does .svn/tmp go missing in the first place? I use tar to create
a .tar.gz of the working-copy, so .svn/tmp should not go missing,
right?
I don't know why that directory goes missing, but I've had some very
hard to correct problems happen when I copied the directory structure
between two different machines. My solution above has always worked. :-)
|
Thanks for the info. I guess I will need to move around just the code and
try to leave the .svn dirs on my main development machine.
Thanks.
--
Chris |
|
| |
|
| Back to top |
Kevin Nathan
Guest
|
| Posted: Wed Nov 19, 2008 8:42 am Post subject: Re: .svn/tmp |
|
|
On Tue, 18 Nov 2008 10:39:04 GMT
Chris <chris@thisisnotanemailaddress.ca> wrote:
| Quote: | Thanks for the info. I guess I will need to move around just the code
and try to leave the .svn dirs on my main development machine.
|
Just to clarify the procedure -- I am assuming your desktop is the
subversion-capable machine and the laptop is not. This, then, is the
procedure to follow:
1. Tar up the source directory on desktop.
2. Copy file to laptop.
3. Untar the source into the correct directory on laptop.
4. Run the script from my other msg on the laptop.
5. Modify your code.
6. Tar up the .svn-free source dir on laptop.
7. Copy to desktop.
8. Untar in top source dir and commit changes.
If you *accidentally* run that script on your desktop in the top source
dir, you first need to tar up that directory, then checkout another
copy of the source and untar the file there. Yes, I did that once! Just
once! :-)
--
Kevin Nathan (Arizona, USA)
Linux Potpourri and a.o.l.s. FAQ -- (temporarily offline)
Open standards. Open source. Open minds.
The command line is the front line.
Linux 2.6.25.18-0.2-pae
8:27pm up 22 days 0:19, 20 users, load average: 0.44, 0.45, 0.48 |
|
| |
|
| Back to top |
Chris
Guest
|
| Posted: Wed Nov 19, 2008 7:28 pm Post subject: Re: .svn/tmp |
|
|
Kevin Nathan wrote:
| Quote: | On Tue, 18 Nov 2008 10:39:04 GMT
Chris <chris@thisisnotanemailaddress.ca> wrote:
Thanks for the info. I guess I will need to move around just the code
and try to leave the .svn dirs on my main development machine.
Just to clarify the procedure -- I am assuming your desktop is the
subversion-capable machine and the laptop is not. This, then, is the
procedure to follow:
1. Tar up the source directory on desktop.
2. Copy file to laptop.
3. Untar the source into the correct directory on laptop.
4. Run the script from my other msg on the laptop.
5. Modify your code.
6. Tar up the .svn-free source dir on laptop.
7. Copy to desktop.
8. Untar in top source dir and commit changes.
If you *accidentally* run that script on your desktop in the top source
dir, you first need to tar up that directory, then checkout another
copy of the source and untar the file there. Yes, I did that once! Just
once! :-)
|
Thanks. I found where the the tmp directories were being deleted. I use KDE
and within Konqueror I right-click on my working-copy directory and select
Actions->Archive and Encrypt. The archiving is provided by Kgpg. This seems
to be the problem. If I tar the directory and then encrypt it as a simple
file, the tmp directory is not go missing.
I cannot seem to find a setting in kgpg to tell it not to ignore/omit tmp
files/directories. I guess I will need to do this as a two step process.
I will try archiving and encrypting in two steps for awhile and see if any
other SVN problems arise.
--
Chris |
|
| |
|
| Back to top |
|
