Re: RESEND - URGENT !!! - Cannot cvsmerge on sourceforge
mån 2008-02-18 klockan 15:58 -0700 skrev Alex Rousskov: Since this problem did not go away since January and Henrik may not be available, perhaps you can log a ticket with SourceForge? That's the proper way. SourceForge site services support requests is filed here: http://sourceforge.net/tracker/?func=addgroup_id=1atid=21 Category: Project CVS Services Summary: stale CVS lock file removal request Description: project: squid [paste CVS output] They usually deal with issues within 24 hours, which often is a better response time than me.. Regards Henrik signature.asc Description: Detta är en digitalt signerad meddelandedel
Re: RESEND - URGENT !!! - Cannot cvsmerge on sourceforge
sön 2008-02-17 klockan 11:46 +0100 skrev Guido Serassio: Hi, Im resending again this message, because the problem is still here, since 21 January .. 18'th actually.. # Set a temporary tag at the new version we are merging towards... cvs -q rtag -F -r HEAD Z-nt_merge-new_HEAD squid cvs rtag: [16:53:08] waiting for squidadm's lock in /cvsroot/squid/squid/ntlm_auth_modules/no_check Cleared. Regards Henrik signature.asc Description: Detta är en digitalt signerad meddelandedel
Re: RESEND - URGENT !!! - Cannot cvsmerge on sourceforge
Hi Alex, At 23:58 18/02/2008, Alex Rousskov wrote: On Sun, 2008-02-17 at 11:46 +0100, Guido Serassio wrote: Im resending again this message, because the problem is still here, since 21 January .. I had that happen a few times and the response was always wait and it will go away or ask Henrik to manually kill the lock. You should be able to find those responses and perhaps more details in the list archives. Since this problem did not go away since January and Henrik may not be available, perhaps you can log a ticket with SourceForge? I'm not sure that they will work on our scripts. We should ask Henrik to publish lock killing instructions when he is back. Yes, I agree. Will Squid2 tree be migrated to bzr along with Squid3? Fine for me, like everything better than now :-) Regards Guido - Guido Serassio Acme Consulting S.r.l. - Microsoft Certified Partner Via Lucia Savarino, 1 10098 - Rivoli (TO) - ITALY Tel. : +39.011.9530135 Fax. : +39.011.9781115 Email: [EMAIL PROTECTED] WWW: http://www.acmeconsulting.it/
Re: RESEND - URGENT !!! - Cannot cvsmerge on sourceforge
On Tue, 2008-02-19 at 22:46 +0100, Guido Serassio wrote: Since this problem did not go away since January and Henrik may not be available, perhaps you can log a ticket with SourceForge? I'm not sure that they will work on our scripts. The problem is not with the script, but with a cvs command that finds a lock somewhere in the repository. You can just tell them what *cvs* command fails and not mention any scripts. Somebody with enough access privileges should be able to go in and manually delete the lock file, I guess. Alex.
Re: RESEND - URGENT !!! - Cannot cvsmerge on sourceforge
On Tue, 2008-02-19 at 16:22 -0700, Alex Rousskov wrote: The problem is not with the script, but with a cvs command that finds a lock somewhere in the repository. You can just tell them what *cvs* command fails and not mention any scripts. Somebody with enough access privileges should be able to go in and manually delete the lock file, I guess. You can actually change the CVS precommit script for a different module to clear the locks in the module you have a problem with; then revert that script back to what it should be. -Rob -- GPG key available at: http://www.robertcollins.net/keys.txt. signature.asc Description: This is a digitally signed message part
Re: RESEND - URGENT !!! - Cannot cvsmerge on sourceforge
On Sun, 2008-02-17 at 11:46 +0100, Guido Serassio wrote: Im resending again this message, because the problem is still here, since 21 January .. I had that happen a few times and the response was always wait and it will go away or ask Henrik to manually kill the lock. You should be able to find those responses and perhaps more details in the list archives. Since this problem did not go away since January and Henrik may not be available, perhaps you can log a ticket with SourceForge? We should ask Henrik to publish lock killing instructions when he is back. Will Squid2 tree be migrated to bzr along with Squid3? Thank you, Alex. There is some problem on the Squid-2 repository on Sourceforge, when running cvsmerge I get forever the following error: # Set a temporary tag at the new version we are merging towards... cvs -q rtag -F -r HEAD Z-nt_merge-new_HEAD squid cvs rtag: [16:53:08] waiting for squidadm's lock in /cvsroot/squid/squid/ntlm_auth_modules/no_check cvs rtag: [16:53:38] waiting for squidadm's lock in /cvsroot/squid/squid/ntlm_auth_modules/no_check cvs rtag: [16:54:08] waiting for squidadm's lock in /cvsroot/squid/squid/ntlm_auth_modules/no_check cvs rtag: [16:54:39] waiting for squidadm's lock in /cvsroot/squid/squid/ntlm_auth_modules/no_check Regards Guido - Guido Serassio Acme Consulting S.r.l. - Microsoft Certified Partner Via Lucia Savarino, 1 10098 - Rivoli (TO) - ITALY Tel. : +39.011.9530135 Fax. : +39.011.9781115 Email: [EMAIL PROTECTED] WWW: http://www.acmeconsulting.it/ - Guido Serassio Acme Consulting S.r.l. - Microsoft Certified Partner Via Lucia Savarino, 1 10098 - Rivoli (TO) - ITALY Tel. : +39.011.9530135 Fax. : +39.011.9781115 Email: [EMAIL PROTECTED] WWW: http://www.acmeconsulting.it/
Re: RESEND - URGENT !!! - Cannot cvsmerge on sourceforge
On Mon, 2008-02-18 at 15:58 -0700, Alex Rousskov wrote: Will Squid2 tree be migrated to bzr along with Squid3? I am happy to do so. I'm not sure that we'll be able to get great joining of history - enough surgery has happened on both trees to make them quite separate these days. Thats not a reason to not migrate though. -Rob signature.asc Description: This is a digitally signed message part