> On Tue, Feb 27, 2007, Alex Rousskov wrote: >> On Sat, 2007-02-24 at 08:43 +0100, Henrik Nordstrom wrote: >> >> > These locks gets cleared automatically after a while and the lock is >> now >> > gone. >> >> Thanks for the explanation and snipped details. Unfortunately, it looks >> like the problem is back and has even become worse as I see more locks >> (from other developers) getting stuck now: >> >> > cvs rtag: [21:28:08] waiting for rousskov's lock in >> /cvsroot/squid/squid3/lib/cppunit-1.10.0/doc >> > cvs rtag: [21:28:38] waiting for serassio's lock in >> /cvsroot/squid/squid3/lib/cppunit-1.10.0/doc >> > cvs rtag: [21:29:08] waiting for amosjeffries's lock in >> /cvsroot/squid/squid3/lib/cppunit-1.10.0/doc >> >> I am unable to merge with HEAD (using cvsmerge) because of this. >> >> Do you know whether there is something going on with SourceForge that >> increases the probability of these locks getting stuck? Anything we can >> do about it in the short term? > > I'm not sure to be honest; but do you think it'd be a good idea just to > shift this > development tree stuff back to a seperate repository or server over at > TMF? > It sounds like it'll be less of a headache now. >
Or we could call a 48+ hour holiday for any usage of HEAD and see if the locks disappear. Mine was either created 18 hours ago now or 36. For my part I'm going to stop-work until this gets fixed or someone else can run a full cvsmerge HEAD without encountering it. Amos PS. I had this crazy Idea, that if re-running a cvsmerge with all (3 now) of our logins at the same time would play leap-frog with the locks and move them across the code and away eventually. But then I'll bet cvs has been coded secure enough so that hack is impossible too.