public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Jim Meyering <jim@meyering.net>
To: overseers@sourceware.org
Subject: Re: Upstream cvs repository corruption?
Date: Mon, 24 Sep 2007 16:50:00 -0000	[thread overview]
Message-ID: <87ir60uhwu.fsf@rho.meyering.net> (raw)
In-Reply-To: <20070924153424.GB29974@ednor.casa.cgf.cx> (Christopher Faylor's message of "Mon, 24 Sep 2007 11:34:24 -0400")

Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org> wrote:

> On Mon, Sep 24, 2007 at 05:06:37PM +0200, Jim Meyering wrote:
>>Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org> wrote:
>>>I was trying to find out what that should actually be.  There is no
>>>need to rationalize the need.  I just want to figure out how this
>>>should actually be set up.  And, I thought that if we chose another
>>>account with different access rights it might actually solve the
>>>problem.
>>
>>Chris,
>>
>From the tone of your messages, I fear I may have done something to
>>offend you.  If so, please rest assured that whatever I did was not
>>intended to rustle any feathers.
>
> Please reread the above without any preconceptions about tone.  I'm not
> "offended".  I want to solve a problem.

I'm glad there was no perceived offense.

BTW, I have no preconceptions.
How could I have any, when I don't know you
and haven't heard anything to bias me?

> Here is my point:
>
> SER       PID %CPU %MEM   VSZ  RSS TTY      STAT START   TIME COMMAND
[more hung cvs-related processes]

The tools that seem to make cvs hang (mirror-* -> git-cvsimport -> cvsps -> cvs)
are solely to synchronize a mirrored git repository from the cvs one.
Thus, removing these tools would not affect whether sourceware.org
provides a git server.

Those same scripts work fine on at least three other systems (one of
which is also RHEL 4).  However, those systems all use cvs-1.12.13,
while sourceware is using cvs-1.11.15.  I've built 1.12.13 with -g
and installed it in my own ~/bin directory so the scripts will use that.
We'll see if that fixes the problem.  If not, I'll debug it, so one
way or another, this problem should last no longer than a day or so more.

      reply	other threads:[~2007-09-24 16:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1190637220.4431.2.camel@linux-cxyg>
2007-09-24 13:04 ` Jim Meyering
2007-09-24 13:15   ` Christopher Faylor
2007-09-24 14:28     ` Jim Meyering
2007-09-24 14:39       ` Christopher Faylor
2007-09-24 15:06         ` Jim Meyering
2007-09-24 15:34           ` Christopher Faylor
2007-09-24 16:50             ` Jim Meyering [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ir60uhwu.fsf@rho.meyering.net \
    --to=jim@meyering.net \
    --cc=overseers@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).