[cvsnt] Committed file does not show up on update.

Krooshof, Frederik Frederik.Krooshof at raet.com
Fri Aug 18 14:10:02 BST 2006


Thanks Bo,

Installing 2.5.03 did indeed bring the solution. So, thank you for your
help!
God only knows why it went wrong in the first place. But hey... Who
cares.
I'm very glad. :-)))

Frederik Krooshof 

Software engineer
Raet|
T +31(0)33 4506506  F +31(0)33 4506482
Postbus 1495, 3800 BL Amersfoort
Plotterweg 38, 3821 BB Amersfoort
The Netherlands
www.raet.nl

-----Original Message-----
From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org] On Behalf
Of Bo Berglund
Sent: woensdag 16 augustus 2006 10:57
To: cvsnt at cvsnt.org
Subject: Re: [cvsnt] Committed file does not show up on update.

Hmm,
you are running build 1990 on the server, and I don't think this is the
best choice....
Please try to install the latest stable release of 2.5.03 instead and
repeat the tests.

If the file in question was added on the branch as the revision number
suggests then it will not exist at all on trunk.
And I seem to remember that some intermediate builds had a problem with
files added on branch so switching to a newer version might well cure
your problem.


Best regards,

Bo Berglund


-----Original Message-----
From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org] On Behalf
Of Krooshof, Frederik
Sent: den 16 augusti 2006 10:07
To: cvsnt at cvsnt.org
Subject: [cvsnt] Committed file does not show up on update.

Hello list,

Maybe someone has also experienced this or has some ideas...

(Our repository is on a NT server).

For over a year now our CVSNT software has served us well. But returning
from a vacation there appeared to be an awkward problem.

Committing changes to a file produces a new revision for the file. But
when someone else updates the sandpit for the particular branch, on
completion of the update the sandpit does not contain the newborn
revision for the file. In stead it shows the one but last revision, for
example 1.5 in stead of 1.5.30.1.
A graph in WinCvs for the file shows:
- the new revision 1.5.30.1 does exist. ( inspection of the ,v file
confirms this )
- the revision is located on the particular branch; it was committed in
the particular branch.

Switching off the virus checker on the server with the repository did
not help.
The problem also occurs when committing on another branch.

<snip>
----
De inhoud van dit bericht en de eventueel daarbij behorende bijlagen zijn
persoonlijk gericht aan en derhalve uitsluitend bestemd voor de geadresseerde.
De ontvanger die niet de geadresseerde is, noch bevoegd is dit bericht namens
geadresseerde te ontvangen, wordt verzocht de afzender onmiddellijk op de hoogte
te stellen van de ontvangst.
Elk gebruik van de inhoud van dit bericht en/of van de daarbij behorende bijlagen
door een ander dan de geadresseerde is onrechtmatig jegens de afzender.

The content of this communication and any attachments are of a confidential 
nature and accordingly intended only to be read by the addressee.
If anyone receives this communication who is not the addressee and is not 
authorised by the addressee to receive such communication then such person 
is requested to notify the sender immediately.
Any use of the content of this communication or any attachments by anyone 
other than the addressee constitutes an unlawful act.
----


More information about the cvsnt mailing list