On 10/15/2014 05:03 PM, Tim Connors wrote: > Note that in that thread, "Our users will never see the warning message > since packages built against the newer gpg-error will depend on it and > packages built against the old one will not show the warning either. (I > have not actually run any tests to verify this, but I guess you did.)" > > We do see the warning message, because the likes of a later version of > libgcrypt doesn't appear to depend on the required version of > libgpg-error (it depends on >= 1.10, whereas it appears from that > discussion to have been built against >=1.15).
hm, i suppose this means that we might want to bump the .symbols file in
libgpg-error0 to refer to 1.15 for all symbols since the version node
was introduced there?
that seems like it would be similar to a library transition, though, and
i know that the release team is frowning on that at this late date, and
it would be entirely for the purpose of avoiding a warning (not an error).
I'm not sure this would be worth the tradeoff, but i'm willing to
consider it if people feel strongly about it.
--dkg
signature.asc
Description: OpenPGP digital signature
