Re: g2clib static lib file name change

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Thanks Volker,

so the affected packages are:
   gdal, grads, ncl, pygrib, wgrib2

I will fix pygrib myself.
Orion Poplawski knows about the change and already looked at gdal.
He also is main contact for ncl and wgrib2.

So only grads remains. I filed a bugzilla entry to warn the maintainers
about this change.

On 08/17/2017 09:11 PM, Volker Fröhlich wrote:
> Am 2017-08-17 um 09:45 schrieb Jos de Kloe:
>> Hi, thanks for your remark.
>>
>> I am aware of one single other package that uses this lib, for which I
>> am the maintainer myself.
>>
>> The updates policy for rawhide says:
>>> A week in advance, notify maintainers who depend on their package to
>>> rebuild when there are abi/api changes that require rebuilds in other
>>> packages or offer to do these rebuilds for them.
>> Actually I don't know how to find out if there are others. I could not
>> find an easy tool/method in the collection of fedora packaging
>> tools/websites to do a query for other packages that have a BR on this
>> library.
> 
> repoquery --enablerepo=fedora-source --enablerepo=updates-source
> --archlist=src --whatrequires g2clib-static
> 
> Greetings,
> 
> Volker
> 
>> On 08/15/2017 10:23 PM, Michael Schwendt wrote:
>>> On Tue, 15 Aug 2017 22:13:00 +0200, Jos de Kloe wrote:
>>>
>>>> Hi,
>>>>
>>>> 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.
>>>
>>> Well, are you aware of any src.rpm that needs this library as build
>>> requirement? If so, better inform the packager directly, because the
>>> next
>>> (re)build of that package will fail. If not other packages in the
>>> distribution
>>> use this lib, there may be private users of the Fedora package, but it's
>>> uncertain whether they can be reached via devel@ list.
>>>
>>> Packaging guidelines don't cover changes like that, but Update
>>> guidelines
>>> may: https://fedoraproject.org/wiki/Category:Package_Maintainers
>>> _______________________________________________
>>> devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
>>> To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
>>>
>> _______________________________________________
>> devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
>> To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
>>
> _______________________________________________
> devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux