Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: "'Daniel Jacobowitz'" <drow@false.org>
Cc: <gdb-patches@sourceware.org>
Subject: Update ARI pages
Date: Thu, 11 Oct 2007 08:55:00 -0000	[thread overview]
Message-ID: <002301c80bd8$051fc9f0$0f5f5dd0$@u-strasbg.fr> (raw)
In-Reply-To: <20071010120140.GB10228@caradoc.them.org>



> -----Original Message-----
> From: gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] On Behalf Of 'Daniel Jacobowitz'
> Sent: Wednesday, October 10, 2007 2:02 PM
> To: Pierre Muller
> Cc: gdb-patches@sourceware.org
> Subject: Re: [RFA] gdb_ari.sh patch to eliminate wrong critical errors
> 
> On Wed, Oct 10, 2007 at 10:09:18AM +0200, Pierre Muller wrote:
> >   I tested this locally and it does reduce the
> > number of critical entries to 4.
> >
> >   Daniel, could you please commit this?
> 
> Done.

  Strange, because the ARI from today still do not
reflect the changes :(
  The gdb_ari.sh still contains the old 'strerror' rule
for which the implementation should be in gdb/utils.c file.
  Maybe the files executing every night are not automatically
synchronized with the cvs repository.

  Daniel, someone having direct access to the web server
is needed here, could you take a look at it?
  Maybe running ./do-scp in the directory
that is used for the nightly update would be enough.

  It might also be a good time (as 6.7 just came out)
to refresh the 'last release' page, but, to be honest,

  I tried to write a custom script for that:

#!/bin/sh
# Copy release to temp dir; directory unsure, based on do-snapshot script
version=6.7
tmpdir=/sourceware/snapshot-tmp/gdb/release/gdb-${version}
wwwdir=/www/sourceware/htdocs/gdb/download
cp /sourceware/ftp/anonftp/pub/gdb/releases/gdb-${version}.tar.gz
${tmpdir}/update-web-ari
# Move to temp dir
cd ${tmpdir}/update-web-ari
#Gunzip tar file
gunzip gdb-${version}.tar.gz
# Run update-web-ari script, destination web dir also uncertain...
$(HOME)/ss/update-web-ari ${tmpdir}/update-web-ari/gdb.tar
${tmpdir}/update-web-ari ${wwwdir} /ari gdb

  But I don't know if the paths are still valid.

Could you try it out?

Pierre
  


 




  parent reply	other threads:[~2007-10-11  7:26 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-10  9:07 [RFA] gdb_ari.sh patch to eliminate wrong critical errors Pierre Muller
2007-10-10 12:18 ` 'Daniel Jacobowitz'
2007-10-10 14:52   ` Ulrich Weigand
2007-10-10 15:04     ` 'Daniel Jacobowitz'
2007-10-10 15:27   ` Jim Blandy
2007-10-10 15:51     ` Mark Kettenis
2007-10-11  8:55   ` Pierre Muller [this message]
2007-10-11 14:20     ` Update ARI pages 'Daniel Jacobowitz'
2007-10-11 16:53       ` Joel Brobecker
2007-10-15  9:23         ` Pierre Muller
2007-10-24 20:07     ` 'Daniel Jacobowitz'
2007-10-24 20:42       ` Joel Brobecker
2007-10-24 21:06         ` Daniel Jacobowitz
2007-10-25  7:55         ` Pierre Muller
2007-10-11 19:41 ` [RFA] gdb_ari.sh patch to eliminate wrong critical errors Ulrich Weigand
2007-10-15 12:15   ` Pierre Muller
2007-10-15 13:47     ` 'Daniel Jacobowitz'
2007-10-15 13:50     ` Ulrich Weigand
2007-10-15 14:13       ` Ulrich Weigand

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='002301c80bd8$051fc9f0$0f5f5dd0$@u-strasbg.fr' \
    --to=muller@ics.u-strasbg.fr \
    --cc=drow@false.org \
    --cc=gdb-patches@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