From: Chad Walstrom <chewie@wookimus.net>
To: help-gnats@gnu.org
Subject: Re: gnats-4_1_0-rc1 updated...
Date: Mon, 13 Dec 2004 20:40:00 -0000 [thread overview]
Message-ID: <20041213203849.GD16742@wookimus.net> (raw)
In-Reply-To: <20041119050846.GC32278@wookimus.net>
[-- Attachment #1.1: Type: text/plain, Size: 1999 bytes --]
Chad Walstrom wrote:
> OK, I've committed the gnats/configure.in changes as well as the new
> gnats/autoconf.h.in and configure, and I moved the gnats-4_1_0-rc1 tag
> forward. To get the new updates, run cvs update in your working
> directory.
Since this post, I haven't been able to work on GNATS much. I'll have
some free time coming up again, so hopefully we can work through some of
these compilation bugs.
> I definitely feel the need to have our own GNATS database back up and
> running, now more than ever. A little dogbowl would be good.
Rather than wait for the volunteer GNU sysadmin's to install GNATS for
us, I've installed it on my personal little Ultrasparc 5 running Debian
GNU/Linux (sarge). I did not have email submitted to bug-gnats@gnu.org
forwarded until this weekend, but I believe everything is working as it
should.
All emails submitted to bug-gnats@gnu.org are being forwarded to
bug-gnats@wookimus.net, the email address for the temporary GNATS
server. You may continue to send subsequent emails for the audit trail
to bug-gnats@wookimus.net.
> We have two new open issues with respect to the RC1. One compilation
> issue with Solaris Workshop 8 cc (conflicts between stdlib.h,
> unistd.h, and stdio.h), and one on FreeBSD with gnats-pwconv being
> unbuildable, which may have something to do with how getopt() is being
> declared.
>
> I've got a busy day at work tomorrow and I'm going hunting this
> weekend, so I'll be unable to work on GNATS until next week. If you
> find solutions to these problems, please send them to
> bug-gnats@gnu.org! ;-)
Correction to that advise. If we should hash things out in public
conversations, send it to help-gnats@gnu.org. Let's reserve bug-gnats
for initial problem reports. If you want to watch audit-trail reports,
subscribe to gnats-prs.
--
Chad Walstrom <chewie@wookimus.net> http://www.wookimus.net/
assert(expired(knowledge)); /* core dump */
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 140 bytes --]
_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://lists.gnu.org/mailman/listinfo/help-gnats
prev parent reply other threads:[~2004-12-13 20:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-19 5:09 Chad Walstrom
2004-12-13 20:40 ` Chad Walstrom [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=20041213203849.GD16742@wookimus.net \
--to=chewie@wookimus.net \
--cc=help-gnats@gnu.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).