On Fri, 2018-03-30 at 09:29 +0200, Niels Möller wrote:
> Daniel P. Berrangé writes:
>
> > The traditional way is for developers to update the dependancies to
> > have
> > an explicit version against the library they require. eg if libvirt
> > requires
> > some symbol
On Fri, Mar 30, 2018 at 09:29:51AM +0200, Niels Möller wrote:
> Daniel P. Berrangé writes:
> > The only scope for errors here is when the
> > nettle developers are creating the symbol version file,
>
> That's me... And I imagine we'll get into the territory of subtle
>
Daniel P. Berrangé writes:
> The traditional way is for developers to update the dependancies to have
> an explicit version against the library they require. eg if libvirt requires
> some symbol introduced in nettle x.y, the maintainer would add
>
> Requires: nettle >= x.y
On Tue, Mar 27, 2018 at 11:04:28PM +0200, Niels Möller wrote:
> Nikos Mavrogiannopoulos writes:
>
> > When we initially introduced symbol versioning in nettle we bundled
> > all symbols from the library in a single version. That means that new
> > symbols added to a release
Nikos Mavrogiannopoulos writes:
> When we initially introduced symbol versioning in nettle we bundled
> all symbols from the library in a single version. That means that new
> symbols added to a release like nettle_get_hashes() may cause issues
> like this:
>
On Tue, Feb 27, 2018 at 02:01:06PM +0100, Nikos Mavrogiannopoulos wrote:
> Hi,
> When we initially introduced symbol versioning in nettle we bundled
> all symbols from the library in a single version. That means that new
> symbols added to a release like nettle_get_hashes() may cause issues
>
Hi,
When we initially introduced symbol versioning in nettle we bundled
all symbols from the library in a single version. That means that new
symbols added to a release like nettle_get_hashes() may cause issues
like this:
https://bugzilla.redhat.com/show_bug.cgi?id=1549190
The underlying issue