storework progression

2007-02-23 Thread Adrian Chadd 

Storework is now missing pretty much all of the HTTP related caching code.
I'm noticing some weird browsing issues where requests get 'lost' and
never complete for some reason, which I'm not suprised at at all.

Is anyone up for testing it out and helping me sort out whatever bugs
are in 'ere?

Thanks,




Adrian

locked out by partial cvsmerge

2007-02-23 Thread Alex Rousskov 
Hi there,

I was running 'cvsmerge HEAD' from squid3-icap branch and got
distracted. Meanwhile the internet connection went down. I am not sure
where cvsmerge stopped, but it probably did not complete. If I try it
again, I get:

 cvs rtag: [06:10:02] waiting for rousskov's lock in 
 /cvsroot/squid/squid3/lib/cppunit-1.10.0/doc

I tried to break my own lock, but, to my surprise, I get the same kind
of result from cvs admin -u. It sounds like to break my lock, I need
to obtain it first, which does not make sense to me:

 cvs admin: [23:22:56] waiting for rousskov's lock in 
 /cvsroot/squid/squid3/lib/cppunit-1.10.0/doc

FWIW, it is always the same directory that CVS gets stuck on.

Do we have command-line access to SourceForge CVS so that the lock file
can be manually removed? What should I do to unlock myself?

Thank you,

Alex.

Re: locked out by partial cvsmerge

2007-02-23 Thread Adrian Chadd 
On Fri, Feb 23, 2007, Alex Rousskov wrote:

 Do we have command-line access to SourceForge CVS so that the lock file
 can be manually removed? What should I do to unlock myself?

Shell.sourceforge.net is currently busted for some reason. I wonder whats going
on.




adrian

Re: locked out by partial cvsmerge

2007-02-23 Thread Amos Jeffries 

Adrian Chadd wrote:

On Fri, Feb 23, 2007, Alex Rousskov wrote:


Do we have command-line access to SourceForge CVS so that the lock file
can be manually removed? What should I do to unlock myself?


Shell.sourceforge.net is currently busted for some reason. I wonder whats going
on.



oh, grrr.
It looks like the rest of us are also blocked by that lock.

I just tried to merge the latest changes down into my branch and it 
gives me the same warning/error.


cvs rtag: [02:21:29] waiting for rousskov's lock in 
/cvsroot/squid/squid3/lib/cppunit-1.10.0/doc


I had to abort after a 30sec loop displaying that error for 10 minutes.

Amos

Re: locked out by partial cvsmerge

2007-02-23 Thread Alex Rousskov 
On Sat, 2007-02-24 at 15:33 +1300, Amos Jeffries wrote:
 Adrian Chadd wrote:
  On Fri, Feb 23, 2007, Alex Rousskov wrote:
  
  Do we have command-line access to SourceForge CVS so that the lock file
  can be manually removed? What should I do to unlock myself?
  
  Shell.sourceforge.net is currently busted for some reason. I wonder whats 
  going
  on.
  
 
 oh, grrr.
 It looks like the rest of us are also blocked by that lock.
 
 I just tried to merge the latest changes down into my branch and it 
 gives me the same warning/error.
 
 cvs rtag: [02:21:29] waiting for rousskov's lock in 
 /cvsroot/squid/squid3/lib/cppunit-1.10.0/doc
 
 I had to abort after a 30sec loop displaying that error for 10 minutes.

Ouch.

FWIW, I can get to shell.sourceforge.net, but I do not want to create
more problems experimenting and probably do not have write access to the
right CVS files anyway. Let's hope somebody will fix this soon.

Sorry,

Alex.

Re: locked out by partial cvsmerge

2007-02-23 Thread Henrik Nordstrom 
fre 2007-02-23 klockan 16:30 -0700 skrev Alex Rousskov:
 Hi there,
 
   I was running 'cvsmerge HEAD' from squid3-icap branch and got
 distracted. Meanwhile the internet connection went down. I am not sure
 where cvsmerge stopped, but it probably did not complete. If I try it
 again, I get:
 
  cvs rtag: [06:10:02] waiting for rousskov's lock in 
  /cvsroot/squid/squid3/lib/cppunit-1.10.0/doc

These locks gets cleared automatically after a while and the lock is now
gone.

 I tried to break my own lock, but, to my surprise, I get the same kind
 of result from cvs admin -u. It sounds like to break my lock, I need
 to obtain it first, which does not make sense to me

CVS has two different kinds of locks.

* edit locks, set/unset manually. Inherited from RCS but generally isn't
used much in CVS or even meaningful in normal use of CVS.

* repository file locks, automatic while it updates the repository.

only the first category can be unlocked manually by using cvs admin. The
second is there to protect the structure of the repository.
Unfortunately sometimes when things go wrong a repository lock may be
left around..

Unfortunately CVS is a bit dumb and does not deal with stale repository
locks very well, but SourceForge automatically clears stale repository
locks after a while (some hours).

Regards
Henrik


signature.asc
Description: Detta är en digitalt signerad	meddelandedel