public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org, overseers@sourceware.org
Subject: Re: ARI no longer updated?
Date: Fri, 22 Jun 2007 15:12:00 -0000	[thread overview]
Message-ID: <20070622135626.GA12381@caradoc.them.org> (raw)
In-Reply-To: <200706221342.l5MDgRm0030152@d12av02.megacenter.de.ibm.com>

On Fri, Jun 22, 2007 at 03:42:27PM +0200, Ulrich Weigand wrote:
> Hello,
> 
> it looks like the GDB A.R. Index web page 
> 
>    http://sourceware.org/gdb/current/ari/
> 
> is no longer updated daily, it says as of today:
> 
>   Last updated: Thu May 24 01:56:16 UTC 2007
> 
> Since I found this page quite useful, I'd like to get the
> updates going again.  Unfortunately, I'm not familiar with
> the infrastructure behind the web page.  Can anyone help
> with this?  Thanks!

This runs out of gdbadmin.  I don't know who has access to the user;
the group is cagney,cgf,anoncvs.

/sourceware/www/sourceware/htdocs/gdb/ari is current (generated
today).  gdb/current/ari has not been generated in a while.  At a guess,
snapshots are failing too.  Ian posted something about that on
binutils@ the same day.

make: *** No rule to make target `ltsugar.m4,', needed by `binutils.tar.bz2'.
Stop.

Looks like someone needs to update src-release.

Overseers, could someone at least make ~gdbadmin a+x (it's already
a+r)?  Maybe someone else should have access to this account now...

-- 
Daniel Jacobowitz
CodeSourcery

       reply	other threads:[~2007-06-22 13:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200706221342.l5MDgRm0030152@d12av02.megacenter.de.ibm.com>
2007-06-22 15:12 ` Daniel Jacobowitz [this message]
2007-06-25 15:56   ` Christopher Faylor

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=20070622135626.GA12381@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=overseers@sourceware.org \
    --cc=uweigand@de.ibm.com \
    /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).