Login | Register
My pages Projects Community openCollabNet

Discussions > users > RE: after commit local copy is still seen as new

fsvs
Discussion topic

Hide all messages in topic

All messages in topic

RE: after commit local copy is still seen as new

Author "Miller, Hugh" <HughMiller at chevron dot com>
Full name "Miller, Hugh" <HughMiller at chevron dot com>
Date 2010-10-20 07:33:29 PDT
Message > -----Original Message-----
> From: Philipp Marek [mailto:philipp at marek dot priv dot at]


> > concerns about damage to the folders under branches that are
currently OK ?

> No, there should be no damage.
> "sync-repos" doesn't change anything of the working copy data - it
just
> fetches a fresh
> filelist from the repository.

Thanks!

>
>
> BTW, why do you keep tags and branches checked out, too?

Actually we don't have anything in tags.

RE: after commit local copy is still seen as new

Author pmarek
Full name P.Marek
Date 2010-10-19 23:53:38 PDT
Message Hello Hugh!

>> If the other branches are separate checkouts (other working copies),
>> they don't need to
>> be handled.
>
> All the branches are under the same working copy base. The base is a
> folder, fsvs_working, with sub-folders branches, tags, trunk, and under
> each of these various versions of the software.
>
> I don't see any way to sync-repos just few version folders under
> branches that have the problem, except by syncing the whole of
> fsvs_working. Is there a way to do this ? If not, should there be any
> concerns about damage to the folders under branches that are currently
> OK ?
No, there should be no damage.
"sync-repos" doesn't change anything of the working copy data - it just fetches a fresh
filelist from the repository.


BTW, why do you keep tags and branches checked out, too?
I'm aware that I didn't implement the "tag" and "branch" commands for FSVS yet, but as
it's a subversion repository you can always do the standard

    svn cp $URL/trunk $URL/tags/1.0.0 -m "Tagged 1.0.0"

without disturbing FSVS ...


Regards,

Phil

--
Versioning your /etc, /home or even your whole installation?
             Try fsvs (fsvs.tigris.org)!

RE: after commit local copy is still seen as new

Author "Miller, Hugh" <HughMiller at chevron dot com>
Full name "Miller, Hugh" <HughMiller at chevron dot com>
Date 2010-10-19 12:35:03 PDT
Message > -----Original Message-----
> From: Philipp Marek [mailto:philipp at marek dot priv dot at]
> Sent: Saturday, October 16, 2010 11:51
> If the other branches are separate checkouts (other working copies),
> they don't need to
> be handled.

All the branches are under the same working copy base. The base is a
folder, fsvs_working, with sub-folders branches, tags, trunk, and under
each of these various versions of the software.

I don't see any way to sync-repos just few version folders under
branches that have the problem, except by syncing the whole of
fsvs_working. Is there a way to do this ? If not, should there be any
concerns about damage to the folders under branches that are currently
OK ?

Thanks, Hugh

RE: after commit local copy is still seen as new

Author pmarek
Full name P.Marek
Date 2010-10-16 09:50:53 PDT
Message Hello Hugh!

>> Well, a "sync-repos" should fix this.
>
> fsvs info for an actual problem folder such as branches/XXXYYYZZZ does
> not show an URL:
...
> Would sync-repos work in this situation ?
>
> Or should I run sync-repos on the branches folder itself ? Would there
> be any danger to other folder in branches (which are OK) ?
"sync-repos" goes to the repository(ies), and asks for the current file-list for the
whole working copy.

If the other branches are separate checkouts (other working copies), they don't need to
be handled.

http://doc.fsvs-soft​ware.org/doxygen-gif​/group__cmds.html#sy​nc-repos


Regards,

Phil


--
Versioning your /etc, /home or even your whole installation?
             Try fsvs (fsvs.tigris.org)!

RE: after commit local copy is still seen as new

Author "Miller, Hugh" <HughMiller at chevron dot com>
Full name "Miller, Hugh" <HughMiller at chevron dot com>
Date 2010-10-16 09:28:27 PDT
Message > -----Original Message-----
> From: P.Marek [mailto:philipp at marek dot priv dot at]
> Sent: Saturday, October 16, 2010 01:11



> > Can you enlighten me on how to fix this ?
> Well, a "sync-repos" should fix this.

fsvs info for an actual problem folder such as branches/XXXYYYZZZ does
not show an URL:

.../branches $ fsvs info XXXYYYZZZ
N... dir XXXYYYZZZ
   Type: directory
   ChildCount: 0
   URL: (none)
   Status: 0x1 (new)
   Flags: 0x80002 (add)
   Dev: 29
   Inode: 13675076
   Mode: 042755
....
   WAA-Path: /A/B/C/fsvs_waa/4e/7​8/47ecbf508f8cfe6f2c​262268ce3e/
   Revision: 0
   Size: 4096

Would sync-repos work in this situation ?

Or should I run sync-repos on the branches folder itself ? Would there
be any danger to other folder in branches (which are OK) ?

Thanks, Hugh

RE: after commit local copy is still seen as new

Author "Miller, Hugh" <HughMiller at chevron dot com>
Full name "Miller, Hugh" <HughMiller at chevron dot com>
Date 2010-10-16 04:08:53 PDT
Message > -----Original Message-----
> From: P.Marek [mailto:philipp at marek dot priv dot at]
> Sent: Saturday, October 16, 2010 01:11

> Is that with a current version? I know that such a bug is in 1.1.17,
> but it should not
> be in the current versions!

I believe it was with fsvs 1.2.2 and svn 1.6.11. (Also running on
rhel5.3.)

I should perhaps mention that I was committing in separate fsvs sessions
other branches (same FSVS environment) around the same time. These
commits were overlapping in duration. Some these were actually unversion
followed by commit and working copy delete to clean up.

>
> Is it reproducible? If yes, please do a run with -d, and perhaps
> another one with strace
> - although I don't that I've forgotten to check an error code
anywhere.

It doesn't seem to be readily reproducible. I made several other commits
of other folders (same branches folder and FSVS environment) at that
time that all worked. I may have seen this once before some months ago.

> > Can you enlighten me on how to fix this ?
> Well, a "sync-repos" should fix this.

I'll give that a try!

Thanks, Hugh

Re: after commit local copy is still seen as new

Author pmarek
Full name P.Marek
Date 2010-10-15 23:11:36 PDT
Message Hello Hugh!

> I committed several working copies. The svn repository
> seems to have all
> the commits correctly, but fsvs status still shows all
> the working copy
> files as "N".
Is that with a current version? I know that such a bug is in 1.1.17, but it should not
be in the current versions!

Is it reproducible? If yes, please do a run with -d, and perhaps another one with strace
- although I don't that I've forgotten to check an error code anywhere.

> Not sure what happened. An attempt to commit again
> gives this type of
> message (where XXXYYYZZZ is the name of the
> working directory):
>
>
> An error occurred: Device or resource busy (16)
> in ci__directory: add_directory(./bran​ches/XXXYYYZZZ,
> source="(null)"@HEAD) returns 160020
>
>
> Can you enlighten me on how to fix this ?
Well, a "sync-repos" should fix this.

But it would be more important to find the root cause ...


Regards,

Phil

--
Versioning your /etc, /home or even your whole installation?
             Try fsvs (fsvs.tigris.org)!

after commit local copy is still seen as new

Author "Miller, Hugh" <HughMiller at chevron dot com>
Full name "Miller, Hugh" <HughMiller at chevron dot com>
Date 2010-10-15 19:46:07 PDT
Message I committed several working copies. The svn repository seems to have all
the commits correctly, but fsvs status still shows all the working copy
files as "N". fsvs info does not show a URL (but does show a WAA-path).
Not sure what happened. An attempt to commit again gives this type of
message (where XXXYYYZZZ is the name of the working directory):


An error occurred: Device or resource busy (16)
  in ci__directory: add_directory(./bran​ches/XXXYYYZZZ,
source="(null)"@HEAD) returns 160020


Can you enlighten me on how to fix this ?

Thanks, Hugh
Messages per page: