[Bug 215792] Review Request: wgrib - Manipulate, inventory and decode GRIB files

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Review Request: wgrib - Manipulate, inventory and decode GRIB files


https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=215792





------- Additional Comments From pertusus at free.fr  2006-11-16 16:07 EST -------
(In reply to comment #4)
> Think the version is right, previous versions are like 1.7.3.1, 1.8.0.9g.

Ok.

> Did you get this output from testbin.f:
> 
>  bad values:  1.0116254E-40

Yes. From my tests it seems to be for the very latest point, maybe 
an error in the test script.

> I'm thinking of not using testbin.f because I don't really want to be debugging
> one test program when another works.  Also, do you really think it makes sense
> to ship testbin.c and land.grb or just use it in %check?

Both would make sense in my opinion. I think that those files would
be rightly in %doc (and also testbin.f).

> I checked out the tar file before, but it seems to be version 1.8.0.12g which is
> marked as "beta" on the main web page.  The full C file seems to be the
> preferred "release" mechanism and the makefile shipped with the tar file is
> pretty useless as well.

Ok, I thought it was the corresponding wgrib.c. In fact the Changes
file is misleading, and that's because of that file that I thought that 
that the shipped version was 1.8.0.12g. I proposed the tar file because 
there are already some files shipped in that tar and it could remove
the need to ship some of the files individually.

Somethingn should be done for the Changes file.

> Here's the latest:
> http://www.cora.nwra.com/~orion/fedora/wgrib-1.8.0.12b-2.fc6.src.rpm
> 
> As for branches, I'd like to do FC-5 on.  Will need to coordinate with your
> grads package obviously.

Ok. It's already done for devel.


-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.