Postings by Jos de Kloe

license change for python-metar

For your information:
the python-metar package has changed license from MIT to BSD,
starting with release 1.7.0.

<a href="" title=""></a>
<a href="" title=""></a>

best regards,

Jos de Kloe.

question about Obsoletes/Provides

I have a question about an open review request on the eccodes package,
see: <a href="" title=""></a>

Eccodes will replace grib_api for which downstream will stop support at
the end of this year.
Therefore the first draft spec file had Obsoletes/Provides entries to
make clear that eccodes will replace it.

Then I received a comment that this was maybe not correct, since the
replacement package may not be compatible enough so I disabled these

Main differences are:
* grib_api provides a fortran77 library, which is absent in eccodes
* library and pkg-config f

g2clib static lib file name change


I just build a new version of g2clib (upgraded from 1.4.0 to 1.6.0), and
with this change this static library for grib file handling changes name:
old: libgrib2c.a
new: libg2c_v1.6.0.a

I dont know of a packaging guideline that tells me to announce this, but
to prevent surprises for dependent packages I thought I'd mention it.

Best regards,


FAILED: BuildError: package ... not in list for tag f27-pending


I'm trying to do a build for the python-metar package (first time since
I adapted it after it was orphaned), but I constantly get this error
when I try to do a fedpkg build:

FAILED: BuildError: package metar not in list for tag f27-pending

does anyone know what is wrong, and how to solve it?
Could it be related to the fact that I renamed the spec file from to in git?
(I did that since rpmlint gave me the error "E: invalid-spec-name")


some help needed with requires issue in spec file for pyproj

something strange happened in my recent pyproj build on rawhide which
causes all relevant requires to be lost, see:

<a href="" title=""></a>

I tried to find a solution or workaround, but without succes.
When I do a local mock build the same problem arises.

I tried to activate some debug options on mock, but even adding
" --verbose --rpmbuild-opts='-vv' "
did not give me anymore details on the process used to find the

stalled package review

This package review: <a href="" title=""></a>
has been stalled for several years now since the original submitter
(Karel Klíč) never got back to it, even though the review was approved.

Since it is not packaged yet, the nonresponsive package maintainers
policy does not apply I think. So can someone else just step in and
package it, or should the review be redone in this case?


request for pygrib packaging debug help

Hi everyone,

I am having a small issue with the pygrib package that I am maintaining.
The package depends on pyproj, but when I install it with yum it also
pulls in python3-pyproj.
All python3 related things are wrapped in "%if 0%{?with_python3}"
macros, so this should not happen I think.
Clearly I am overlooking some dependency issue in my spec file.
Any help would be appreciated.

Best regards,

Jos de Kloe

self introduction

Hi everyone,

my name is Jos de Kloe, I am working for the Dutch Met.