GNATS 4.1.0 Released!

GNATS 4.1.0 Released!

[Chad Walstrom]

[-- Attachment #1.1: Type: text/plain, Size: 1371 bytes --]

GNATS 4.1.0, March 2005
==========================

This is GNATS 4.1.0, a release that incorporates multiple bug fixes
and enhancements that have been committed to CVS since the release of
GNATS 4.0.  Notable enhancements include:

- Upgrade to autoconf 2.59 generated configure scripts.
- New PR numbers are reported to the client upon new submissions
- Rewrite of install-sid.  Now, rather than editing send-pr, which can
  be installed on a read-only partition, install-sid creates or edits
  user or site configuration files ~/.send-pr.conf or
  /etc/gnats/send-pr.conf.
- Removal of libiberty, old manpages, and old build framework cruft
- Performance enhancements to indexing code
- Various cleanups and bugfixes.  See the ChangeLog files for details.

This release of GNATS is available at ftp://ftp.gnu.org/pub/gnu/gnats/
or in CVS under the gnats-4_1-branch as gnats-4_1_0-release.  See the
Savannah project page [1]_ for instructions on how to use CVS [2]_.

.. [1] http://savannah.gnu.org/projects/gnats/
.. [2] http://savannah.gnu.org/cvs/?group=gnats

For general questions or help with GNATS, email help-gnats@gnu.org.  To
report bugs, please send email to bug-gnats@gnu.org.

Happy Tracking!

-- 
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

RE: GNATS 4.1.0 Released!

[David S Gathright]

Thanks, Chad and the rest of the GNATS team for pushing this one through!
I've got a few people (students mostly) working for me and I hope I can get
them doing some GNATS-related tools (integrated charts like in the 3.x
distro, maybe an admin interface, etc).  So, hopefully we can give some back
in the near future.

-----
David S Gathright                   LASP - University of Colorado
Flight Software Engineer            1234 Innovation Drive
David.Gathright@lasp.colorado.edu   Boulder, CO 80303
(303) 492-7997 Office               		



_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://lists.gnu.org/mailman/listinfo/help-gnats

Re: GNATS 4.1.0 Released!

['Chad Walstrom']

[-- Attachment #1.1: Type: text/plain, Size: 947 bytes --]

David S Gathright wrote:
> Thanks, Chad and the rest of the GNATS team for pushing this one
> through!  I've got a few people (students mostly) working for me and I
> hope I can get them doing some GNATS-related tools (integrated charts
> like in the 3.x distro, maybe an admin interface, etc).  So, hopefully
> we can give some back in the near future.

Glad to help.  Just make sure you send us your GNATS-related bug
reports.  Either send to bug-gnats@gnu.org or directly to
bug-gnats@skuld.wookimus.net (the temporary home of our GNATS database).

I'll be working on the Debian packages early this week and hope to get
something uploaded to experimental or even unstable before Friday.  I
will definitely be running the new packages on skuld.wookimus.net, so
we'll be eating our own dog-food.

-- 
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

RE: GNATS 4.1.0 Released!

[David S Gathright]

Thanks, Chad and the rest of the GNATS team for pushing this one through!
I've got a few people (students mostly) working for me and I hope I can get
them doing some GNATS-related tools (integrated charts like in the 3.x
distro, maybe an admin interface, etc).  So, hopefully we can give some back
in the near future.

-----
David S Gathright                   LASP - University of Colorado
Flight Software Engineer            1234 Innovation Drive
David.Gathright@lasp.colorado.edu   Boulder, CO 80303
(303) 492-7997 Office               		





_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://lists.gnu.org/mailman/listinfo/help-gnats

Re: GNATS 4.1.0 Released!

['Chad Walstrom']

[-- Attachment #1.1: Type: text/plain, Size: 483 bytes --]

The Debian packages have been compiled and uploaded to unstable.  I've
got 4.1.0 running on skuld.wookimus.net (Debian Sarge on sparc64), and
it seems to be doing well.

I would like to hear from our Mac OS X people on whether or not
compiling with optimizations work.  Hopefully, things should be a bit
cleaner in the absence of libiberty.

-- 
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

My experiences building GNATS 4.10

[Tim Buck]

I got an error building GNATS 4.10:

   Creating gnats-databases...
   make: don't know how to make gnats-pwconv.o. Stop
   *** Error code 2

   Stop in /usr/projects/tim/gnats-4.1.0.

This is on FreeBSD-4.9 using gcc-2.95.4. I edited gnats/Makefile
and appended "gnats-pwconv.c" to the SOURCES line, which got me
past this error. Then I got this one:

   make: don't know how to make send-pr. Stop
   *** Error code 2

I can get past this one by going into the send-pr directory and
doing a "make" there. Next I get this error:

-I . -o gnats.info
-I:No such file or directory
*** Error code 1

Stop in /usr/projects/tim/gnats-4.1.0.

I manually ran "makeinfo -I . -o gnats.info gnats.texi" from the
doc directory to get around this.

Tim Buck * Information Technology Manager * Recognition Research, Inc.
PHONE +1 540 961-6500 * FAX +1 540 961-3568 * EMAIL tbuck@rrinc.com
Good judgment comes from bad experience; a lot of that comes from
bad judgment.




_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://lists.gnu.org/mailman/listinfo/help-gnats

Re: My experiences building GNATS 4.10

[Mike M. Volokhov]

On Tue, 22 Mar 2005 16:54:39 -0500
Tim Buck <tbuck@rrinc.com> wrote:

> I got an error building GNATS 4.10:
> 
>    Creating gnats-databases...
>    make: don't know how to make gnats-pwconv.o. Stop
>    *** Error code 2
> 
>    Stop in /usr/projects/tim/gnats-4.1.0.
> 
> This is on FreeBSD-4.9 using gcc-2.95.4. I edited gnats/Makefile
> and appended "gnats-pwconv.c" to the SOURCES line, which got me
> past this error. Then I got this one:

Yes, this (and some other) file has been missed. Is this ok to put just
all *.c files into SOURCES? I.e.:

Index: Makefile.in
===================================================================
RCS file: /cvsroot/gnats/gnats/gnats/Makefile.in,v
retrieving revision 1.71
diff -u -r1.71 Makefile.in
--- Makefile.in	24 Feb 2005 21:21:22 -0000	1.71
+++ Makefile.in	23 Mar 2005 08:07:10 -0000
@@ -125,7 +125,12 @@
 
 #### Host-, target-, and site-specific makefiles are inserted here.
 
-SOURCES = btime.c cmds.c file-pr.c gen-closed-date.c gen-index.c getclose.c gnatsd.c pr-age.c pr-edit.c pr-stat.c query-pr.c queue-pr.c
+SOURCES = adm.c btime.c client.c cmds.c database.c edit.c fconfig.c \
+	fconfigl.c field.c file-pr.c gen-closed-date.c gen-index.c \
+	getclose.c getdate.c gnats-pwconv.c gnatsd.c gnugetopt.c gnugetopt1.c \
+	index.c internal.c lists.c mail.c misc.c mk_auth.c pr-age.c \
+	pr-edit.c pr-init.c pr-stat.c pr.c query-pr.c query.c queue-pr.c \
+	regex.c version.c
 
 EXTRA_OBJS = @EXTRA_OBJS@
 
> 
>    make: don't know how to make send-pr. Stop
>    *** Error code 2
> 
> I can get past this one by going into the send-pr directory and
> doing a "make" there. Next I get this error:
> 
> -I . -o gnats.info
> -I:No such file or directory
> *** Error code 1
> 
> Stop in /usr/projects/tim/gnats-4.1.0.
> 
> I manually ran "makeinfo -I . -o gnats.info gnats.texi" from the
> doc directory to get around this.

Seems you using FreeBSD make instead of GNU make, so as ${MAKEINFO} has
been not substituted by its default value (makeinfo), and you unable to
built send-pr from top directory. Generally said, missing ".c.o"
expansions can be also done using GNU make.

Another question is why build process so unclean (missing .c files,
missing variables, some "magic" explicit rules at the end of makefile,
and so on)? IMHO we should cleanup makefiles to be compliant to generic
make rules or use GNU atomake framework (but I'm personally are not
familiar with GNU build tools). Which way more preferred?

--
Mishka.


_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://lists.gnu.org/mailman/listinfo/help-gnats

Re: My experiences building GNATS 4.10

[Tim Buck]

On Mar 23, 2005, at 3:21 AM, Mike M. Volokhov wrote:

> Seems you using FreeBSD make instead of GNU make, so as ${MAKEINFO} has
> been not substituted by its default value (makeinfo), and you unable to
> built send-pr from top directory. Generally said, missing ".c.o"
> expansions can be also done using GNU make.

You're right, when I use gmake it compiles cleanly with no errors.
It never occurred to me to try gmake.

Tim Buck * Information Technology Manager * Recognition Research, Inc.
PHONE +1 540 961-6500 * FAX +1 540 961-3568 * EMAIL tbuck@rrinc.com
Our lives are not determined by what happens to us, but by how we react
to what happens.




_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://lists.gnu.org/mailman/listinfo/help-gnats

Re: My experiences building GNATS 4.1.0

[Chad Walstrom]

[-- Attachment #1.1: Type: text/plain, Size: 910 bytes --]

By the way, it isn't GNATS 4.10.  You're about 9 releases in the future.
;-)

On Wed, Mar 23, 2005 at 10:21:44AM +0200, Mike M. Volokhov wrote:
> Another question is why build process so unclean (missing .c files,
> missing variables, some "magic" explicit rules at the end of makefile,
> and so on)?

Historical remnants.

> IMHO we should cleanup makefiles to be compliant to generic make rules
> or use GNU atomake framework (but I'm personally are not familiar with
> GNU build tools). Which way more preferred?

I would like to see a migration to automake and a single configure.ac
file.  However, I didn't want to hold up rolling out 4.1.0 any longer
than necessary.  Now that we've reached that milestone, we can look into
cleaning it up a bit more.

-- 
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

Re: My experiences building GNATS 4.1.0

[Mike M. Volokhov]

On Wed, 23 Mar 2005 10:59:11 -0600
Chad Walstrom <chewie@wookimus.net> wrote:

> By the way, it isn't GNATS 4.10.  You're about 9 releases in the future.
> ;-)
> 
> On Wed, Mar 23, 2005 at 10:21:44AM +0200, Mike M. Volokhov wrote:
> > Another question is why build process so unclean (missing .c files,
> > missing variables, some "magic" explicit rules at the end of makefile,
> > and so on)?
> 
> Historical remnants.
> 
> > IMHO we should cleanup makefiles to be compliant to generic make rules
> > or use GNU atomake framework (but I'm personally are not familiar with
> > GNU build tools). Which way more preferred?
> 
> I would like to see a migration to automake and a single configure.ac

Yep.

> file.  However, I didn't want to hold up rolling out 4.1.0 any longer
> than necessary.  Now that we've reached that milestone, we can look into
> cleaning it up a bit more.

As for me that was correctness decision. Thanks for you work, Chad!

--
Best wishes,
Mishka.


_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://lists.gnu.org/mailman/listinfo/help-gnats